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).
Implementation Principles

Implementation Principles

Logical Architecture

This section describes VHA components and their positions in the system architecture layer by layer.

Figure 26-2 shows the logical architecture of VHA.

Figure 26-2 Logical architecture of VHA
Table 26-1 Component details

Type

Name

Description

Console

VHA

VHA management console.

Service

BCManager eReplication

VHA service system, which receives requests from the VHA management console.

Management domain

Operation Plane

Provide operation management for VHA, such as quota, metering and so on.

OM Plane

Provide operation and maintenance management for VHA, such as alarm, log and so on.

IAM

Provides identity and access management for VHA.

Service Flow

Figure 26-3 shows the workflow of VHA.

Figure 26-3 Service flow of VHA
  1. A VDC operator applies for an EVS disk HA service instance on the ManageOne operation plane.
  2. After receiving the task of creating DR protection, BCManager eReplication invokes Nova API to query the number of volumes mounted to ECSs.
  3. BCManager eReplication invokes Cinder API to create a HyperMetro secondary volume on the corresponding HyperMetro storage device, and query the capacity of volumes mounted to ECSs and obtains the corresponding storage device information.
  4. BCManager eReplication invokes DRExtend API to create HyperMetro pairs between the primary and secondary volumes. Add all HyperMetro pairs in the service instance to the HyperMetro consistency group.
  5. BCManager eReplication invokes Nova API to mount the created HyperMetro secondary volume to an ECS.
Translation
Download
Updated: 2019-10-23

Document ID: EDOC1100063247

Views: 64070

Downloads: 182

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