Separate Storage Network
159
• The Management Server cluster (including front-end load balancers, Management Server nodes,
and the MySQL database) is connected to the management network through a pair of load
balancers.
• Secondary storage servers are connected to the management network.
• Each pod contains storage and computing servers. Each storage and computing server should have
redundant NICs connected to separate layer-2 access switches.
13.3. Separate Storage Network
In the large-scale redundant setup described in the previous section, storage traffic can overload the
management network. A separate storage network is optional for deployments. Storage protocols such
as iSCSI are sensitive to network delays. A separate storage network ensures guest network traffic
contention does not impact storage performance.
13.4. Multi-Node Management Server
The CloudPlatform Management Server is deployed on one or more front-end servers connected to
a single MySQL database. Optionally a pair of hardware load balancers distributes requests from the
web. A backup management server set may be deployed using MySQL replication at a remote site to
add DR capabilities.
The administrator must decide the following.
• Whether or not load balancers will be used.
• How many Management Servers will be deployed.
• Whether MySQL replication will be deployed to enable disaster recovery.
13.5. Multi-Site Deployment
The CloudPlatform platform scales well into multiple sites through the use of zones.
There are two ways to configure the storage network:
• Bonded NIC and redundant switches can be deployed for NFS. In NFS deployments, redundant
switches and bonded NICs still result in one network (one CIDR block+ default gateway address).
• iSCSI can take advantage of two separate storage networks (two CIDR blocks each with its own
default gateway). Multipath iSCSI client can failover and load balance between separate storage
networks.