I have a foreman-installer Ansible role[1], its really flexible and works
by merging a hash of custom parameters with the default ones defined in the
scenario's answer file.
I would quite like to move it to theforeman Github organisation and publish
it in Ansible galaxy under TheForeman name if people agree ?
My use case was for configuring a foreman cluster.
> Hey guys!
>
> I have a foreman-installer Ansible role[1], its really flexible and works by
> merging a hash of custom parameters with the default ones defined in the
> scenario's answer file.
> I would quite like to move it to theforeman Github organisation and publish
> it in Ansible galaxy under TheForeman name if people agree ?
>
> My use case was for configuring a foreman cluster.
> > Hey guys!
> >
> > I have a foreman-installer Ansible role[1], its really flexible and works by
> > merging a hash of custom parameters with the default ones defined in the
> > scenario's answer file.
> > I would quite like to move it to theforeman Github organisation and publish
> > it in Ansible galaxy under TheForeman name if people agree ?
> >
> > My use case was for configuring a foreman cluster.
>
> There is one in Forklift already:
> https://github.com/theforeman/forklift/tree/master/playbooks/roles/foreman_installer
>
> If there's features that yours has that this one doesn't maybe we could merge
> them together and then release it on Ansible galaxy.
Also have a look at the pipelines. There are some deployments, but we
could use more complex multi host setups. Combined with the
foreman_installer_module_prs parameter you can easily test complex
puppet module PRs or PRs that so any common deployment should be there.
My goal is a scenario where we have one service per VM.
···
On Thu, May 18, 2017 at 10:33:41AM -0400, Stephen Benjamin wrote:
> On Thu, May 18, 2017 at 7:57 AM, Sean O'Keeffe wrote: