| Sun Java System Content Delivery Server Capacity Planning Guide |     |
| C H A P T E R 4 |
|
Sample Configurations |
The minimal hardware configuration you need to run the Content Delivery Server consists of a single server configured with one CPU (two CPUs is preferred), 1 GByte RAM (2 GBytes are preferred), and 35 GBytes of free disk space, running Sun Solaris
10 Operating System, and Oracle 10g. This configuration is sufficient for an initial product evaluation, but not for an actual deployment.
This chapter describes a few sample Content Delivery Server configurations:
How you choose to configure a trial deployment depends on several things including how a trial configuration influences your actual deployment configuration needs and the kinds of servers and other equipment available to you. This section describes one possible trial configuration.
An initial trial of a content delivery system that supports a few thousand highly active subscribers might have a hardware configuration that looks like the one depicted in FIGURE 4-1:
FIGURE 4-1 Simple Two Server Configuration
The configuration employs two dual CPU servers for Content Delivery Server Service and Database Modules. A simple router switch provides connectivity between these servers and to your private and public networks.
FIGURE 4-2 shows a sample configuration of Content Delivery Server components (X indicates which applications are included).
FIGURE 4-2 Sample Application Configuration for Small Size Deployment
This configuration defines a single service domain including all Content Delivery Server application components (running services as needed). There is only one host (cdssrv) in Content Delivery Server Service Module and you only need to configure a single deployment.
While this configuration might be sufficient for an initial content delivery system, be sure you understand the security risks inherent in combining the internal administrative services and the external subscriber and developer services in a single service domain. Service availability can also be a concern while deploying Content Delivery Server to a single host. Finally, this configuration raises concerns about database availability and data security.
The hardware requirements for this deployment are:
For a larger trial deployment, use Sun SPARC T5120, or T5220 server. For details, see the hardware requirements for medium deployments.
As you move beyond the initial trial, you might want to consider a configuration such as the one depicted in the following diagram:
FIGURE 4-3 Configuration for a Small to Medium Size Deployment
This configuration employs two to eight dual CPU servers for the externally facing services (four are shown in the figure) and one additional server for an administrative service domain. The database module is configured with two Sun T5240 servers configured in a cluster configuration with shared mirrored disk arrays for database storage. Alternatively, Sun SPARC T5120 or T5220 can be used.
| Note - FIGURE 4-3 shows a moderate-sized deployment configuration with only a single administration server. While such a configuration can work well, it is problematic in case of a failure at the administrative layer. A more robust configuration that does not rely solely on a single server would have an administration layer with at least two servers and a load balancer. |
FIGURE 4-4 shows a sample configuration of Content Delivery Server components:
FIGURE 4-4 Sample Application Configuration for Medium Deployment
The Content Service Module contains three service domains:
Following are the hardware requirements for this deployment:
Alternatively, you can use the Sun SPARC T5220 server in a similar configuration.
Ideally load balancers are located outside the public and private networks, at the same level as the virtual IP (VIP), if one exists. However, placing load balancers between each server layer increases the reliability of the system.
If you plan to make use of the multivending feature you can use a configuration similar to the one described in Small to Medium Deployment. However, if you plan to deploy more processes, use servers that can be configured with more CPUs. For instance, you can use either the Sun SPARC T5240 or Sun SPARC T5440 server, which can be configured with up to four and eight core T1 or T2 CPUs, respectively. This provides a configuration that is easily scalable with respect to both subscribers and Vending Managers.
FIGURE 4-5 Configuration for Multivending Deployment
The illustrated configuration employs four Sun SPARC T5140 servers for the externally facing service domains and one additional server for the administrative service domain. The database module consists of two clustered Sun SPARC T5440 servers with mirrored disk arrays for database storage.
| Note - FIGURE 4-5 shows a moderate-sized deployment configuration with only a single administration server. While such a configuration can work well, it is problematic in case of a failure at the administrative layer. A more robust configuration that does not rely solely on a single server would have an administration layer with at least two servers and a load balancer. |
FIGURE 4-6 shows a deployment configuration with four Vending Managers.
FIGURE 4-6 Sample Application Configuration for Multivending Deployment
The Content Service Module consists of nine service domains:
Following are the hardware requirements for this deployment:
Alternatively, for a more robust deployment, you can use Sun SPARC T5120 or T5220, with four to eight core T1 or T2 CPUs at 1.2 or 1.4 GHz respectively, 16 to 64 GBytes RAM each. Count one CPU per every two CPUs assigned to the subscriber service domain.
For a discussion of load balancer placement for optimal throughput, see the hardware requirements for a medium sized deployment in Deployment Hardware Requirements.
You can easily scale the configurations described in the Small to Medium Deployment and Multivending Deployment by adding more servers and by providing additional resources for the database module. However, for large deployments you might consider using fewer large servers. FIGURE 4-7 uses the Sun SPARC T5240 mid-range data-center server, which can be configured with up to four to eight T1 or T2 CPUs at 1.2 or 1.4 GHz processors.
FIGURE 4-7 Configuration for Large Deployment
This configuration employs five Sun SPARC T5440 servers. For the externally facing service domains, two T5140 servers are used, each partitioned into two system domains. For the internal administration domains, a third server is used, also partitioned into two system domains. The last two servers, clustered and configured with associated storage arrays, provide a highly available database server.
This hardware configuration works well for both single-vending and multivending content delivery systems. FIGURE 4-8 illustrates a single-vending configuration with multiple subscriber service domains.
FIGURE 4-8 Sample Application Configuration for Large Size Deployment
The Content Service Module consists of five domains:
Following are hardware requirements for this deployment:
For a discussion of load balancer placement for optimal throughput, see the hardware requirements for a medium sized deployment in Deployment Hardware Requirements.
| Sun Java System Content Delivery Server Capacity Planning Guide | 820-1939-10 | |
Copyright © 2008 Sun Microsystems, Inc. All Rights Reserved.