Bug 224357 - system requirement of "6 GB storage per channel" too low to store "mature" channels
system requirement of "6 GB storage per channel" too low to store "mature" ch...
Status: CLOSED CURRENTRELEASE
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Docs Reference Guide (Show other bugs)
500
All Linux
medium Severity medium
: ---
: ---
Assigned To: John Ha
Red Hat Satellite QA List
http://www.redhat.com/docs/manuals/RH...
: Documentation
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2007-01-25 07:46 EST by Riaan van Niekerk
Modified: 2014-08-04 18:17 EDT (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2009-09-30 05:20:08 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Riaan van Niekerk 2007-01-25 07:46:01 EST
The system requirements for Satellite mention "6 GB storage per channel, in the
/var/satellite/ directory by default but configurable at install"

This is completely insufficient to store the packages of current RHEL 3 / RHEL 4
channels. e.g. the channel dump for RHEL 4 x86_64 is 30 ISOs (including
incremental dumps), 18 GB. I have no reason to believe that once this data is
imported to /var/satellite, it will use any less.

I would recommend a more generous estimate of 15 to 20 GB per channel
Comment 1 Michael Hideo 2007-06-19 21:31:48 EDT
Moving Bugs to John Ha and assigning.

Re-prioritization meeting on June 20, 7PM EST.
Comment 2 Riaan van Niekerk 2007-09-11 10:54:44 EDT
This same insufficient 6 GB per channel is still present in the RHN Satellite 
5.0 documentation:

http://www.redhat.com/docs/manuals/satellite/Red_Hat_Network_Satellite-5.0.0/
html/Installation_Guide/s1-requirements-hardware.html
Comment 3 Michael Hideo 2007-10-22 22:47:52 EDT
Removing automation notification
Comment 4 Riaan van Niekerk 2009-09-30 05:20:08 EDT
I see this is fixed in the latest version

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