Let´s install The Foreman, and with a great plugin called Katello. This is what RedHat sells as “RedHat Satellite”, but here is not the place to talk about this software, RLabs is just about about practical HOW-TOs.
Proceed only if you have your lab up and running and will start with Foreman now.
Prepare for installation
You will need a CentOS or RedHat host with 8Gb of ram and two vCpus, at least.
If it will be a VM with LVM, you can start with 20Gb of space. You can get recommended partitioning settings at the official site (nightly release).
You should configure your network interfaces as follow (for the rlabs purposes):
First: 192.168.12.30/24, gateway: 192.168.12.1, DNS: 192.168.12.2
You should have a working DNS on 192.168.12.2 resolving foreman.ext.dc1.lab to 192.168.12.30 and also resolving recursive queries.
hostnamectl set-hostname foreman.ext.dc1.lab
Edit /etc/hosts and make sure you have an IP->hostname entry:
echo "192.168.12.30 foreman.ext.dc1.lab foreman" >> /etc/hosts
Go to https://theforeman.org/plugins/katello/ and click on the latest stable release on the right pane.
Click on the link Installation/Katello on the left pane and follow the instructions.
YES – That´s it. Follow the instructions.
I won´t paste here the instructions to force you to always use the official procedures on the official site, and then I won´t need to update this post everytime a new release is lauched.
You can follow the instructions until you have to run the foreman-installer command.
Options to foreman-installer
Create a file on the root user home with your foreman-installer command and options.
In this lab I used the following options:
foreman-installer --scenario katello \ --foreman-admin-password adminadmin \ --enable-foreman-proxy-plugin-ansible \ --enable-foreman-plugin-discovery \ --enable-foreman-proxy-plugin-discovery \ --foreman-proxy-plugin-discovery-install-images true \ --enable-foreman-plugin-ansible \ --enable-foreman-compute-vmware \ --enable-foreman-compute-ec2 \ --enable-foreman-compute-gce \ --enable-foreman-plugin-remote-execution \ --enable-foreman-proxy-plugin-remote-execution-ssh \ --foreman-initial-location dc1 \ --foreman-initial-organization RLabs \ --foreman-proxy-dns=false
You should adjust as needed.
You should run the Puppet Agent so it will report to the Foreman server:
. /etc/profile && puppet agent -t
If your foreman server is reacheabe only by the internal networks (and it should be so), accept any new puppet agent:
echo "*" >> /etc/puppetlabs/puppet/autosign.conf
Now log in to your foreman server: https://foreman.ext.dc1.lab as admin password adminadmin .