Deploying Local Office Services on CloudPond

Updated on 2024-05-17 GMT+08:00

View PDF

Background

A customer plans to migrate their OA services from a local virtualization environment to the cloud by deploying CloudPond in their data center. The service status is as follows:

OA services cannot be migrated to the public cloud because of the service purposes.
Currently, there is no plan to deploy a large number of services on the public cloud.
The service purposes and people who use OA services seldom change. So the service performance is predictable, and the services are not required for high reliability (available: 5 working days x 8 hours + some holidays).
The public network bandwidth of the data center is limited and is shared with services of other domains.

Networking Configuration

The recommended edge-cloud networking is shown in Figure 1.

Figure 1 Networking design

Key Points

The minimum bandwidth is provided for management plane and data plane networks because all services are deployed at the edge and the edge-cloud traffic is small.
CloudPond EIPs use the cloud's shared bandwidths (≥100 Mbit/s) because the customer data center's public network only has limited bandwidths shared by services.
EIP billing by traffic is recommended for the default settings of edge-cloud communications because the cloud data plane does not need to communicate with the edge.
Internet single-line connection is used because edge OA services are not required for high reliability. If the management plane is disconnected, edge services can still run properly but cannot be managed by the central cloud, which has a small impact on the entire service system.