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 Principle

Implementation Principle

Logical Architecture

Figure 16-5 ECS logical architecture
Table 16-9 Component details




Console layer


Provides level-1 load balancing.


Provides level-2 load balancing.


ECS UI is a console centered on the ECS service and manages relevant resources.

Service/API layer


Provides load balancing capabilities for Combined APIs.

Combined API

Provides the backend service for ECS, serves as the server side of the ECS UI, and can call FusionSphere OpenStack components. Requests sent by an ECS from the console are forwarded by ECS UI to Combined API and are returned to ECS UI after being processed by Combined API.

Public component

API Gateway

Third-party applications call ECS APIs through the 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 environment, 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.


Collects alarms generated for hardware devices such as the host and the switch.

Service OM

Operations on host groups, USB ECSs, and ECS flavors are performed on Service OM.


Provides the resource metering and billing function using SDR.


Figure 16-6 shows the workflow for creating an ECS.

Figure 16-6 Workflow for creating an ECS

The tasks in all steps are as follows:

  1. Applying for an ECS is launched on the ECS console.
  2. The ECS API of the Combined API calls the VPC API of the Combined API.
  3. The VPC API calls Neutron or AC to create an EIP and interface.
  4. The ECS API of the Combined API calls the EVS API of the Combined API.
  5. The EVS API calls Cinder.
  6. Cinder creates volumes in the storage pool according to storage resource application policies.
  7. The ECS API sends the request to Nova.
  8. Nova creates an ECS in the computing resource pool.
Updated: 2019-04-23

Document ID: EDOC1100026685

Views: 162329

Downloads: 264

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