Chapter 6. Content Distribution Server (CDS) Instances

The CDS Management screen is used to list, add, and delete content distribution server (CDS) instances. From this screen, you can also access the CDS Repository Management screen, which allows you to view and change information for individual CDS instances.
To access the CDS Management screen, go to the Home screen and type c at the prompt:
rhui (home) => c 

------------------------------------------------------------------------------
             -= Red Hat Update Infrastructure Management Tool =-


-= Content Delivery Server (CDS) Management =-

   l   list all CDS instances registered to the RHUI
   a   register (add) a new CDS instance
   d   unregister (delete) a CDS instance from the RHUI

                                   Connected: rhua.example.com
------------------------------------------------------------------------------
rhui (cds) =>

Procedure 6.1. List CDS instances

  • From the CDS Management screen, type l at the prompt to list the CDS instances currently being managed by the RHUI:
    rhui (cds) => l
    
    -= RHUI Content Delivery Servers =-
    
      US East Region CDS
      US West Region CDS
    
    ------------------------------------------------------------------------------
    rhui (cds) =>
    

Procedure 6.2. Add a CDS Instance

  1. From the CDS Management screen, type a at the prompt to add a new CDS instance:
    rhui (cds) => a
    
  2. Important

    Ensure that the CDS you are adding is configured and running. If the CDS is not running before you try to register it, the registration will fail.
    Enter the hostname of the CDS to added. This must match the hostname configured on the CDS itself. You cannot use the IP address. If the hostname does not match exactly, the operation will fail.
    Prior to registering a CDS, the CDS must be configured and running.
    
    Hostname of the CDS to register:
    cds.us-east.example.com
    
  3. Enter a display name for the CDS. This name is used to identify the CDS within RHUI Manager. Alternatively, leave the field blank to use the hostname as the display name:
    Display name for the CDS [cds.us-east.example.com]:
    US East Region CDS
    
  4. The details of the new CDS will be displayed. Type y at the prompt to confirm the information and create the CDS:
    The following CDS instance will be registered:
      Hostname: cds.us-east.example.com
      Name:     US East Region CDS
    Proceed? (y/n) y
    
    Successfully registered US East Region CDS
    
    ------------------------------------------------------------------------------
    rhui (cds) =>
    

    Note

    If adding the CDS fails, check that the CDS daemon pulp-cds is running and that the firewall rules permit access between the RHUA and the CDS.

Procedure 6.3. Delete a CDS Instance

Warning

When a CDS is deleted, all of the repositories and data will be lost. It is important that RHUI Manager can access the CDS to ensure that content is no longer being hosted from the CDS instance before it is deleted.
  1. From the CDS Management screen, type d at the prompt to delete a CDS instance:
    rhui (cds) => d
    
  2. A list of all CDS instances currently being managed by the RHUI will be displayed. Select which CDS instances to delete by typing the number of the CDS at the prompt. Typing the number of a CDS will place a checkmark next to the name of that CDS. Continue until all CDS instances you wish to delete have been checked, and then type c at the prompt to confirm:
    	Select the CDS instances to be removed from the RHUI: 
      -  1 : US East Region CDS
    Enter value from (1-1) to toggle selection, 'c' to confirm selections, or '?'
    for more commands: 1
    
    Select the CDS instances to be removed from the RHUI: 
      x  1 : US East Region CDS
    Enter value from (1-1) to toggle selection, 'c' to confirm selections, or '?'
    for more commands: c
    
  3. A list of the CDS instances to be deleted will be displayed. Type y at the prompt to confirm the selection and delete the CDS instances:
    The following CDS instances will be unregistered:
      US East Region CDS
    Proceed? (y/n) y
    
    Unregistering US East Region CDS...
    
    ------------------------------------------------------------------------------
    rhui (cds) =>
    
  4. RHUI Manager contacts the CDS to ensure it is properly cleaned up when it is deleted. RHUI Manager is unable to delete a CDS instance that it cannot communicate with. However, there are some cases where you might need to remove an unresponsive CDS instance.

    Important

    CDS instances exchange a secret with the RHUA so that only the RHUA is able to communicate with it. This secret is removed as part of the cleanup operation when a CDS is deleted normally. When a CDS instance is forcibly removed without being properly cleaned up, this secret is not deleted. You will not be able to register the CDS again until that secret has been removed. You can do this manually by deleting the /var/lib/pulp-cds/.gofer/secret file.
    When you attempt to perform a delete operation on a CDS instance that is not running, RHUI Manager will notify you that it is unable to delete the CDS, and ask if you want to forcibly remove the CDS. Type y to forcibly remove the unresponsive CDS:

    Warning

    Be very careful with this command. If you delete a CDS instance that is not running, RHUI Manager cannot confirm that the CDS instance is not hosting repositories that have previously been deployed.
    ------------------------------------------------------------------------------
    rhui (cds) => d
    
    Select the CDS instances to be removed from the RHUI: 
      -  1 : CDS 1
    Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for
    more commands: 1
    
    Select the CDS instances to be removed from the RHUI: 
      x  1 : CDS 1
    Enter value (1-1) to toggle selection, 'c' to confirm selections, or '?' for
    more commands: c
    
    
    All previously deployed repositories will be deleted when a CDS is
    unregistered.
    
    The following CDS instances will be unregistered:
      CDS 1
    Proceed? (y/n) y
    
    
    Unregistering CDS 1...
    
    The following CDS instances could not be contacted to be unregistered.
    They may still be removed from the RHUI database, however the RHUI is unable
    confirm that they have stopped hosting repositories.
      CDS 1
    
    Forcibly remove these CDS instances? (y/n)y
    
    Forcibly unregistering CDS 1...