The BMS service allows you to provision BMSs using the XenServer OS. You can build a XenServer private cloud based on the BMS cluster and seamlessly migrate your core applications to the cloud. Service VMs in the XenServer private cloud can communicate with Elastic Cloud Servers (ECSs) to provide you with a more flexible solution to migrate services to the cloud.
This document provides a reference solution for deploying a XenServer system using BMSs. You can also deploy the XenServer system in a different mode based on the capabilities provided by the public cloud.
In XenServer on BMS, at least two BMSs are required. One is a multi-NIC Windows BMS with XenCenter installed that functions as the management node of the virtualization cluster. The other is a multi-NIC XenServer BMS that is used to provision service VMs. BMSs of this type can be added based on service requirements (single node and cluster).
If service VMs need to provide services to the Internet, an EIP must be bound to the BMS used to provision service VMs. If a cluster contains multiple BMSs, you can create a NAT gateway and add a DNAT rule to it enable multiple BMSs to share an EIP. This reduces management cost.
If service VMs only communicate with ECSs in the same VPC, you do not need to assign an EIP.
In Figure 1, the user-defined network is a network type provided by the cloud platform for the XenServer on BMS solution. This network provides functions similar to those of the VPC for VMs.