Bug 649778 - RHUI 1.2 Updates: Chapter 3 - Installation
Summary: RHUI 1.2 Updates: Chapter 3 - Installation
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-04 14:47 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:12:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Jay Dobies 2010-11-04 14:47:42 UTC
3.2  FYI, this is standard SSL. We provide it since most people we've come across aren't too familiar with the details of working with it.

-----

3.3  "In order for the RHUA to communicate with the CDS instances, you must create a secure connection"

Might want to rephrase this to indicate that the connection has to also allow password-less login from the RHUA to CDS.

-----

3.3  Add a note in there that the SSH configuration on the CDS must allow root logins. I learned that one the hard way trying to do the IBM installation.

-----

3.4  Those URLs in the first step will need to change to be 1.2, for instance:

https://cdn.redhat.com/content/dist/rhel/server/5Server/i386/rhui/1.1/iso/rhel-5.5-rhui-1.1-i386.iso

will become

https://cdn.redhat.com/content/dist/rhel/server/5Server/i386/rhui/1.2/iso/rhel-5.5-rhui-1.2-i386.iso

Same for the ISO filenames in the following steps.

-----

3.4  Need to add a step that if the customer is using an external load balancer (i.e. not on the RHUA) the install_CDS.sh script will need to be installed on that instance as well. Yes, that's not a typo, you run install_CDS.sh on the load balancer instance. It's a bit wonky.

Comment 1 Lana Brindley 2010-11-10 02:54:11 UTC
Added to content spec. Installation.

LKB

Comment 2 Lana Brindley 2010-11-17 00:44:35 UTC
(In reply to comment #0)
> 3.2  FYI, this is standard SSL. We provide it since most people we've come
> across aren't too familiar with the details of working with it.
> 

I've made a few edits to this section.

> -----
> 
> 3.3  "In order for the RHUA to communicate with the CDS instances, you must
> create a secure connection"
> 
> Might want to rephrase this to indicate that the connection has to also allow
> password-less login from the RHUA to CDS.
> 
> -----
> 
> 3.3  Add a note in there that the SSH configuration on the CDS must allow root
> logins. I learned that one the hard way trying to do the IBM installation.
> 

<para>
	In order for the RHUA to communicate with the CDS instances, you must create a secure connection. The CDS must also be configured to allow root login without requesting a password. &RHEL; contains the OpenSSH communication program to authenticate connections.
</para>

> -----
> 
> 3.4  Those URLs in the first step will need to change to be 1.2, for instance:
> 
> https://cdn.redhat.com/content/dist/rhel/server/5Server/i386/rhui/1.1/iso/rhel-5.5-rhui-1.1-i386.iso
> 
> will become
> 
> https://cdn.redhat.com/content/dist/rhel/server/5Server/i386/rhui/1.2/iso/rhel-5.5-rhui-1.2-i386.iso
> 
> Same for the ISO filenames in the following steps.
> 

<screen>
wget --certificate=&lt;Content Certificate&gt;\
--private-key=&lt;Content Certificate Private Key&gt;\
--ca-certificate=&lt;CA Certificate&gt;\
https://cdn.redhat.com/content/dist/rhel/server/5Server/i386/rhui/1.1/iso/rhel-5.5-rhui-&RHUIVER;-i386.iso
</screen>

and

<screen>
wget --certificate=&lt;Content Certificate&gt;\
--private-key=&lt;Content Certificate Private Key&gt;\
--ca-certificate=&lt;CA Certificate&gt;\
https://cdn.redhat.com/content/dist/rhel/server/5Server/x86_64/rhui/1.1/iso/rhel-5.5-rhui-&RHUIVER;-x86_64.iso
</screen>

and

<screen>
mkdir /mnt/rhuiso
mount -o loop -t iso9660 -r rhel-5.5-rhui-&RHUIVER;-i386.iso /mnt/rhuiso/
</screen>

and

<screen>
mkdir /mnt/rhuiso 
mount -o loop -t iso9660 -r rhel-5.5-rhui-&RHUIVER;-x86_64.iso /mnt/rhuiso/
</screen>

<!ENTITY RHUIVER "1.2">

> -----
> 
> 3.4  Need to add a step that if the customer is using an external load balancer
> (i.e. not on the RHUA) the install_CDS.sh script will need to be installed on
> that instance as well. Yes, that's not a typo, you run install_CDS.sh on the
> load balancer instance. It's a bit wonky.

<listitem>
	<para>
		If you are using an external load balancer (a load balancer that is not on the RHUA), the <command>install_CDS.sh</command> script will need to be run on the load balancer instance as well.
	</para>
</listitem>

LKB

Comment 3 Lana Brindley 2010-11-17 00:45:30 UTC
Further proofing and review also undertaken in this chapter. See revision 0-2.

LKB

Comment 4 Andrew Ross 2010-12-07 03:01:00 UTC
Checking: Red_Hat_Update_Infrastructure-Installation_Guide-1.2-web-en-US-0-8.el5

(In reply to comment #0)

> 3.4  Those URLs in the first step will need to change to be 1.2, for instance:
> 
> https://cdn.redhat.com/content/dist/rhel/server/5Server/i386/rhui/1.1/iso/rhel-5.5-rhui-1.1-i386.iso
> 
> will become
> 
> https://cdn.redhat.com/content/dist/rhel/server/5Server/i386/rhui/1.2/iso/rhel-5.5-rhui-1.2-i386.iso
> 
> Same for the ISO filenames in the following steps.

Paths partly correct. Still contain 1.1: rhui/1.1/iso

https://cdn.redhat.com/content/dist/rhel/server/5Server/i386/rhui/1.1/iso/rhel-5.5-rhui-1.2-i386.iso

https://cdn.redhat.com/content/dist/rhel/server/5Server/x86_64/rhui/1.1/iso/rhel-5.5-rhui-1.2-x86_64.iso

Comment 5 Lana Brindley 2010-12-08 03:17:10 UTC
(In reply to comment #4)
> Checking:
> Red_Hat_Update_Infrastructure-Installation_Guide-1.2-web-en-US-0-8.el5
>
> 
> Paths partly correct. Still contain 1.1: rhui/1.1/iso

Fixed.

LKB

Comment 6 Lana Brindley 2010-12-13 23:12:46 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.