【FusionCloud V100R006C10 】Solution Deploy Architecture

Deploy Architecture

Concepts

The FusionCloud solution involves multiple data centers that may belong to different geographic regions. Only one set of some components need to be deployed for the whole solution (Global), whereas other components are required in one region or multiple regions. Table1 lists the principles for global deployment and region deployment.

Table1 Global or region deployment principles
Deployment Type	Description	Deployment Principle
Global	This applies to components that are deployed only once in the solution.	The following services are deployed in a global manner: Cloud management layer: IAM, ServiceCenter, and OperationCenter Cloud service layer: Cloud Service Console Public service layer: LVS, Nginx, and console framework
Region	Region is the geographic region. Region can be considered as a circle whose radius is the delay. Access delay: Users within the region receive services within a delay shorter than 100 ms. Coverage area: Service quality cannot be guaranteed beyond the radius (delay). Another Region is required for service provisioning. Geographic redundancy: Generally, Regions are geographically diverse and can form geographical redundancy.	All components except for those for global deployment are deployed by Region.
AZ	An available zone (AZ) may correspond to one or multiple physical DCs. It has independent cooling, fire extinguishing, moisture-proof, and electricity facilities. With AZ divisions, computing, network, storage, and other resources are logically divided into clusters. AZs within a Region are interconnected using high-speed optical fibers to realize cross-AZ high availability for the system.	-

Typical Deployment Scenarios

Two typical deployment schemes (Region Type I and Region Type II) are recommended for the FusionCloud solution. Table5 lists the advantages and disadvantages. Table6 lists the difference.

Table1 Advantages and disadvantages between the Region Type I and Region Type II scenarios
Scenario	Advantages	Disadvantages
Region Type I	Supports hybrid cloud with lower cost	Higher network delay
Region Type II	Supports VMware heterogeneous virtualization with lower network delay Supports the cloud server disaster recovery (CSDR) service with remote disaster recovery protection for ECSs	Higher cost

Table1 Difference between Region Type I and Region Type II
Typical deployment scenarios	Region Type I	Region Type II
Management Server	RH2288H V3	RH2288H V3
Networking Type	FusionSphere OpenStack network node FusionSphere OpenStack provides the network node function, which enables deployment of modules such as vRouter on network nodes, providing basic network capabilities for the cloud services.	Agile Controller Agile Controller is a new-generation SDN controller designed for the data center network. It provides application-based network automation function, reducing network deployment complexity. Corresponding network devices are required for Agile Controller: CloudEngine 12800 Firewall (USG9500, Eudemon-X3, Eudemon-X8)
Management Storage	Promoted: IPSAN Supported: FusionStorage Block Converged Deployment	Promoted: IPSAN Supported: FusionStorage Block Converged Deployment
Cascaded Form	The first cascaded FusionSphere OpenStack system is deployed on VMs (controller node 3, cloud service node 1, and cloud service node 2 of the cascaded FusionSphere OpenStack). The second cascaded FusionSphere OpenStack system is deployed on PMs (three physical servers functioning as the controller nodes of the cascaded FusionSphere OpenStack). You need to add three physical servers as the controller nodes for each new cascaded FusionSphere OpenStack system.	-
SDN Form	Software SDN	Hardware SDN
Virtualization Type	KVM	KVM
Service Storage	IPSAN FusionStorage separated deployment FCSAN	IPSAN FusionStorage separated deployment FCSAN
Image Storage	OBS/Swift	OBS/Swift
Mongodb	SSD	SSD