RHN Proxy Server: Installation Guide; Version 1.8.0
Previous Chapter 2. Requirements Next

2.2. Hardware Requirements

To use the RHN Proxy Server, the following hardware is required:

  • The RHN Proxy Server and its components are supported only on the x86 architecture with the minimum requirement of a Pentium processor -- the faster, the better.

  • For a single RHN Proxy Server, the minimum requirement is one server that acts as the RHN Proxy Broker Server, RHN Authentication Daemon, and RHN Proxy SSL Redirect Server. Alternately, the RHN Authentication Daemon and RHN Proxy SSL Redirect Server may reside on separate machines.

  • The amount of memory is dependent on other services that run on the same machine. In most cases, 64MB of RAM memory should suffice.

2.2.1. Disk Space Requirements

The HTTP proxy caching server used to save bandwidth for the clients should have a fairly reasonable amount of space available. If you are using Squid as the HTTP proxy caching server, the cached packages are stored in /var/cache/squid. The recommended free space allotment should be approximately 120% of the total space taken by the RPMs for all distributions intended to be served. You can compute the space requirements depending on how many different distributions the proxy will have to serve. Configure approximately 1.3 GB of space per distribution (including updates and source packages) as a maximum; the actual amount can be much lower if you download only package updates.

If the RHN Proxy Server is configured to distribute local packages, make sure that the /var mount point on the system storing local packages has sufficient disk space to hold all of the custom packages, which are stored in /var/up2date/packages. The required disk space for local packages depends on the number of custom packages deployed.

The RHN Authentication Daemon requires approximately 5 KB of disk space for each client server the RHN Proxy Server will service.

The RHN Proxy SSL Redirect Server requires approximately 130 KB for the server itself plus disk space for Apache and Python, which require approximately 2 MB combined.

For the RHN Proxy Broker Server (two scenarios):

  1. If you are not planning to provide local channels (for example, have your own distribution stored locally on the proxy), the space requirements for the proxy itself are minimal: approximately 2 MB.

  2. Running local channels will add some disk space requirements for the packages you will have: whatever is needed for the packages you plan to serve, plus the space required for scenario 1.

For details on how to limit the number of cached distributions, refer to Section G.3 HTTP Proxy Caching Server Configuration.

Previous Home Next
Requirements Up Additional Requirements