Registering Hosts

In the orcharhino management UI, navigate to Hosts > Register Host.

Optional: Select a different Organization.

Optional: Select a different Location.

Optional: From the Host Group list, select the host group to associate the hosts with. Fields that inherit value from Host group: Operating system, Activation Keys and Lifecycle environment.

Optional: From the Operating system list, select the operating system of hosts that you want to register.

Optional: From the orcharhino Proxy list, select the orcharhino Proxy to register hosts through.

Optional: Select the Insecure option, if you want to make the first call insecure. During this first call, hosts download the CA file from orcharhino. Hosts will use this CA file to connect to orcharhino with all future calls making them secure.

$ update-ca-trust enable
$ update-ca-trust

$ curl -sS https://orcharhino.example.com/register ...

$ curl -sS --insecure https://orcharhino.example.com/register ...

Select the Advanced tab.

From the Setup REX list, select whether you want to deploy orcharhino SSH keys to hosts or not.

Optional: In the Install packages field, list the packages (separated with spaces) that you want to install on the host upon registration. This can be set by the host_packages parameter.

Optional: Select the Update packages option to update all packages on the host upon registration. This can be set by the host_update_packages parameter.

Optional: In the Repository field, enter a repository to be added before the registration is performed. For example, it can be useful to make the subscription-manager package available for the purpose of the registration. For SUSE Linux Enterprise Server, enter the path to the orcharhino Client for SUSE Linux Enterprise Server repository, for example http://orcharhino.example.com/pulp/content/Example/Library/custom/suse_linux_enterprise_server_client/suse_linux_enterprise_server_client/.

Optional: In the Repository GPG key URL field, specify the public key to verify the signatures of GPG-signed packages. It needs to be specified in the ASCII form with the GPG public key header.

Optional: In the Token lifetime (hours) field, change the validity duration of the JSON Web Token (JWT) that orcharhino uses for authentication. The duration of this token defines how long the generated curl command works. You can set the duration to 0 – 999 999 hours or unlimited.

Optional: In the Remote Execution Interface field, enter the identifier of a network interface that hosts must use for the SSH connection. If you keep this field blank, orcharhino uses the default network interface.

From the REX pull mode list, select whether you want to deploy orcharhino remote execution pull client.

In the Activation Keys field, enter one or more activation keys to assign to hosts.

Optional: Select the Lifecycle environment.

Optional: Select the Ignore errors option if you want to ignore subscription manager errors.

Optional: Select the Force option if you want to remove any katello-ca-consumer rpms before registration and run subscription-manager with the --force argument.

Click the Generate button.

Copy the generated curl command.

On the hosts that you want to register, run the curl command as root.

Download the bootstrap.py script using wget:

$ wget https://orcharhino.example.com/pub/bootstrap.py

Use the --help option to display a list of mandatory options:

$ python bootstrap.py --help

Register an existing host to orcharhino:

$ ./bootstrap.py \
--fqdn "my-host.example.com" \
--skip "puppet" \
-L "Munich" \
-a "suse_linux_enterprise_server" \
-g "SUSE Linux Enterprise Server" \
-l "admin" \
-o "Example" \
-p "password" \
--deps-repository-url https://orcharhino.example.com/pulp/content/Example/Library/custom/suse_linux_enterprise_server_Client/suse_linux_enterprise_server_15/ \
--deps-repository-gpg-key file:///etc/pki/rpm-gpg/RPM-GPG-KEY-kt-bootstrap \
-s "orcharhino.example.com"

Install sudo on your managed host:

$ zypper install -y sudo

Add your custom user:

$ useradd -m My_Custom_User

Set up SSH for your custom user:

$ mkdir -p ~My_Custom_User/.ssh
$ chmod 0700 ~My_Custom_User/.ssh
$ chown -R My_Custom_User: ~My_Custom_User/.ssh

Add your custom user to the sudoers file:

$ echo "My_Custom_User ALL = (root) NOPASSWD : ALL" >> /etc/sudoers
$ echo "Defaults:_My_Custom_User_ My_Custom_User_Password" >> /etc/sudoers

Run the bootstrap.py script:

$ ./bootstrap.py --force

Navigate to Hosts > All Hosts and select your host.

In the Select Action menu, click Disassociate Hosts.

Navigate to Infrastructure > Compute Resources and select your compute resource.

Click Associate VMs.

In case your orcharhino Server or orcharhino Proxies run on the same compute resource, disassociate the VMs on the All Hosts page again.

Add a repository containing the subscription-manager package:

$ zypper addrepo -G --check "http://orcharhino.example.com/pulp/repos/My_Organization/Library/custom/SLES_Client/SLES_Client_15SP5/" or_sles_client

Install the subscription-manager:

$ zypper --non-interactive --no-gpg-checks --quiet install --auto-agree-with-licenses subscription-manager

Install a package from your orcharhino bundling all necessary certificates:

$ rpm -ivh http://orcharhino.example.com/pub/katello-ca-consumer-latest.noarch.rpm

Register your host with an activation key:

$ subscription-manager register --org="My_Organization" --name="sles15sp5.example.com" --activationkey="My_SLES15SP5_Activation_Key"

Install the katello-host-tools:

$ zypper --non-interactive --no-gpg-checks --quiet install --auto-agree-with-licenses katello-host-tools

To use remote execution, add the SSH public key from orcharhino Server. For more information, see Adding SSH Keys for Remote Execution.

Create the required directory:

$ mkdir -p ~root/.ssh

Add the SSH public key from your orcharhino:

$ cat << EOF >> ~root/.ssh/authorized_keys
ssh-rsa My_SSH_Public_Key foreman-proxy@orcharhino.example.com
EOF

On your managed hosts, view the MAC address, IP address, and device identifier of the network interface providing a connection to your orcharhino:

$ ip a

Navigate to Hosts > All Hosts, select your host, and click Edit.

On the Interfaces tab, click Edit and enter the MAC address, IPv4 address, and the device identifier.

Click Submit to save your changes.

Navigate to Hosts > All hosts and tick the checkbox of your host.

In the Select Action drop down menu, click Disassociate Hosts.

Navigate to Infrastructure > Compute Resources and select the compute resource your host runs on.

On the Compute Resources tab, click Associate VMs.

Optional: Navigate to Hosts > All Hosts, select your host, and verify your change by changing the power status of the host.

If you have Remote Execution configured to use ssh mode, distribute the remote execution SSH keys to the hosts. For more information, see Distributing SSH Keys for Remote Execution.

If you have Remote Execution configured to use pull-mqtt mode, deploy the remote execution pull client to the hosts. For more information, see Configuring a Host to Use the Pull Client.

Stop the goferd service on content hosts:

$ systemctl stop goferd

Disable the goferd service on content hosts:

$ systemctl disable goferd

Remove the Katello agent on content hosts:

$ dnf remove katello-agent

In the orcharhino management UI, navigate to Administer > Settings.

Select the Content tab.

Set the Use remote execution by default parameter to Yes.