After installation of Katello, navigate to the /pub
directory and trust Katello’s CA certificate for identifying web sites (e.g. http://katello.example.com/pub/katello-server-ca.crt
).
Katello does not currently support installation on existing Foreman deployments. DO NOT attempt to install Katello on an existing Foreman deployment, unless you are a Foreman developer and willing to debug the broken configuration that will result from attempting an install on existing system.
Katello may be installed onto a baremetal host or on a virtual guest. The minimum requirements are:
The following ports need to be open to external connections:
Katello provides a Puppet based installer for deploying production installations. Production installations are supported on the following operating systems:
Installation may be done manually or via our recommended approach of using forklift.
Select your Operating System:
After setting up the appropriate repositories, update your system:
Then install Katello:
At this point the foreman-installer
should be available to setup the server. The installation may be customized, to see a list of options:
Note
Prior to running the installer, the machine should be set up with a time service such as ntpd or chrony, since several Katello features will not function well if there is minor clock skew.
These may be set as command line options or in the answer file (/etc/foreman-installer/scenarios.d/katello-answers.yaml). Now run the options:
The installer only supports one subnet and one DNS domain via command line arguments. Multiple entries can be entered via /etc/foreman-installer/custom-hiera.yaml file:
dhcp::pools:
isolated.lan:
network: 192.168.99.0
mask: 255.255.255.0
gateway: 192.168.99.1
range: 192.168.99.5 192.168.99.49
dns::zones:
# creates @ SOA $::fqdn root.example.com.
# creates $::fqdn A $::ipaddress
example.com: {}
# creates @ SOA test.example.net. hostmaster.example.com.
# creates test.example.net A 192.0.2.100
example.net:
soa: test.example.net
soaip: 192.0.2.100
contact: hostmaster.example.com.
# creates @ SOA $::fqdn root.example.org.
# does NOT create an A record
example.org:
reverse: true
# creates @ SOA $::fqdn hostmaster.example.com.
2.0.192.in-addr.arpa:
reverse: true
contact: hostmaster.example.com.
The Foreman installer supports automatic tuning of your environment using predefined tuning profiles. These tuning profiles are the result of a culmination of extensive learning from Foreman environments deployed at scale in large user environments.
When the foreman-installer is run, it is deployed with a default
predefined tuning profile. Other than the default tuned profile, foreman-installer supports 4 different tuning profiles:
Based on your environment needs, use one of the tuning profiles (medium
, large
, extra-large
, extra-extra-large
) in the installer. For example, medium
profile can be applied like:
foreman-installer --tuning medium
To reset to the default profile:
foreman-installer --tuning default
Use foreman-installer --help | grep tuning
to identify the current tuning level.
Sample output for medium
tuning:
foreman-installer --help | grep tuning
--tuning INSTALLATION_SIZE Tune for an installation size. Choices: default, medium, large, extra-large, extra-extra-large (default: "medium")
Sample output for default
tuning:
foreman-installer --help | grep tuning
--tuning INSTALLATION_SIZE Tune for an installation size. Choices: default, medium, large, extra-large, extra-extra-large (default: "default")
Note
/usr/share/foreman-installer/config/foreman.hiera/tuning/sizes/
. Note that common.yaml
is always applied and the selected tuning profile (e.g., medium
) is applied on top and takes precedence.--tuning
option does not update /etc/foreman-installer/custom-hiera.yml
, instead it directly updates the required configuration as specified in the corresponding tuning profile. You can still use custom-hiera.yml
to override any configuration if really needed.custom-hiera.yml
and starting to use the tuned profiles, you may want to review the definition of tuned profiles (/usr/share/foreman-installer/config/foreman.hiera/tuning/common.yaml
and /usr/share/foreman-installer/config/foreman.hiera/tuning/sizes/
) and remove the duplicated configuration entries from your custom-hiera.yml
.foreman-installer --tuning <profile> --noop
to run the installer in a test mode and identify what configurations will be changed before actually running the installer.It is difficult to find the exact tuning profile for a specific environment in the first attempt because it depends on various factors like the number of managed hosts, the features used in scale (E.g., Remote Execution), the bulk actions on hosts, the total amount of content, amount of host traffic to foreman, etc. Our recommendation is that you start with the tuning profile guidance as shown in the below table based on the number of managed hosts and scale up your environment as needed.
Note
disable-system-checks
if you like to skip this check in the installer.Tuned profile | Number of Managed hosts | Minimum Recommended RAM | Minimum Recommended CPU Cores |
---|---|---|---|
default | up-to 5000 | 20G | 4 |
medium | 5000 - 10000 | 32G | 8 |
large | 10000 - 20000 | 64G | 16 |
extra-large | 20000 - 60000 | 128G | 32 |
extra-extra-large | 20000 - 60000 | 256G | 48 |
Foreman provides a git repository designed to streamline setup by setting up all the proper repositories. Forklift provides the ability to deploy a virtual machine instance via Vagrant or direct deployment on an already provisioned machine. For details on how to install using forklift, please see the README.
Foreman 3.12.0 has been released! Follow the quick start to install it.
Foreman 3.11.2 has been released! Follow the quick start to install it.