Ok, so now you have connected Foreman with VMware and want to start creating Linux VMs.
Foreman can create hosts on VMware but even if you won´t do so, Foreman and VMware integration still worth it since it can delete, power on/off VMs and even get Console Access via VMRC.
Foreman already comes with Puppet. In fact, when you run foreman-installer it uses Puppet to install and configure Foreman.
Even if you won´t manage servers with Puppet, it´s useful to install the Puppet agent on all hosts connected to Foreman so you´ll have reports and inventory.
Here we´ll talk about adding hosts to the Puppet Server running on Foreman.
Foreman has a bunch of plugins but none of them can be compared to Katello, a plugin that is so big, so big, that it changes the way you install and configure Foreman.
Katello is a “plugin” to manage CentOS and RedHat repositories, mirroring content and managing updates and erratas. This is called content management.
In fact, Satellite is the paid and suported version of Foreman/Katello by RedHat, but it suports only RedHat systems while the upstream Foreman/Katello suports both RedHat and CentOS.
The Foreman is a great tool. It´s a complete lifecycle manager for physical, virtual and cloud servers.
It does configuration management and orchestration with Puppet, Chef, Salt and Ansible.
It does server provisioning on almost all of the cloud providers, virtualization solutions and even bare metal.
When combined with the Katello plugin, it becomes what RedHat sells as RedHat Satellite 6, a complete system to manage updates, erratas, security patches and compliance and provisioning of Linux systems.
Let´s install The Foreman with the Katello plugin.
Proceed only if you have your lab up and running and will start with Foreman now.
My lab environment.
You can run your lab in the Cloud as I used to do so until few months ago when most of the things I needed to test was related to VMware.
So, I bought two HP z800 workstations, with two Xeon six core and 96Gb of ram each. I needed this resources because I was testing the automation of ESXi Host installation itself, and running many of then inside the physical ESXi hosts – nested virtualization. But you won´t need this much unless you want to do the same.