Client machines can be added in one of two ways: manually or via a provisioned host.
Install the appropriate Katello client release packages. For CentOS 6, you will also need to enable the COPR repository for subscription-manager.
Select your Operating System:
Now you are ready to install the client package:
katello-host-tools package reports errata & package profile information, but does not allow you to run remote actions on the clients.
We generally recommend using Foreman Remote Execution or Ansible for remote actions, but we also offer a messaging bus based client that does have some limitations when used with a large number of clients.
Optionally you can also install
katello-host-tools-tracer and the client will report processes that need restarting after an update back to the Katello server.
For Suse Clients, only katello-host-tools is supported:
In order to install the katello-agent package on a host you are provisioning, you will need to make the appropriate client repository available within your Katello. The first step is to either create a new product or add to an existing product, the appropriate client repository from the dropdown in the manual section above. After you create the new repositories, they will need to be synced locally. Next, you will then need to add them to the relevant content view(s) for the hosts you are wanting to provision. At this point, a new version of the content view can be published and promoted to the appropriate environments that you are wanting to provision a host into. At this point, you can go provision a host and the host will install the katello-agent package during setup.
When provisioning new clients that should use Puppet 4, set a parameter called ‘enable-puppet4’ to ‘true’, so the templates know which package to install and where to place the configuration. This parameter can be placed at the host, host group, or another appropriate level of the hierarchy.