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


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


FusionCloud 6.3.0 Solution Description 05

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


Figure 10-6 shows the logical architecture of VPC.

Figure 10-6 Logical architecture of VPC
Table 10-1 Component details




Console layer


Provides level-1 load balancing.


Provides level-2 load balancing.

Network Console

You can use this console to manage all VPC-related resources.

API/service layer


Provides load balancing for Combined APIs.

Network Service

Provides interfaces for the Network Console to manage VPC resources.

Common component

API Gateway

Third-party applications call cloud service APIs through API Gateway.


Provides the resource metering and billing function.


Provides domain name resolution and time synchronization.


Displays the task status.

Resource pool


Provides the Image Management Service (IMS).


Manages the life cycle of computing cloud servers in the FusionSphere OpenStack system, for example, creating cloud servers in batches, and scheduling or stopping cloud servers on demand.


Provides persistent block storage for running cloud servers. Its pluggable drives facilitate block storage creation and management.


Provides APIs for network connectivity and addressing.

Management zone


Provides Identity and Access Management (IAM).


Provides performance monitoring and alarm generation.

Service OM

Provides FusionSphere OpenStack management and resource configuration.


Provides the resource metering and billing function using SDR.


Figure 10-7 shows the VPC workflow.

Figure 10-7 VPC workflow

The tasks in all steps are as follows:

  1. Create a VPC on the VPC UI and invoke the VPC interface provided by the Network Service to deliver configurations. When creating an instance on the console, select the VPC to add the NIC of the instance to the VPC.
  2. The Network Service invokes the network, subnet, and router interfaces provided by the OpenStack Neutron to create a VPC.
  3. Type I scenario: The Neutron server uses the RPC to instruct the Neutron agent to create subnets and networks and configure the network namespace for routes of the Linux operating system.

    Type II scenario: The Neutron server uses the RPC to instruct the Neutron agent to create subnets and networks, and controls the AC to configure the VRF of the physical switch.

    Type III scenario: The Neutron server uses the RPC to instruct the Neutron agent to create subnets and networks.

Updated: 2019-04-23

Document ID: EDOC1100026685

Views: 162430

Downloads: 264

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