No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

FusionCloud 6.3.1.1 Solution Description 04

Rate and give feedback:
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Region Type II

Region Type II

FusionCloud consists of components that provide different functions. In the overall architecture, some components need to be deployed in Global with only one set, and some components need to be deployed in a single Region or multiple Regions. Figure 3-4 and Table 3-5 show the typical deployment architecture in the Region Type II scenario.

Figure 3-4 FusionCloud deployment architecture (Region Type II)
Table 3-5 Descriptions for the FusionCloud deployment architecture (Region Type II)

Function Layer

Component

Function Description

Infrastructure

Servers

  • Management nodes
    • Basic management node (control node): Mandatory and is used to deploy FusionSphere OpenStack, ManageOne, common components, and basic cloud services.
    • Agile Controller-DCN control node: Mandatory. It is used to deploy Agile Controller-DCN as the hardware SDN controller.
  • Service nodes (ECS/EVS)
    • KVM compute node (general): Mandatory and is used to generate ECS instances (KVM VM pool). The number of required KVM compute nodes is determined by the number of required ECS instances.
    • KVM compute node (GPU): Optional and is used to generate GPU enhanced ECS instances (KVM VM pool). The number of required KVM compute nodes is determined by the number of the required GPU enhanced ECS instances.
    • Compute and storage converged node: Optional and is used to deploy FusionStorage as a block storage resource pool in converged mode. This node is required when FusionStorage is selected for service storage.
    • Distributed storage node: Optional and is used to deploy FusionStorage as a block storage resource pool in separated mode. This node is required when FusionStorage is selected for service storage.
  • BMS

    BMS node: Optional and is used to generate BMS instances (bare metal server pool). The number of required BMS nodes is determined by the number of required BMS instances. This node type is required when the BMS service is selected.

  • SAP Cloud resource pool (computing + storage)
    • SAP Cloud compute node (virtualization): Optional and is used to generate SAP HANA ECS instances. The number of required SAP Cloud compute nodes is determined by the number of required SAP HANA ECS instances.
    • SAP Cloud compute node (BMS): Optional and is used to generate high-specification SAP HANA ECS instances. The number of SAP Cloud compute nodes is determined by the number of high-specification SAP HANA ECS instances.
  • DR and backup services
    • eBackup Server&Proxy node (CSBS/VBS): Optional and is used to deploy the backup management software eBackup Server&Proxy. This node type is required when the CSBS or VBS service is selected.
    • Quorum server node (CSHA): Optional and is used to deploy the cloud platform arbitration service. This node is required when CSHA is selected.
  • OBS
    • Object storage node (OBS): Optional and is used to deploy FusionStorage Object as the OBS backend. This node is required when OBS is selected.
    • Object storage LVS node (OBS): Optional and is used for OBS traffic load balancing. This server is required when OBS is selected.
  • Big data services
    • Hadoop data node (HDS): Optional and is used to deploy FusionInsight HD data nodes. This node is required when HDS is selected.
    • LibrA management node (ADS): Optional and is used to deploy FusionInsight LibrA management nodes. This node is required when the ADS is selected.
  • Compute node for VMware management: Optional. VMware services directly invoke the node without passing through FusionSphere OpenStack. This node is required when VMware services are selected.
  • Compute node for Hyper-V management: Optional. Hyper-V services directly invoke the node without passing through FusionSphere OpenStack. This node is required when Hyper-V services are selected.
  • Compute node for Power inventory management: Optional. Power service directly invokes the node without passing through FusionSphere OpenStack. This node is required when Power service is selected.
  • Compute node for Converged Network: Optional. Converged Network directly invokes the node without passing through FusionSphere OpenStack. This node is required when Converged Network is selected.

Storage devices

  • Management storage (management nodes): Optional and are used as the storage resource pools of management nodes. These nodes are required when IP SAN/FC SAN is selected as the management storage.
  • Enterprise storage (service node): Optional and is used to form the storage resource pool of service nodes. This node type is required when IP SAN/FC SAN is selected as the service storage.
  • All-flash storage (service nodes): Optional and are used as the storage resource pools of service nodes. These nodes are required when IP SAN/FC SAN is selected as the service storage.
  • Backup storage (CSBS/VBS): Optional and is required when CSBS or VBS is selected.
  • File storage (SFS): Optional and is required when the SFS service is selected.
  • Production storage (CSHA/VHA): Optional and is required when CSHA or VHA is selected.
  • Active-active storage (CSHA/VHA): Optional and is required when CSHA or VHA is selected.
  • Production storage (CSDR): Optional and is required when CSDR is selected.
  • DR storage (CSDR): Optional and is required when CSDR is selected.

Network devices

Network devices matching Agile Controller-DCN:

  • Core/aggregation switch: Provides TOR uplink aggregation and L2/L3 switching on the underlay network, and functions as a VXLAN gateway on the overlay network.
  • Access switch: Functions as a TOR on the underlay network to connect servers and storage devices. Functions as a Network Virtualization Edge (NVE) on the overlay network, that is, the virtual edge of a VXLAN network.
  • Firewall
    • Border firewall: Optional and is required in the following scenarios: security protection in the Mgt zone, and accessing the OBS service from a public network.
    • EdgeFW: Optional and is required when EdgeFW is selected.
    • VPN firewall: Connects to Agile Controller-DCN and provides the VPN resource pools.

Resource pools

FusionSphere OpenStack

  • FusionSphere OpenStack: Used to connect computing resource pools, storage resource pools of service storage, storage resource pools of management storage, and network resource pools. It is deployed on physical servers of basic management nodes.
  • Service OM: Provides cloud service O&M capabilities. It is deployed on VMs of basic management nodes.

Computing resource pool

  • KVM virtualization pool: KVM compute nodes are connected to the cascaded FusionSphere OpenStack.
  • Bare metal server pool: Optional. BMSs are connected to the cascaded FusionSphere OpenStack. This pool is required when the BMS service is selected.
  • SAP Cloud resource pool: Optional. SAP Cloud compute nodes are connected to the cascaded FusionSphere OpenStack. This pool is required when SAP Cloud is selected.

Storage resource pool

  • FusionStorage Block storage pool: FusionStorage connects to FusionSphere OpenStack as a block storage resource pool.
  • IP SAN/FC SAN storage pool: Storage devices are connected to FusionSphere OpenStack as storage resource pools.

Network resource pool

Network device access Agile Controller-DCN, providing network resource pools.

Big data pool

Optional and is invoked by the HDS and ADS services without passing through FusionSphere OpenStack. This pool is required when the HDS or ADS service is selected.

Database pool

Optional and is invoked by the RDS and Oracle Database Service without passing through FusionSphere OpenStack. This pool is required when the RDS and Oracle Database Service is selected.

Object storage pool

Optional. FusionStorage Object functions as the backend of the OBS service. This pool is required when OBS is selected.

DR storage pool

  • Optional. The active-active storage device connects to FusionSphere OpenStack as the resource pool. This pool is required when CSHA or VHA is selected.
  • Optional. The DR storage device connects to FusionSphere OpenStack as the resource pool. This pool is required when CSDR is selected.

Backup storage pool

Optional. The backup storage device connects to FusionSphere OpenStack as the backup storage pool. This pool is required when CSBS or VBS is selected.

File storage pool

Optional and is required when OceanStor 9000 provides file storage resources for the SFS service.

FusionStage pool

Optional and is invoked by the ServiceStage cloud service.

Resource pool of VMware inventory management

Optional. VMware services directly invoke the resource pool without passing through FusionSphere OpenStack. This pool is required when a VMware service is selected.

Resource pool of Hyper-V inventory management

Optional and is invoked by the Hyper-V service without passing through FusionSphere OpenStack. This pool is required when the Hyper-V service is selected.

Resource pool of Power inventory management

Optional. Power service directly invokes the resource pool without passing through FusionSphere OpenStack. This pool is required when Power service is selected.

Two-level cloud resource pool

Optional. The peer FusionCloud resource pool is connected to the local end. This pool is required when the two-level cloud is selected.

Resource pool of the management plane hybrid cloud

Optional. Public cloud resources are connected to the FusionCloud through API adaptation. This pool is required when the management plane hybrid cloud is selected.

Virtual resource pool

Optional. Virtual resource pools are centrally managed by FusionManager in FusionCloud, and cloud service resources, such as ECSs and EVS disks, in virtual resource pools managed by FusionManager are synchronized. This function is required when the virtual resource pool cloud service is selected.

Management domain

ManageOne

ManageOne: Provides cloud service operation management and system O&M management, including two-level cloud, LogCenter, vAPP, and management plane hybrid cloud, which are deployed on VMs of basic management nodes.

  • vAPP: Provides ECS, scaling group, and network resource orchestration, one-click deployment, and application autoscaling based on monitoring indicators. vAPP consists of one or multiple ECSs and works together with resources such as ECS networks to provide specific services.
  • LogCenter: Provides log management.
  • Two-level cloud: If the local FusionCloud private cloud resources are insufficient, the peer private cloud is connected, and you can quickly borrow resources from the peer resource pool.
  • Management plane hybrid cloud: It allows you to access and manage public cloud resources through API adaptation.
  • eSight
  • LogCenter
  • FusionCare
  • G-ray

Deployed on VMs of the basic management nodes.

  • eSight: Manages servers, storage devices, and network devices in a unified manner.
  • LogCenter: Provides log management.
  • FusionCare: A tool specific to O&M personnel for unified health check and FusionSphere offline log collection.
  • G-ray: A distributed call tracing system specific to O&M personnel. In the case of failed service operations, such as tenant VM creation failure, G-ray helps O&M personnel locate the fault and the component where the fault occurs.

Cloud services

Cloud service console

The consoles of basic cloud services are deployed on VMs of basic management nodes. The consoles of other cloud services are deployed on VMs of extended management nodes.

  • ECS UI: Provides the console for ECS, BMS, IMS, AS, EVS, ELB, and SAP HANA.
  • VPC Console: Provides a console page for VPC, SG, EIP, VFW, or VPN.
  • OBS Console: Optional. It provides a console page when OBS is selected.
  • SFS Console: Optional. It provides a console page when SFS is selected.
  • SCC Console: Optional. It provides a console page when ARS, SIS, SSA, EdgeFW, HSS, or DBSS is selected.
  • CSBS-VBS Console: Optional. It provides a console page when the CSBS or VBS service is selected.
  • CSDR Console: Optional. It provides a console page when CSDR is selected.
  • CSHA Console: Optional. It provides a console page when CSHA is selected.
  • VHA Console: Optional. It provides a console page when VHA is selected.
  • SMN Console: Optional. It provides a console page when the SMN (full version) is selected (not required for the simplified-version SMN).
  • ServiceStage Console: Optional. It provides a console page when ServiceStage is selected.
  • HDS Console: Optional. It provides a console page when HDS is selected.
  • ADS Console: Optional. It provides a console page when ADS is selected.
  • Oracle Console: Optional. It provides a console page when Oracle Database Service is selected.
  • RDS Console: Optional. It provides a console page when RDS for MySQL/PG/SQL Server is selected.
  • HiCloud Service Console: Optional. It provides a console page for VMware Service, Hyper-V Service, Power Service, and Converged Network.
  • Console of Virtual Resource Pool Cloud Service: Optional. It provides a cloud service console for virtualization resources to be managed by FusionManager in FusionCloud. This console is required when the Virtual Resource Pool Cloud Service is selected.

Cloud service backend

The backends of basic cloud services are deployed on VMs of basic management nodes. The backends of other cloud services are deployed on VMs of extended management nodes.

  • Combined API: Provides the service backend for ECS, BMS, IMS, EVS, and SAP HANA. It is also used to invoke the computing and storage resource pools.
  • ImageConvert: Provides the image conversion function for IMS.
  • AS: Optional. It works as an AS backend when AS is selected.
  • VPC: Provides backends for VPC, SG, EIP, ELB, VFW, and VPN, and invokes the network resource pool.
  • OceanStor DJ (Manila): Optional. It provides a backend for SFS when the SFS service is selected.
  • ARS: Optional. It provides a backend for ARS.
  • SIS: Optional. It provides a backend for SIS.
  • SSA: Optional. It provides a backend for SSA.
  • EdgeFW: Optional. It provides a backend for EdgeFW.
  • HSS: Optional. It provides a backend for HSS.
  • DBSS: Optional. It provides a backend for DBSS.
  • Karbor: Optional. It provides backends for CSBS and VBS and is responsible for backup policy scheduling and backup copy management. Karbor is required when CSBS or VBS is selected.
  • eBackup Manager&Workflow node: Optional. It is used to deploy the backup management software eBackup Manager&Workflow when the CSBS service is selected.
  • eReplication: It provides service backends for CSDR, CSHA, and VHA. This cloud service backend is required when CSDR, CSHA, or VHA is selected.
  • SMN: It provides a backend for SMN. Either the full-version or simplified-version SMN can be used.
  • ServiceStage: Optional. It provides a backend for ServiceStage.
  • HDS: Optional. It provides a backend for HDS.
  • ADS: Optional. It provides a backend for ADS.
  • RDS: Optional. It provides a backend for RDS.
  • Oracle: Optional. It provides a backend for Oracle Database Service.
  • HiCloud Service backend: Optional. It provides a backend for VMware Service, Hyper-V Service, Power Service, and Converged Network.

Common components

Common components are deployed on VMs of basic management nodes.

  • Linux Virtual Server (LVS): The Linux server cluster system provides level-1 load balancing for common services in FusionCloud.
  • Nginx: Provides a reverse proxy for the Console page of the cloud service to implement load balancing of services and data on each console node and distribute traffic. Cloud service requests are delivered by the LVS and forwarded to the Nginx. The Nginx forwards the cloud service requests to the cloud service console.
  • Deploy Management Kit (DMK): Provides a unified deployment and configuration platform on which services can be deployed and upgraded.
  • GaussDB: Provides common databases for cloud services.
  • EulerOS: The management VMs of each cloud service use EulerOS as the operating system.
  • DNS&NTP: The DNS provides the domain name resolution service for common services in FusionCloud. Network Time Protocol (NTP): Provides time synchronization services for common services in FusionCloud.
  • HAProxy: Provides load balancing for cloud services from the console node to service node. Cloud service requests are sent from the console node to HAProxy. Then HAProxy forwards the requests to the required cloud service node.
  • TaskCenter: Used to view the creation of service instances such as ECS.
  • Service Detail Record (SDR): Provides metering and charging files of each cloud service.
  • Cloud Configuration Service (CCS): Allows users to access third-party cloud resources based on FusionCloud, which supports cross-cloud management and deployment.
  • API Gateway: Provides API management as well as API intranet and extranet isolation functions. When a user accesses a cloud service API, the user does not call the service API directly, but accesses the API of the service registered on API Gateway. In this way, invalid requests are shielded, preventing the internal management API from being exposed.
  • Resource Template Service (RTS): Provides the resource orchestration function.
  • Arbitration: Optional. Provides the cloud platform arbitration function. This component is required when CSHA is selected.
Translation
Download
Updated: 2019-10-23

Document ID: EDOC1100063247

Views: 64896

Downloads: 182

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next