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 15-3 shows the logical architecture of IMS.

Figure 15-3 Logical architecture of IMS
Table 15-2 Component details




Console layer


Provides level-1 load balancing.


Provides level-2 load balancing.


Serves as a console centered on IMS and manages relevant resources.

Service/API layer


Provides load balancing capability for IMS.

Combined API (IMS)

Serves as the IMS background and the server side of the ECS UI (IMS), and can invoke FusionSphere OpenStack components. Requests sent by IMS from the console are forwarded by ECS UI (IMS) to Combined API (IMS) and are returned to ECS UI (IMS) after being processed by Combined API (IMS).

Common component

API Gateway

Used by third-party applications to call IMS APIs.


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


Manages identities and access.

Monitoring alarms

Provides alarm monitoring services.

Service OM

Provides cloud service O&M capabilities.

Service Flow

Figure 15-4 shows the service flow for creating an image using an ECS.

Figure 15-4 Creating an image from an ECS

The process of creating an image using an ECS is as follows:

  1. A user selects an ECS from the ManageOne operation plane to create an image. IMS finds the corresponding system disk based on the ECS.
  2. After receiving the request, Combined API checks and creates an image bucket.
  3. Combined API invokes the upload-to-image interface of the Cinder to create an image.
  4. Cinder invokes the Glance interface to create image metadata and invokes the glance image-upload interface to change the image status to active.

Except invoking VM creation API, other interfaces are invoked asynchronously. The timeout duration set by the IMS is eight hours. That is, if the timeout duration is longer than eight hours, the task times out.

Updated: 2019-04-23

Document ID: EDOC1100026685

Views: 160690

Downloads: 263

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