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

Logical Architecture

Figure 12-3 Logical architecture of EIP
Table 12-1 Component description




Console layer


Provides level-1 load balancing.


Provides level-2 load balancing.

Network Console

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

API/Service layer


Provides load balancing capabilities for Combined API.

Network Service

Provides interfaces for Network Console to manage VPC resources.

Common component

API Gateway

Third-party applications call ECS 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.


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


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


Provides APIs for network connectivity and addressing.

Management domain


Provides Identity and Access Management (IAM).



Service OM



Provides the resource metering and billing function using SDR.

Service Flow

Figure 12-4 EIP service flow

The tasks in all steps are as follows:

  1. When provisioning a BMS on the BMS UI, specify an EIP. When creating a VM on the ECS UI, specify an EIP. When creating an AS instance on the AS UI, specify an EIP. You can also configure an EIP on the EIP or ELB page of the VPC service. Each UI calls the EIP API provided by the VPC service to deliver the configuration.
  2. The VPC service calls the native floating IP API provided by FusionSphere OpenStack Neutron to configure the EIP and calls the native QoS API to configure the bandwidth.
  3. The Neutron server notifies the Neutron agent through RPC to create NAT specifications while triggering the task for configuring NGFW to limit the bandwidth.
Updated: 2019-04-23

Document ID: EDOC1100026685

Views: 152930

Downloads: 262

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