Bug 637809 - Update database size requirements
Summary: Update database size requirements
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Satellite 5
Classification: Red Hat
Component: Docs Installation Guide
Version: 540
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Lana Brindley
QA Contact: Pavel Novotny
URL:
Whiteboard:
Depends On: 644720
Blocks: sat541-docs
TreeView+ depends on / blocked
 
Reported: 2010-09-27 14:04 UTC by Michael Mráka
Modified: 2013-10-23 23:19 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-16 22:24:23 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

Description Michael Mráka 2010-09-27 14:04:31 UTC
Current Installation Guide contain out-of-date databaze size requirements.

Current (Sat 5.3) requirements:

2.3. Database Requirements

...
A single 6 GB tablespace is recommended as more than sufficient for most installations. It is possible for many customers to function with a smaller tablespace. An experienced Oracle database administrator (DBA) will be necessary to assess sizing issues. The following formula should be used to determine the required size of your database: 
* 192 KB per client system 
* 64 MB per channel 
For instance, an RHN Satellite containing 10 channels serving 10,000 systems would require 1.92 GB for its clients and 640 MB for its channels. If custom channels are to be established for testing and staging of packages, they must be included in this formula.
...


Updated (Sat 5.4) requirements:

2.3. Database Requirements

...
A single 12 GB tablespace is recommended as sufficient for most installations. It is possible for many customers to function with a smaller tablespace. An experienced Oracle database administrator (DBA) will be necessary to assess sizing issues. The following formula should be used to determine the required size of your database: 
* 250 KiB per client system 
* 500 KiB per channel + 230 KiB per package in channel (i.e. 1.1GiB for channel with 5000 packages)
For instance, an RHN Satellite containing 4 channels (Red Hat Enterprise Linux AS 4 and Red Hat Enterprise Linux  Server 5, both for i386 and x86_64 architectures) channels serving 10,000 systems would require 2.5 GiB for its clients and 11 GiB for its channels. If custom channels are to be established for testing and staging of packages, they must be included in this formula.
...

Comment 1 Clifford Perry 2010-09-27 14:16:22 UTC
We should look to include this doc change the next time (post 5.4 GA) we look to respin/edit the Satellite guide. Right now, as a public bug, customers can be pointed to this, if needed.

Cliff

Comment 2 Lana Brindley 2010-10-08 04:20:35 UTC
This is slated for inclusion in the Satellite 5.5 documentation. If there is
any other source content that is not listed (or linked to) in this bug, please
link to it.

LKB

Comment 3 Lana Brindley 2010-11-16 21:14:27 UTC
Added to content specification for 5.4.1.

LKB

Comment 4 Lana Brindley 2011-02-03 23:19:36 UTC
 <para>
	    A single 12 GB tablespace is recommended for most installations, although many customers will find it possible to function with a smaller tablespace. Have an 
experienced Oracle database administrator (DBA) assess your sizing requirements. Use the following formula to determine the required size of your database:
    </para>

    <itemizedlist>
      <listitem>
	<para>
	  250 KiB per client system
	</para>
      </listitem>
      <listitem>
	<para>
	  500 KiB per channel, plus 230 KiB per package in the channel (so a channel with 5000 packages would require 1.1 Gib)
	</para>
      </listitem>
    </itemizedlist>

    <para>
      For instance, an &SAT; containing 4 channels (both &RHEL; AS 4 and &RHEL; Server 5, both for i396 and x86_64 architectures) serving 10,000
      systems would require 2.5 GiB for its clients and 11 GiB for its channels. If custom channels are to be established for testing
      and staging of packages, they must be included in this formula.
    </para>

Updated in revision 1-31, which should be available on the stage for review within 24 hours.

LKB

Comment 5 Pavel Novotny 2011-04-21 12:23:21 UTC
Taking this bug for verification.

Comment 6 Pavel Novotny 2011-04-21 15:07:36 UTC
(In reply to comment #4)
> [ snip ]
>
>     <para>
>       For instance, an &SAT; containing 4 channels (both &RHEL; AS 4 and &RHEL;
> Server 5, both for i396 and x86_64 architectures) serving 10,000
Typo in 'i396' architecture, it should be '..., both for i386 and x86_64 architectures)'

Rest of the text is OK.

Moving back to ASSIGNED.

Comment 8 Lana Brindley 2011-04-26 23:11:12 UTC
(In reply to comment #6)
> (In reply to comment #4)
> > [ snip ]
> >
> >     <para>
> >       For instance, an &SAT; containing 4 channels (both &RHEL; AS 4 and &RHEL;
> > Server 5, both for i396 and x86_64 architectures) serving 10,000
> Typo in 'i396' architecture, it should be '..., both for i386 and x86_64
> architectures)'
> 
> Rest of the text is OK.
> 
> Moving back to ASSIGNED.

<para>
	For instance, an &SAT; containing 4 channels (both &RHEL; AS 4 and &RHEL; Server 5, both for i386 and x86_64 architectures) serving 10,000 systems would require 2.5 GiB for its clients and 11 GiB for its channels. If custom channels are to be established for testing and staging of packages, they must be included in this formula.
</para>

Fixed in revision 1-35

LKB

Comment 10 Lana Brindley 2011-05-06 00:12:55 UTC
This book has now been dropped to translation (RT#75265).
No further updates can be accepted. Please raise a new bug for any changes.
LKB

Comment 11 Lana Brindley 2011-05-06 00:14:56 UTC
This book has now been dropped to translation (RT#75265).
No further updates can be accepted. Please raise a new bug for any changes.
LKB

Comment 12 Lana Brindley 2011-06-16 22:24:23 UTC
5.4.1 Satellite books are now available on docs.redhat.com. Please raise a new bug for any issues.

LKB


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