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

Reminder

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

upgrade

FusionCloud 6.3.1.1 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 Principles

Implementation Principles

Architecture

The BMS service architecture contains the cloud service layer and FusionSphere OpenStack infrastructure layer.
  • The cloud service layer consists of the BMS Console layer and BMS Service layer.
    • The BMS Console layer consists of the BMS UI, which is the user interface of the BMS. It functions as the entry for user requests and uses IAM for identification and access management. The BMS UI is hosted in the ECS UI.
    • BMS Service layer contains BMS service and BMS plugin (SDR). BMS service is the logical processing layer of the BMS. It is hosted in combined API and uses eSight to monitor and generate alarms. BMS plugin (SDR) is an extension plug-in of the SDR system and is used for metering.
  • The infrastructure layer contains FusionSphere OpenStack management services and BMS resource pools. In the OpenStack system, Ironic is the core component used by the BMS service. Ironic provides management services for BMSs, and works with components such as Nova and Neutron. The BMS networking can be a virtual network consisting of only software or a network consisting of specialized hardware devices managed by a central controller. Different networking modes are used in different scenarios to provide you with similar user experience as ECSs.

Figure 20-2 shows the BMS logical architecture.

Figure 20-2 Logical architecture
Table 20-1 BMS component details

Type

Component Name

Description

Console layer

LVS

Provides level-1 load balancing.

Nginx

Provides level-2 load balancing.

ECS UI (BMS)

It is the portal of the BMS service. It is integrated into ECS UI.

Common Component

API-gateway

Forwards user requests to the BMS server.

BMS Plugin (SDR)

Provides the resource metering and billing function. BMS plug-in is SDR module for the BMS service. It is an extended plug-in of the SDR system. You do not need to add management resources.

DNS/NTP

Provides domain name resolution and time synchronization.

TaskCenter

Displays the task status.

API/Service layer

HAProxy

Provides load balancing for Combined APIs.

Combined API (BMS)

Functions as the BMS server and is integrated in Combined API. Combined API can call FusionSphere OpenStack components. Requests sent by a BMS 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

Ironic

Is deployed on FusionSphere OpenStack controller nodes in the BMS POD.

Nova

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.

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.

Glance

Provides the Image Management Service (IMS).

Swift

Provides the Object Storage Service (OBS).

Gauss DB

Provides the database service.

KeyStone

Provides the OpenStack authentication service.

Management

Metering

Provides the resource metering and billing function using SDRs.

IAM

Provides Identity and Access Management (IAM) for the BMS.

eSight

Provides performance monitoring and alarm generation.

Service OM

Provides O&M management.

Control Flow

Figure 20-3 BMS control flow
  1. A user applies for resources on the BMS GUI, and the request is sent to Combined API.
  2. Combined API (BMS) calls the interfaces of EVS, VPC, and IMS.
  3. VPC calls Neutron to create an EIP or a port. EVS calls Cinder to create a volume based on the policy for applying for storage resources. IMS calls Glance to query image information.
  4. BMS sends the creation request to Nova.
  5. Nova sends the request to Ironic to create a BMS instance.
Translation
Download
Updated: 2019-10-23

Document ID: EDOC1100063247

Views: 73503

Downloads: 192

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