Chapter 6. Managing content delivery servers
Chapter 6. Managing content delivery servers CDS nodes provide content to RHUI clients. You can use the Content Delivery Server (CDS) Management screen to list, add, delete, and reinstall CDS nodes. 6.1. Registering a new CDS The Red Hat Update Infrastructure Management Tool provides several options for configuring a CDS within the RHUI. Prerequisites Make sure sshd is running on the CDS node and that port 443 is open. Note Answering yes (y) to the below question: Update instance(s) after reinstalling? (y/n): will result in a dnf update being run on the instance after it is registered. This may require a reboot of the instance. Answering no (n) to this question will result in the dnf update not being run. Procedure Navigate to the Red Hat Update Infrastructure Management Tool home screen: Press c to select manage content delivery servers (CDS) . From the Content Delivery Server (CDS) Management screen, press a to add a new CDS instance. Enter the hostname of the CDS to add: Enter the user name that will have SSH access to the CDS and have sudo privileges. Enter the absolute path to the SSH private key for logging in to the CDS and press Enter . Update the instance with the latest versions of available packages Optional: If you wish to use custom SSL certificates, enter the absolute path to the custom SSL certificate, SSL Key, and SSL crt files. Note If you do not provide an SSL certificate, it will be automatically generated. If adding the content delivery server fails, check that the firewall rules permit access between the RHUA and the CDS. Run the mount command to see if shared storage is mounted as read-write. After successful configuration, repeat these steps for all remaining CDS nodes. 6.2. Listing all known CDS instances managed by RHUI 4 You can use the Content Delivery Server (CDS) Management screen to list all CDS nodes managed by Red Hat Update Infrastructure 4. Procedure Navigate to the Red Hat Update Infrastructure Management Tool home screen: Press c to select manage content delivery servers (CDS) : From the Content Delivery Server (CDS) Management screen, press l to list all known CDS nodes that Red Hat Update Infrastructure 4 manages: 6.3. Reinstalling and reapplying configuration to a CDS You may encounter a situation where you need to reinstall and reapply the configuration for a CDS. The Red Hat Update Infrastructure Management Tool provides an easy way to accomplish this task. Prerequisites At least one installed CDS Note Answering yes (y) to the below question: Update instance(s) after reinstalling? (y/n): will result in a dnf update being run on the instance after it is reinstalled. This may require a reboot of the instance. Answering no (n) to this question will result in the dnf update not being run. Procedure Navigate to the Red Hat Update Infrastructure Management Tool home screen: Press c to select manage content delivery servers (CDS) . From the Content Delivery Server (CDS) Management screen, press r to select reinstall and reapply configuration to an existing CDS instance . The Red Hat Update Infrastructure Management Tool automatically performs all reinstallation and reconfiguration tasks. Select the CDS to reinstall: Enter a value or b to abort: 1: 1 Update instance(s) after reinstalling? (y/n): y Verification Check that you successfully reinstalled and reconfigured the CDS by viewing the code output: 6.4. Configuring a CDS to accept legacy CAs By default, a content delivery server (CDS) node only accepts entitlement certificates signed by the Certificate Authority (CA) that is currently configured on your RHUI system. However, you might want to accept previously created CAs so that clients can continue to work in case you change your main CA or when the CA certificate expires. This procedure provides instructions to support legacy CAs on RHUI by installing CA certificates on your CDS nodes. Prerequisites Ensure you are running the latest version of RHUI. Note If you have installed an older version of RHUI, you must reinstall your CDS nodes in rhui-manager . Procedure On the CDS node, create the /etc/pki/rhui/legacy directory if it does not already exist: Save the legacy CA certificate in the directory. Verification The CDS node starts accepting legacy CAs as soon as you store the CA certificate in the directory. 6.5. Configuring a CDS to stop accepting legacy CAs To limit your content delivery servers (CDS) nodes from accepting legacy certificate authorities (CAs), remove the respective CA certificates. Prerequisites Clients are no longer using the CA. Procedure On the CDS node, navigate to the /etc/pki/rhui/legacy/ directory: Optional: Back up the existing CA certificates: Delete the CA certificate that corresponds to the CA you want to limit: Verification The CDS node stops accepting legacy CAs as soon as you delete the CA certificate. 6.6. Unregistering a CDS You can unregister (delete) a CDS instance that you are not going to use. Procedure Navigate to the Red Hat Update Infrastructure Management Tool home screen: Press c to select manage content delivery servers (CDS) . From the Content Delivery Server (CDS) Management screen, press d to delete a CDS instance. Enter the hostname of the CDS to delete:
rhui-manager Hostname of the CDS instance to register: cds1.example.com Username with SSH access to <cds1.example.com> and sudo privileges: <cloud-user> Absolute path to an SSH private key to log into <cds1.example.com> as <cloud-user>: /home/<cloud-user>/.ssh/id_rsa_rhua Update instance after registering? (y/n): y Optional absolute path to user supplied SSL key file: /home/<cloud-user>/custom_ssl.key Optional absolute path to user supplied SSL crt file: /home/<cloud-user>/custom_ssl.crt ...................................................................... The following CDS has been successfully added: Hostname: <cds1.example.com> SSH Username: <cloud-user> SSH Private Key: /home/<cloud-user>/.ssh/id_rsa_rhua The CDS will now be configured: ................................................................. The CDS was successfully configured. mount | grep rhui nfs.example.com:/export on /var/lib/rhui/remote_share type nfs4 (rw,relatime,vers=4.2,rsize=1048576,wsize=1048576,namlen=255,hard,proto=tcp,timeo=600,retrans=2,sec=sys,clientaddr=10.8.41.163,local_lock=none,addr=10.8.41.163) rhui-manager Hostname: <cds1.example.com> SSH Username: <cloud-user> SSH Private Key: /<cloud-user>/.ssh/id_rsa_rhua rhui-manager 1 - Hostname: <cds1.example.com> SSH Username: <cloud-user> SSH Private Key: /<cloud-user>/.ssh/id_rsa_rhua Checking that the RHUA services are reachable from the instance Done. Installing and configuring the CDS PLAY [Registering a CDS instance] ********************************************** TASK [Update CDS instance] ***************************************************** ok: [cds1.example.com] PLAY RECAP ********************************************************************* cloud-user@cds1.example.com : ok=24 changed=10 unreachable=0 failed=0 skipped=2 rescued=0 ignored=0 Done. Ensuring that instance ports are reachable Done. mkdir /etc/pki/rhui/legacy cd /etc/pki/rhui/legacy/ rm example-legacy.crt rhui-manager Hostname of the CDS instance to unregister: cds1.example.com