Some time ago there was a discussion about having an (alternative) Ansible based
foreman-installer. Is someone still interested in such an implementation? I
don't want to advertise our playbook [1] but it already provides a good baseline
and we would be more than happy to contribute and improve it.
I'm aware that maintaining 2 installers requires additional work but from my
point of view it would be a great enhancement to give users the freedom and
possibility to choose between them, especially as bigger projects (e.g.
Openshift, also supported by Red Hat) are now using Ansible as a deployment
tool.
We would be more than happy to contribute and help improve it (e.g. more
functionality, Ansible guidelines, documentation, change the license if required
etc.).
···
On Mon, Mar 13, 2017 at 3:22 PM, Michael Hofer < michael.hofer@adfinis-sygroup.ch> wrote:
Hi all
Some time ago there was a discussion about having an (alternative) Ansible
based
foreman-installer. Is someone still interested in such an implementation? I
don’t want to advertise our playbook [1] but it already provides a good
baseline
and we would be more than happy to contribute and improve it.
I’m aware that maintaining 2 installers requires additional work but from
my
point of view it would be a great enhancement to give users the freedom and
possibility to choose between them, especially as bigger projects (e.g.
Openshift, also supported by Red Hat) are now using Ansible as a deployment
tool.
We would be more than happy to contribute and help improve it (e.g. more
functionality, Ansible guidelines, documentation, change the license if
required
etc.).
> Hi all
>
> Some time ago there was a discussion about having an (alternative) Ansible
> based
> foreman-installer. Is someone still interested in such an implementation? I
> don't want to advertise our playbook [1] but it already provides a good
> baseline
> and we would be more than happy to contribute and improve it.
>
> [1] GitHub - adfinis/foreman-ansible: Ansible playbook to deploy a complete Foreman instance within minutes.
>
> I'm aware that maintaining 2 installers requires additional work but from
> my
> point of view it would be a great enhancement to give users the freedom and
> possibility to choose between them, especially as bigger projects (e.g.
> Openshift, also supported by Red Hat) are now using Ansible as a deployment
> tool.
>
> We would be more than happy to contribute and help improve it (e.g. more
> functionality, Ansible guidelines, documentation, change the license if
> required
> etc.).
>
> What do you think?
>
Would you be interested in doing a deep dive about the installer? what it
currently does, how to use it etc?
I think it would be interesting to our increasing ansible users community.
thanks!
Ohad
···
On Mon, Mar 13, 2017 at 9:22 PM, Michael Hofer < michael.hofer@adfinis-sygroup.ch> wrote:
This is interesting indeed for those which are not super-comfortable
with using Puppet (e.g. me
Now the big question, does it install Katello?
I see it configures passenger and passenger-ngix external
repositories. Does it also work with passenger from EPEL?
Is there something which is preventing from SELinux running in enforcing?
I'd also love to see demo. It will be really lot of work to put this
on par with our puppet installer, we have a super nice CLI (kafo) for
example.
···
On Mon, Mar 13, 2017 at 8:22 PM, Michael Hofer wrote:
> Hi all
>
> Some time ago there was a discussion about having an (alternative) Ansible based
> foreman-installer. Is someone still interested in such an implementation? I
> don't want to advertise our playbook [1] but it already provides a good baseline
> and we would be more than happy to contribute and improve it.
>
> [1] https://github.com/adfinis-sygroup/foreman-ansible
>
> I'm aware that maintaining 2 installers requires additional work but from my
> point of view it would be a great enhancement to give users the freedom and
> possibility to choose between them, especially as bigger projects (e.g.
> Openshift, also supported by Red Hat) are now using Ansible as a deployment
> tool.
>
> We would be more than happy to contribute and help improve it (e.g. more
> functionality, Ansible guidelines, documentation, change the license if required
> etc.).
>
> What do you think?
>
> Cheers
>
> Michael
>
> --
> You received this message because you are subscribed to the Google Groups "foreman-dev" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to foreman-dev+unsubscribe@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.
[…]
> Would you be interested in doing a deep dive about the installer? what it
> currently does, how to use it etc?
>
> I think it would be interesting to our increasing ansible users community.
[…]
Sure, why not!
Would that be a topic for a community demo?
Michael
···
On Tue, 14 Mar 2017 08:45:19 +0200 Ohad Levy wrote:
> This is interesting indeed for those which are not super-comfortable
> with using Puppet (e.g. me
>
> Now the big question, does it install Katello?
>
> I see it configures passenger and passenger-ngix external
> repositories. Does it also work with passenger from EPEL?
>
> Is there something which is preventing from SELinux running in enforcing?
Thanks for the feedback! I've just created some issues to keep track of your
input. Currently there's no role to deploy Katello and no flag to deploy
passenger from EPEL. Regarding SELinux I haven't done much testing, thus the
note in the README but it's on the issue list.
> I'd also love to see demo. It will be really lot of work to put this
> on par with our puppet installer, we have a super nice CLI (kafo) for
> example.
[…]
Sure, I'd be happy to present the playbook. Would this be interesting enough
for a community demo or what do you have in mind?
Michael
···
On Tue, 14 Mar 2017 19:32:11 +0100 Lukas Zapletal wrote:
We can do it either way (or both!). Community demo items tend to be short
(5-10 mins tops) and stay at a high level. Deep dives obviously have more time
to get into the details.
I'd suggest a dedicated deep dive to start with, and then you'll always be
welcome to join the regular demos to show off latest developments in the
Ansible installer.
If that works for you, I'll ping you offlist to sort out a date & time for the
deep dive.
Greg
···
On Tuesday, 14 March 2017 18:16:59 GMT Michael Hofer wrote:
> Hi Ohad
>
> On Tue, 14 Mar 2017 08:45:19 +0200 > Ohad Levy wrote:
> [...]
>
> > Would you be interested in doing a deep dive about the installer? what it
> > currently does, how to use it etc?
> >
> > I think it would be interesting to our increasing ansible users community.
>
> [...]
>
> Sure, why not! :)
>
> Would that be a topic for a community demo?
[…]
> We can do it either way (or both!). Community demo items tend to be short
> (5-10 mins tops) and stay at a high level. Deep dives obviously have more
> time to get into the details.
>
> I'd suggest a dedicated deep dive to start with, and then you'll always be
> welcome to join the regular demos to show off latest developments in the
> Ansible installer.
>
> If that works for you, I'll ping you offlist to sort out a date & time for
> the deep dive.
Sounds good, feel free to ping me.
Michael
···
On Thu, 16 Mar 2017 12:55:15 +0000 Greg Sutcliffe wrote:
