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 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 Principle

Implementation Principle


Figure 18-5 ECS logical architecture
Table 18-18 Component details




ECS_UI is a console centered on the Elastic Cloud Server (ECS) service and manages relevant resources.

Combined API (ECS)

Provides a backend service for ECSs. It can be seen as the server end of 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.

Resource pool

  • Glance: Provides image management service.
  • Nova: Manages the life cycle of compute instances in the FusionSphere OpenStack environment, for example, creating instances in batches, and scheduling or stopping instances on demand.
  • Cinder: Provides persistent block storage for running instances. Its pluggable drives facilitate block storage creation and management.
  • Neutron: Provides APIs for network connectivity and addressing.

Unified Authentication

Provides Identity and Access Management (IAM) during login.

Common Component

Combined API reports ECS quota, order, product information, and metering and charging information to the ManageOne operation module.

Unified O&M

Combined API reports ECS log, monitoring, and alarm information to the ManageOne O&M module.


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

Figure 18-6 Workflow for creating an ECS

The steps in the figure above are as follows:

  1. The user requests an ECS on the ECS console.
  2. The ECS API of Combined API calls the VPC API of Combined API.
  3. The VPC API calls Neutron or AC to create an EIP or a port.
  4. The ECS API of Combined API calls the EVS API of 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 compute resource pool.
Updated: 2019-10-23

Document ID: EDOC1100063247

Views: 73737

Downloads: 192

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