Show Table of Contents
Chapter 3. Example Topologies
The RHN Proxy Server can be configured in multiple ways. Select one method depending on the following factors:
- The total number of client systems to be served by the RHN Proxy Server
- The maximum number of clients expected to connect concurrently to the RHN Proxy Server.
- The number of custom packages and channels to be served by the RHN Proxy Server.
- The number of RHN Proxy Servers being used in the customer environment.
The rest of this chapter describes possible configurations and explains their benefits.
3.1. Single Proxy Topology
The simplest configuration is to use a single RHN Proxy Server to serve your entire network. This configuration is adequate to service a small group of clients and a network that would benefit from caching Red Hat RPMs and storing custom packages on a local server.
The disadvantage of using one RHN Proxy Server is that performance will be compromised as the number of clients requesting packages grows.
Figure 3.1. Single Proxy Topology
Where did the comment section go?
Red Hat's documentation publication system recently went through an upgrade to enable speedier, more mobile-friendly content. We decided to re-evaluate our commenting platform to ensure that it meets your expectations and serves as an optimal feedback mechanism. During this redesign, we invite your input on providing feedback on Red Hat documentation via the discussion platform.