I'm not sure how you typically handle conveying what's changed from one version to the next. In this case, it's pretty significant, so I'll explain the situation and let you make the call. In 1.2, "RHUI Tools" did everything from configuring SSL on the RHUA and CDS instances to selecting products to be synchronized. You saw in RHUI Manager that much of that functionality has now been moved into the Manager portion. That leaves the RHUI Installer as being responsible for configuring static information about the servers themselves. The goal is to get the RHUI running, allowing the user to then use Manager to use it ("configure it"?). Some examples of the things the installer does: - Configures httpd on the RHUA and CDS instances with SSL certificates - Installs a custom CA certificate for use in user (as in, the user that logs into RHUI Manager) to protect admin access - Configures the RHUA (things like hostname and enabling repo authentication) - Configures secure communications between RHUA and CDS Things the installer does not do: - Select which repositories to sync - Generate client entitlement certificates and configuration RPMs - Protect against a zombie attack Another big difference from 1.2 is that all of the interactive prompts are gone. Most are moved to RHUI Manager, others are unnecessary. The new model is to only use the answers file concept that was provided as an option in 1.2. The user fills out an answers file (a sample is included at /etc/rhui/answers.sample) and passes that to the Installer. It runs using the values in there and produces one or more configuration RPMs. Those RPMs are installed on their respective components (RHUA or CDS) which will configure and start all RHUI services. At that point, RHUI Manager can be used to manipulate repositories, CDS instances, and client-side pieces (entitlement certs and config RPMs).
Installation/RHUI Installer LKB
(In reply to comment #0) > > Things the installer does not do: > - Select which repositories to sync > - Generate client entitlement certificates and configuration RPMs > - Protect against a zombie attack I'm disappointed. I thought that came standard these days? ;) Revision 1-7. LKB
I think its good to add what RHUI Installer does, in the RHUI Installer section: - Configures httpd on the RHUA and CDS instances with SSL certificates - Installs a custom CA certificate for use in user (as in, the user that logs into RHUI Manager) to protect admin access - Configures the RHUA (things like hostname and enabling repo authentication) - Configures secure communications between RHUA and CDS
<variablelist> <para> The RHUI Installer performs the following tasks: </para> <listitem> <para> Configures <command>httpd</command> on the RHUA and any CDS instances with SSL certificates </para> </listitem> <listitem> <para> Installs a custom CA certificate that is used for authentication of users </para> </listitem> <listitem> <para> Configures the RHUA </para> </listitem> <listitem> <para> Configures secure communication between the RHUA and the CDS instances </para> </listitem> </variablelist> Revision 1-21 LKB
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