Bug 752962 - Documentation corrections/suggestions - Chap 1
Summary: Documentation corrections/suggestions - Chap 1
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: Documentation
Version: 2.0.2
Hardware: Unspecified
OS: Linux
low
low
Target Milestone: ---
: ---
Assignee: Lana Brindley
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-10 21:46 UTC by Karthik Prabhakar
Modified: 2016-10-30 22:52 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-01-29 21:10:47 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description Karthik Prabhakar 2011-11-10 21:46:28 UTC
Sec 1.1.2: Rename "SSL Certificates" to "Server Certificates" to be more clear - pretty much every certificate (entitlement/content/server) is an ssl cert.

Sec 1: In the box marked "Important": remove mention of RHEL 5

Comment 1 Lana Brindley 2012-01-03 23:17:21 UTC
(In reply to comment #0)
> Sec 1.1.2: Rename "SSL Certificates" to "Server Certificates" to be more clear
> - pretty much every certificate (entitlement/content/server) is an ssl cert.

<varlistentry>
	<term>Server Certificates</term>
	<listitem>
		<para>
			A new server certificate is generated for each load balancer and CDS instance. For example, in an environment with three CDS instances, three separate server certificates will need to be generated. The common name (CN) of the certificate must match the hostname of the instance.
		</para>
	</listitem>
</varlistentry>

> 
> Sec 1: In the box marked "Important": remove mention of RHEL 5

<important>
	<para>
		Always ensure that you include the package that installs the GPG keys when installing client configuration RPMs. For &RHEL; 6, the package required is <filename>redhat-release-server</filename>.
	</para>
</important>

Revision 2-15

LKB

Comment 3 James Slagle 2012-03-12 19:40:04 UTC
Released in RHUI 2.0.2


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