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).
Node Types and Deployment Details

Node Types and Deployment Details

Basic Management Nodes and Extended Management Nodes (Region Type I)

Basic management nodes are also called controller nodes. This type of node is mandatory in the Region Type I scenario and is used to deploy FusionSphere OpenStack controller nodes, basic cloud services, common components, and management domain components at the resource pool layer.

Management nodes need to be expanded due to the increase of compute nodes in the OpenStack system. For example, components such as GaussDB and RabbitMQ are separated from basic management nodes and deployed on extended management nodes.

The basic management node uses the UVP as the host OS, the cascading FusionSphere OpenStack is deployed on physical machines, and the cascaded FusionSphere OpenStack and Service OM are deployed on VMs. When FusionStorage is used as the management storage, FusionStorage is deployed on physical machines and FusionStorage Manager is deployed on VMs. Computing cloud services, storage cloud services, network cloud services, common components, and management domain components are deployed on VMs. Figure 3-6 shows the deployment details of the basic management nodes (Region Type I).

Figure 3-6 Deployment details of basic management nodes and extended management nodes

Basic Management Nodes and Extended Management Nodes (Region Type II)

This node type is mandatory in the Region Type II scenario and is used to deploy FusionSphere OpenStack control nodes, basic cloud services, common components, and management domain components at the resource pool layer.

Management nodes need to be expanded due to the increase of compute nodes in the OpenStack system. For example, components such as GaussDB and RabbitMQ are separated from basic management nodes and deployed on extended management nodes.

The basic management node uses the UVP as the host OS, FusionSphere OpenStack is deployed on physical machines, and Service OM is deployed on VMs. When FusionStorage is used as the management storage, FusionStorage is deployed on physical machines and FusionStorage Manager is deployed on VMs. Computing cloud services, storage cloud services, network cloud services, common components, and management domain components are deployed on VMs. Figure 3-7 shows the deployment details of the basic management nodes (Region Type II).

Figure 3-7 Deployment details of basic management nodes and extended management nodes

Basic Management Nodes and Extended Management Nodes (Region Type III)

This node type is mandatory in the Region Type III scenario and is used to deploy FusionSphere OpenStack control nodes, basic cloud services, common components, and management domain components at the resource pool layer.

Management nodes need to be expanded due to the increase of compute nodes in the OpenStack system. For example, components such as GaussDB and RabbitMQ are separated from basic management nodes and deployed on extended management nodes.

The basic management node uses the UVP as the host OS, FusionSphere OpenStack is deployed on physical machines, and Service OM is deployed on VMs. When FusionStorage is used as the management storage, FusionStorage is deployed on physical machines and FusionStorage Manager is deployed on VMs. Computing cloud services, storage cloud services, network cloud services, common components, and management domain components are deployed on VMs. Figure 3-8 shows the deployment details of the basic management nodes (Region Type III).

Figure 3-8 Deployment details of basic management nodes and extended management nodes

Network Nodes (Region Type I)

This node type is mandatory in the Region Type I scenario and is used only for deploying software SDN components in the Region Type I scenario. Region Type II and Region Type III do not require this node type.

The network node uses the UVP as the host OS. The vRouter, L3NAT, L3_service, and VPN components are deployed on VMs. Figure 3-9 shows the deployment details of the network nodes (Region Type I).

Figure 3-9 Deployment details of the network nodes

ECS and EVS Related Nodes

ECS and EVS related nodes are as follows:

  • KVM compute node (general-purpose ECS)

    This node type is mandatory and is used by the ECS service to provision general-purpose ECS instances (tenant VMs).

    The KVM compute node (general-purpose) uses the UVP as the host OS, and FusionSphere OpenStack (role compute) is deployed on physical machines.

  • KVM compute node (GPU ECS)

    This node type is optional and is used by the ECS service to provision general GPU ECS instances (tenant VMs).

    The KVM compute node (GPU ECS) uses the UVP as the host OS, and FusionSphere OpenStack (role compute) is deployed on physical machines.

  • Distributed storage node (EVS)

    This node type is optional. When FusionStorage is used as a service storage and FusionStorage separated deployment is adopted, this node is used by EVS services to provision EVS instances (tenant EVS disks).

    The distributed storage node (EVS) uses EulerOS as the host OS, and FusionStorage is deployed on physical machines.

  • Converged compute and storage node (ECS and EVS)

    This node type is optional. When FusionStorage is used as a service storage and FusionStorage is deployed in converged mode, this node is used by the ECS service to provision ECS instances (tenant VMs) and EVS instances (tenant EVS disks).

    The converged compute and storage node (ECS and EVS) uses the UVP as the host OS, and FusionSphere OpenStack (compute role) and FusionStorage is deployed on physical machines.

Figure 3-10 shows the deployment details of ECS and EVS related nodes.

Figure 3-10 Deployment details of ECS and EVS related nodes

BMS Related Nodes

