I have a number of Ansible modules that I have developed for managing
Katello entities and Foreman organizations. An Ansible module can be
thought of as providing extentsibility and new functionality to Ansible
roles and playbooks. In this case, by being able to manage entities within
Foreman and Katello. There are also a number of modules I have seen upon
google search that exist for other various Foreman entities.
I would like to share the modules I have written and encourage other
community users to share theirs in a centralized place for use. Ideally,
these modules would be offered to and go into Ansible's core set of modules
after some time of development. However, I believe they need somewhere
useful to live during said transition and as a place to harden them before
offering them up and awaiting an Ansible release.
Thus, I would like to propose and request a repository on theforeman Github
organization named 'foreman-ansible-modules' as a place for these to live.
The goals of the repository would be:
House Ansible modules for managing Foreman and Katello entities
Encourage other community users to add in their own to centralize them
Have a mission to contribute the modules to Ansible proper and remove
them from this repository when they are accepted
If the development community feels this should be not be part of theforeman
proper then so be it and I will manage them on my own. But, I ask that we
weigh the value that this could add to the community at large.
I'm +1 for this. We have the same structure for the Puppet modules, in that we
maintain them and then release them on the Forge, and I see no reason why we
can't do the same for Ansible. It's not like there's an upper limit on how
many repos our GitHub organisation can have, so I don't see any downsides
Does this mean that it's one repository for all modules or one
repository per module? I'm fine either way, just want to curious.
···
On Wed, Apr 05, 2017 at 11:04:24AM -0400, Eric D Helms wrote:
> Howdy,
>
> I have a number of Ansible modules that I have developed for managing
> Katello entities and Foreman organizations. An Ansible module can be
> thought of as providing extentsibility and new functionality to Ansible
> roles and playbooks. In this case, by being able to manage entities within
> Foreman and Katello. There are also a number of modules I have seen upon
> google search that exist for other various Foreman entities.
>
> I would like to share the modules I have written and encourage other
> community users to share theirs in a centralized place for use. Ideally,
> these modules would be offered to and go into Ansible's core set of modules
> after some time of development. However, I believe they need somewhere
> useful to live during said transition and as a place to harden them before
> offering them up and awaiting an Ansible release.
>
> Thus, I would like to propose and request a repository on theforeman Github
> organization named 'foreman-ansible-modules' as a place for these to live.
> The goals of the repository would be:
I think this is a great idea, being able to configure and populate multiple
Katello servers from a git repository is something I'm going to be doing in
a couple of months and this sound perfect for it!
···
On Wed, 5 Apr 2017 at 16:04, Eric D Helms wrote:
Howdy,
I have a number of Ansible modules that I have developed for managing
Katello entities and Foreman organizations. An Ansible module can be
thought of as providing extentsibility and new functionality to Ansible
roles and playbooks. In this case, by being able to manage entities within
Foreman and Katello. There are also a number of modules I have seen upon
google search that exist for other various Foreman entities.
I would like to share the modules I have written and encourage other
community users to share theirs in a centralized place for use. Ideally,
these modules would be offered to and go into Ansible’s core set of modules
after some time of development. However, I believe they need somewhere
useful to live during said transition and as a place to harden them before
offering them up and awaiting an Ansible release.
Thus, I would like to propose and request a repository on theforeman
Github organization named ‘foreman-ansible-modules’ as a place for these to
live. The goals of the repository would be:
House Ansible modules for managing Foreman and Katello entities
Encourage other community users to add in their own to centralize them
Have a mission to contribute the modules to Ansible proper and remove
them from this repository when they are accepted
If the development community feels this should be not be part of
theforeman proper then so be it and I will manage them on my own. But, I
ask that we weigh the value that this could add to the community at large.
> > Howdy,
> >
> > I have a number of Ansible modules that I have developed for managing
> > Katello entities and Foreman organizations. An Ansible module can be
> > thought of as providing extentsibility and new functionality to Ansible
> > roles and playbooks. In this case, by being able to manage entities
> within
> > Foreman and Katello. There are also a number of modules I have seen upon
> > google search that exist for other various Foreman entities.
> >
> > I would like to share the modules I have written and encourage other
> > community users to share theirs in a centralized place for use. Ideally,
> > these modules would be offered to and go into Ansible's core set of
> modules
> > after some time of development. However, I believe they need somewhere
> > useful to live during said transition and as a place to harden them
> before
> > offering them up and awaiting an Ansible release.
> >
> > Thus, I would like to propose and request a repository on theforeman
> Github
> > organization named 'foreman-ansible-modules' as a place for these to
> live.
> > The goals of the repository would be:
>
> Does this mean that it's one repository for all modules or one
> repository per module? I'm fine either way, just want to curious.
>
I'd prefer one repository for all modules otherwise this could mean a lot
of repositories and if a users wants to use them they have to download each
and every one vs cloning a single repo.
···
On Thu, Apr 6, 2017 at 2:02 PM, Ewoud Kohl van Wijngaarden < ewoud@kohlvanwijngaarden.nl> wrote:
> On Wed, Apr 05, 2017 at 11:04:24AM -0400, Eric D Helms wrote:
