Accessed from the home scren: c manage content delivery servers (CDS) Similar to the Repository Management screen, this screen provides the means to display registered CDS instances, register/unregister instances from the RHUI, and access the CDS Repository Management screen to control the repositories deployed on a specific CDS. Menu: ------------------------------------------------------------------------------ -= 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 r manage repositories hosted on a CDS instance Connected: guardian ------------------------------------------------------------------------------ rhui (cds) =>
Accessed from the menu: l list all CDS instances registered to the RHUI Not much to say here. Lists the display name of all CDS instances registered to the RHUI. Sample: rhui (cds) => l -= RHUI Content Delivery Servers =- US East Region CDS US West Region CDS ------------------------------------------------------------------------------ rhui (cds) =>
Register a CDS instance: a register (add) a new CDS instance I tend to use the term "register" a CDS since you're not creating/adding anything per se. In fact, in order to register a CDS instance the CDS packages must be installed, configured, and running (more on that in the RHUI Installer section). At registration time, the RHUA will attempt to contact the CDS and exchange security information, so if this connection cannot happen, the register fails. For what it's worth, I used 'a' as the trigger for consistency with repos; I thought it made for a better UI if you can always rely on 'l' to list stuff, 'a' to create things, and 'd' to remove things. There isn't much to it. The user enters the following information: Hostname - Identifies the CDS being registered. This *must* be the same as the hostname configured on the CDS itself (in other words, the IP cannot be used). The reason is because the hostname is used as the message bus ID of the CDS. The CDS registers itself on the bus by deriving its ID from its hostname, hence it is critical the hostname supplied to the RHUA be the same (it's your call on how much of this to explain, but the register will fail if they screw this up). Display Name: Defaults to the hostname if the user does not input anything. This is only used for display purposes in RHUI Manager and will be shown in any menus in which the list of CDS instances is needed. Sample: ------------------------------------------------------------------------------ rhui (cds) => a Prior to registering a CDS, the CDS must be configured and running. Hostname of the CDS to register: cds.us-east.example.com Display name for the CDS [cds.us-east.example.com]: US East Region 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 ------------------------------------------------------------------------------
Unregister a CDS instance d unregister (delete) a CDS instance from the RHUI Currently, there is a bug that if the CDS is offline or otherwise inaccessible to the RHUA, the unregistration fails. This will be corrected before we ship. When a CDS is unregistered, all of the repositories and their data are deleted from the CDS. If the CDS is inaccessible, this step will not take place. When I resolve the aforementioned bug, I'll warn the user about this situation in the RHUI, saying something along the lines of "CDS removed from the RHUI however the CDS instance itself could not be cleaned up." The idea is that the user will have to do some manual steps to ensure the content is no longer being hosted from the CDS instance. When I get to that point, I'll update this bug with what that warning message looks like. As for the UI, the user simply selects one or more CDS instances and is displayed a summary before being asked to confirm the deletion. I'll drop a note in there reminding them that content will be deleted, but I'm relying more on this guide to highlight the destructive nature of this call. ------------------------------------------------------------------------------ rhui (cds) => d 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 The following CDS instances will be unregistered: US East Region CDS Proceed? (y/n) y Unregistering US East Region CDS... ------------------------------------------------------------------------------ rhui (cds) =>
Operation/CDS LKB
Revision 1-4 LKB
Covered in the latest docs.
This book is now available at http://docs.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/2.0/html/Installation_Guide/index.html Please raise a new bug for any further changes. LKB