BMS related nodes are as follows:

  • Cascaded OpenStack BMS management node

    This node type is optional. This node type is used only when the BMS cloud service is used in the Region Type I scenario and is used to deploy the cascaded FusionSphere OpenStack. Region Type II and Region Type III do not require this node type.

    This type of nodes use the UVP as the host OS. The cascaded FusionSphere OpenStack is deployed on VMs. When FusionStorage is used as the management storage, FusionStorage is deployed on physical servers.

  • BMS gateway node

    This node type is optional. This node type is used only when the BMS cloud service is used in the Region Type I scenario and is used to deploy FusionSphere OpenStack (role baremetal-gateway). Region Type II and Region Type III do not require this node type.

    The BMS gateway node uses the UVP as the host OS. FusionSphere OpenStack (baremetal-gateway role) is deployed on physical servers.

  • BMS node

    This node type is optional and is used by the BMS service to provision BMS instances (tenant physical machines).

    The BMS node uses the UVP as the host OS, and FusionSphere OpenStack (role baremetal-server) and FusionStorage is deployed on physical machines.

Figure 3-11 shows the deployment details of BMS related nodes.

Figure 3-11 Deployment details of BMS related nodes

SAP Cloud Nodes

SAP Cloud nodes are as follows:

  • SAP Cloud compute node (virtualization)

    This node type is optional. It is used by the ECS service to provision the SAP HANA ECS instances (tenant SAP HANA VMs).

    The SAP Cloud compute node (virtualization) uses the UVP as the host OS, and FusionSphere OpenStack (role compute) is deployed on physical machines.

  • SAP Cloud compute node (BMS)

    This node type is optional. It is used by the ECS service to provision the SAP HANA ECS instances (tenant SAP HANA physical machines).

    The SAP Cloud compute node (BMS) uses the UVP as the host OS. FusionSphere OpenStack (baremetal-server role) is deployed on physical servers.

Figure 3-12 shows the deployment details of SAP Cloud related nodes.

Figure 3-12 Deployment details of SAP Cloud related nodes

CSBS and VBS Related Nodes

The eBackup Server&Proxy node is optional. This node type is used only when the CSBS or VBS service is used. This node type is used to deploy eBackup Server&Proxy for CSBS and VBS.

The eBackup Server&Proxy node uses EulerOS as the host OS. Figure 3-13 shows the deployment details of the eBackup Server&Proxy nodes.

Figure 3-13 Deployment details of eBackup Server&Proxy nodes

CSHA Related Nodes

CSHA related nodes are as follows:

  • Cloud platform quorum server node (CSHA)

    This node type is optional. This node type is used only when the CSHA service is used. This node is used to deploy the cloud platform Arbitration component.

    The cloud platform quorum server node uses EulerOS as the host OS, and the cloud platform Arbitration component is deployed on physical machines.

  • Storage arbitration server node (CSHA)

    This node type is optional. This node type is used only when the CSHA service is used. This node is used to deploy the arbitration service.

    The cloud platform quorum server node uses EulerOS as the host OS, and the storage quorum server is deployed on physical machines.

  • IAM quorum server node (CSHA)

    This node type is optional. This node type is used only when the CSHA service is used. This node is used to deploy the IAM arbitration services.

    The IAM quorum server node uses EulerOS as the host OS, and the IAM quorum server is deployed on physical machines.

Figure 3-14 shows the deployment details of CSHA related nodes.

Figure 3-14 Deployment details of CSHA related nodes

OBS Related Nodes

OBS related nodes are as follows:

  • Object storage LVS node (OBS)

    This node type is optional. This node type is used only when the OBS service is used. This node is used to deploy the LVS (used only by OBS).

    The object storage LVS node uses EulerOS as the host OS, and LVS is deployed on physical machines.

  • Object storage node (OBS)

    This node type is optional. This node type is used only when the OBS service is used. This node is used to deploy FusionStorage Object.

    The object storage node uses EulerOS as the host OS, and FusionStorage Object is deployed on physical machines.

Figure 3-15 shows the deployment details of OBS related nodes.

Figure 3-15 Deployment details of OBS related nodes

HDS and ADS Related Nodes

HDS and ADS related nodes are as follows:

  • Hadoop management node (HDS)

    This node type is optional. This node type is used only when the HDS service is used. This node is used to deploy FusionInsight HD.

    The Hadoop management node uses EulerOS as the host OS, and FusionInsight HD is deployed on physical machines.

  • Hadoop control node (HDS)

    This node type is optional. This node type is used only when the HDS service is used. This node is used to deploy FusionInsight HD.

    The Hadoop control node uses EulerOS as the host OS, and FusionInsight HD is deployed on physical machines.

  • Hadoop data node (HDS)

    This node type is optional. This node type is used only when the HDS service is used. This node is used to deploy FusionInsight HD.

    The Hadoop data node uses EulerOS as the host OS, and FusionInsight HD is deployed on physical machines.

  • LibrA management node (ADS)

    This node type is optional. This node type is used only when the ADS service is used. This node is used to deploy FusionInsight LibrA.

    The LibrA management node uses EulerOS as the host OS, and FusionInsight LibrA is deployed on physical machines.

  • LibrA data node (ADS)

    This node type is optional. This node type is used only when the ADS service is used. This node is used to deploy FusionInsight LibrA.

    The LibrA data node uses EulerOS as the host OS, and FusionInsight LibrA is deployed on physical machines.

Figure 3-16 shows the deployment details of HDS and ADS related nodes.

Figure 3-16 Deployment details of HDS and ADS related nodes
Translation
Download
Updated: 2019-10-23

Document ID: EDOC1100063247

Views: 74428

Downloads: 192

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