I just want to let you know that there's a public formula (like a
Puppet's modules) which can be used to deploy Foreman with all (most of)
its components around:
CLI packages
compute providers
Foreman plugins
Foreman web frontend
Foreman Smart Proxy
Use of Foreman Installer (kafo-based)
The are also additional formulas available to setup httpd (+passenger),
ISC dhcp, BIND, tftpd, libvirt, postgres and more.
If you have any feature requests, feel free to file issues on Github.
@Foreman team: Maybe it would be helpful for users to set a link to the
Foreman formula in the documentation, /quickstart_guide.html maybe?
I also plan to create several screencasts how to setup an infrastructure
with Foreman and the infrastructure itself in the future to explain what
the formulas do.
Interesting, the plan is to deploy Foreman with Saltstack, and replace all
Foreman Installer Recipes with Salt Formulas but nodes would still be
managed by Puppet?
Are you doing this 'just because you can or because there's some use case
I'm missing here? It strikes me as odd that you use one configuration
management system (Saltstack) to deploy Foreman and a different one
(Puppet/Chef) to manage the nodes.
···
On Mon, Jun 23, 2014 at 5:02 PM, Arnold Bechtoldt wrote:
Hey guys,
I just want to let you know that there’s a public formula (like a
Puppet’s modules) which can be used to deploy Foreman with all (most of)
its components around:
CLI packages
compute providers
Foreman plugins
Foreman web frontend
Foreman Smart Proxy
Use of Foreman Installer (kafo-based)
The are also additional formulas available to setup httpd (+passenger),
ISC dhcp, BIND, tftpd, libvirt, postgres and more.
If you have any feature requests, feel free to file issues on Github.
@Foreman team: Maybe it would be helpful for users to set a link to the
Foreman formula in the documentation, /quickstart_guide.html maybe?
I also plan to create several screencasts how to setup an infrastructure
with Foreman and the infrastructure itself in the future to explain what
the formulas do.
> Interesting, the plan is to deploy Foreman with Saltstack, and replace
> all Foreman Installer Recipes with Salt Formulas but nodes would still
> be managed by Puppet?
No, actually I don't use a single code of Puppet in my (own)
infrastructure. Foreman is used to deploy bare metal hosts and soon VMs
via the OpenNebula compute provider too.
> It strikes me as odd that you use one
> configuration management system (Saltstack) to deploy Foreman and a
> different one (Puppet/Chef) to manage the nodes.
Interesting, the plan is to deploy Foreman with Saltstack, and replace
all Foreman Installer Recipes with Salt Formulas but nodes would still
be managed by Puppet?
Are you doing this 'just because you can or because there’s some use
case I’m missing here? It strikes me as odd that you use one
configuration management system (Saltstack) to deploy Foreman and a
different one (Puppet/Chef) to manage the nodes.
Hey guys,
I just want to let you know that there's a public formula (like a
Puppet's modules) which can be used to deploy Foreman with all (most of)
its components around:
* CLI packages
* compute providers
* Foreman plugins
* Foreman web frontend
* Foreman Smart Proxy
* Use of Foreman Installer (kafo-based)
The are also additional formulas available to setup httpd (+passenger),
ISC dhcp, BIND, tftpd, libvirt, postgres and more.
You can (hopefully) find everything you need at
=> <https://github.com/bechtoldt/>
If you have any feature requests, feel free to file issues on Github.
@Foreman team: Maybe it would be helpful for users to set a link to the
Foreman formula in the documentation, /quickstart_guide.html maybe?
I also plan to create several screencasts how to setup an infrastructure
with Foreman and the infrastructure itself in the future to explain what
the formulas do.
Best regards,
Arnold
--
Arnold Bechtoldt
Karlsruhe, Germany
