Contents
SUSE Manager can be configured in multiple ways. Select one method depending on the following factors:
The total number of client systems to be served by SUSE Manager.
The maximum number of clients expected to connect concurrently to .
The number of custom packages and channels to be served by SUSE Manager.
The number of SUSE Managers being used in the customer environment.
The rest of this chapter describes possible configurations and explains their benefits.
The simplest configuration is to use a single SUSE Manager to serve your entire network. This configuration is adequate to service a medium-size group of clients and network.
The disadvantage of using one SUSE Manager is that performance will be compromised as the number of clients requesting packages grows.
For very large networks, a more distributed method may be needed, such as having multiple SUSE Managers in a horizontally tiered configuration and balancing the load of client requests.
Additional maintenance is the biggest disadvantage of this horizontal structure.
An alternative method to balance load is to install SUSE Manager Proxy Servers below a SUSE Manager. These Proxies connect to the SUSE Manager for RPMs from Novell Customer Center and custom packages created locally. In essence, the Proxies act as clients of the SUSE Manager.
This vertically tiered configuration requires that channels and RPMs be created only on the SUSE Manager. In this manner, the Proxies inherit and then serve packages from a central location.
Similarly, you should make the Proxies' SSL certificates clients of the SUSE Manager while also setting them to serve the client systems. This process is described in the Client Configuration Guide.