Bug 651111 - RHUI 1.2 Updates: Chapter 6 - Configuring CDS Instances
Summary: RHUI 1.2 Updates: Chapter 6 - Configuring CDS Instances
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: Documentation
Version: 1.1
Hardware: Unspecified
OS: Unspecified
low
medium
Target Milestone: ---
: ---
Assignee: Lana Brindley
QA Contact: ecs-bugs
URL:
Whiteboard:
Depends On:
Blocks: 649091
TreeView+ depends on / blocked
 
Reported: 2010-11-08 20:34 UTC by Jay Dobies
Modified: 2013-10-23 23:19 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-13 23:14:32 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
CDS configuration sample from tools (1.44 KB, application/octet-stream)
2010-11-08 20:35 UTC, Jay Dobies
no flags Details

Description Jay Dobies 2010-11-08 20:34:41 UTC
Intro:  Might want to add a note in there that this must be run once per CDS being used. Each CDS has its own SSL certificate which will be bundled into the CDS configuration, so in order to distribute those certificates where necessary individual CDS configuration RPMs are created.

Not sure where you'd want to put this, but you will only need one client RPM per entitlement certificate. This has confused people in the past. You need one CDS configuration RPM per CDS instance, but you reuse the same client configuration RPM for all clients that should share the same set of entitlements.

-----

Intro:  "The Red Hat Update Infrastructure features a tool for configuring the Content Distribution Server (CDS) instances called the rhui-tool..."

Again, this feels wonky. By now they should know that, but this reads like it's the first time they would be seeing it.

-----

Intro:  "Choose option 2 to configure the CDS instance(s). "

The CDS is now option 4: "4 - CDS"

-----

1.  No changes.

2.  Name of the configuration RPM (see 651052 for an explanation of RPM names and versions, since it's the same rationale for all of the RHUI components).

The only potential addition is that they can use this name field to help distinguish between the RPMs. For instance, given the following two CDS instances:

batman.example.com
robin.example.com

They might want to choose the RPM names to reflect which machine to install it on. So something like "rhui-batman-0.1.rpm" and "rhui-robin-0.1.rpm".

3.  Version of the configuration RPM (again, see 651052).

4.  Directory on the CDS... Same as 2 in the existing documentation.

5.  Full path to the CDS SSL certificate... Same as 3 in the existing documentation.

6.  Full path to the CDS SSL certificate private key... Same as 4 in the existing documentation.

7.  Full path to the CA certificate... Same as 5 in the existing documentation.

8.  Full path to the CA chain file... Same as 6 in the existing documentation, with the exception that the existing documentation is wrong. A CA chain file isn't the concatenation of the CDS SSL certificates. It's a description of the CA chain of trust if one is used in their environment.

Comment 1 Jay Dobies 2010-11-08 20:35:10 UTC
Created attachment 458880 [details]
CDS configuration sample from tools

Attached a sample CDS configuration using RHUI tools.

Comment 2 Lana Brindley 2010-11-10 03:02:36 UTC
Added to content spec. Configuration -> Content Distribution Server instances.

LKB

Comment 3 Lana Brindley 2010-11-22 10:43:42 UTC
New process and example added.

See revision 0-4.

LKB

Comment 5 Lana Brindley 2010-12-13 23:14:32 UTC
Published 14 December 2010: http://docs.redhat.com/docs/en-US/Red_Hat_Update_Infrastructure/1.2/html/Installation_Guide/index.html

Please raise any issues as new bugs against this live version.

Thanks,
LKB


Note You need to log in before you can comment on or make changes to this bug.