Bug 726154 - Add a "Hardware" section to the installation prereqs
Summary: Add a "Hardware" section to the installation prereqs
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Update Infrastructure for Cloud Providers
Classification: Red Hat
Component: Documentation
Version: 2.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
: ---
Assignee: Lana Brindley
QA Contact: wes hayutin
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-27 17:20 UTC by Jay Dobies
Modified: 2016-02-18 06:15 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-29 04:57:28 UTC
Target Upstream Version:

Attachments (Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Description Jay Dobies 2011-07-27 17:20:16 UTC 
I'm sure there's a pretty standard way of formatting these, so I'll just spit out a bunch of data and you can pretty it up. For what it's worth, I'm using http://docs.redhat.com/docs/en-US/Red_Hat_Network_Satellite/5.4.1/html/Installation_Guide/sect-Installation_Guide-Hardware_Requirements.html as a bit of a model here.


Required:
* 2GB of memory
* 4GB of swap space
* At least 30 GB storage per software channel in /var/lib/pulp (there's already something there about storage and establishing that /var/lib/pulp, so your call if you want to merge it into there)
* RHEL 6 base install (it doesn't run on RHEL 5)
Comment 1 Lana Brindley 2011-07-27 23:56:19 UTC 
I haven't added a separate section for this, as we don't really have enough data to make it worthwhile. I've changed the "Storage Requirements" section to read "Hardware and Storage Requirements" and have added the information there instead.

Revision 1-25.

LKB
Comment 3 Lana Brindley 2011-07-29 04:57:28 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.