Intro: As I mentioned in 651111, we should probably make a note about needing one client configuration per entitlement certificate, but that the RPM can be used for all instances. ----- Intro: "The Red Hat Update Infrastructure features a tool for configuring the Client instances called the rhui-tools..." If you're been reading these in order, you know where my issue lies in here. Also, in this case "rhui-tools" is in bold but it's not in the other chapters. ----- Steps: 1. No changes. 2. Full path to the entitlement certificate... Same as 3 in the current documentation. 3. Unlike the RHUA/CDS, we don't prompt for the name of the client configuration RPM. Instead, it's derived from the name of the certificate specified in step 2, which itself was the "entitlement certificate name" specified in that step in RHUI Tools. This helps us later when we get to the idea of uploading a newer version of a client configuration RPM. 4. Version of the RPM. This they can and will need to control. If they are deploying an updated version of an existing client configuration RPM, this will need to be higher so that yum detects it as an updated version and installs it. 5. Hostname of the RHUI load balancer... This is a replacement for step 2 in the existing documentation, which is incorrect. We don't use a mirror list anymore. The load balancer *might* be the RHUA instance if the embedded load balancer is used. 6. Full path to the private key... Same as 4 in the current documentation. 7. Full path to the CA certificate... Same as 5 in the current documentation.
Created attachment 458891 [details] Client configuration sample Attached sample output from configuring a client through RHUI Tools.
Added to content spec. Configuration -> Client Instance. LKB
Putting this into the same format used for the other sections. Can you please provide a 1-2 sentence blurb about configuring the client instance to go here: <para> Something here about configuring the client instance ... ==FIXME== </para> <important> <title>Important</title> <para> You need one configuration RPM for each CDS instance, but you can reuse the same client configuration RPM for all clients that share the same entitlements. </para> </important> <para> &PRODUCT; contains a tool called <command>rhui-tools</command> that offers the ability to configure each content distribution server (CDS). </para> LKB
New process and example added. See revision 0-4. LKB
Flicking back to assigned while waiting on further info. LKB
"Client configuration RPMs are used to install an entitlement certificate and repo definitions on a client instance. Each client configuration RPM is scoped to a single entitlement certificate and will provide access to all products contained within it." FYI, this is incorrect: "You need one configuration RPM for each CDS instance, but you can reuse the same client configuration RPM for all clients that share the same entitlements." It should be you need one client configuration RPM for each entitlement certificate.
(In reply to comment #6) > "Client configuration RPMs are used to install an entitlement certificate and > repo definitions on a client instance. Each client configuration RPM is scoped > to a single entitlement certificate and will provide access to all products > contained within it." > <para> Client configuration RPMs are used to install the entitlement certificate and repo definitions on a client instance. Each client configuration RPM is aligned to a single entitlement certificate, and will provide access to all products contained within it. </para> > > FYI, this is incorrect: > > "You need one configuration RPM for each CDS instance, but you can reuse the > same client configuration RPM for all clients that share the same > entitlements." > > It should be you need one client configuration RPM for each entitlement > certificate. <important> <title>Important</title> <para> You need one configuration RPM for each entitlement certificate, but you can reuse the same client configuration RPM for all clients that share the same entitlements. </para> </important> Revision 0-5. LKB
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