Huawei FusionSphere 5.1 Technical White Paper On OpenStack Cascading Technology (Cloud Data Center)
Huawei FusionSphere 5.1 Technical White Paper On OpenStack Cascading Technology (Cloud Data Center)
Huawei FusionSphere 5.1 Technical White Paper On OpenStack Cascading Technology (Cloud Data Center)
Code
Issue 01
Date 2015-04-20
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: http://enterprise.huawei.com
Purpose
This document describes the FusionSphere OpenStack cascading functions.
Intended Audience
This document is intended for Huawei marketing and sales engineers, as well as FusionSphere
distributors in their market development projects.
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not
avoided, will result in death or serious injury.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 1.0 (2015-04-20)
This issue is the first official release.
Contents
Only each OpenStack service architecture is understood, this problem can be easily answered.
OpenStack services typically consist of APIs, message buses, databases (DBs), and distributed
nodes supporting different backends.
OpenStack usually manages nova-compute, such as kernel-based virtual machines (KVMs)
and Xen, Cinder, such as Ceph and logical volume managers (LVMs), L2 and L3 agents, such
as open vSwitch (OVS), LinuxBridge, and Router, and Swift, such as Ceph and simple
storage service (S3).
Nova, Cinder, Neutron, Glance, and Ceilometer can be configured to the nova-compute
hypervisor, the cinder-volume storage backend, the network device used for the
interconnection of L2 and L3 agents, the Glance storage backend, and Ceilometer data
backend, respectively, using the OpenStack driver and agent mechanism.
Therefore, more OpenStack management and scheduling methods can be provided using the
OpenStack architecture and mechanism. This mode is called OpenStack cascading.
The cascading OpenStack system: provides APIs, scheduling, and orchestrating services, and
connects cascaded OpenStack systems.
The cascaded OpenStack system: is used to deploy VMs, volumes, and virtual network
resources.
1.8 Summary
OpenStack cascading allows one OpenStack system to manage other OpenStack systems,
provides unified OpenStack APIs, and centralizes management of multiple data centers.
Open architecture: The cascading OpenStack system provides two levels of standard
OpenStack APIs.
Plug-and-play integration: Any third-party infrastructure that provides standard
OpenStack APIs can be rapidly integrated into the OpenStack architecture.
Reliable fault isolation system: A single cascaded OpenStack system can manage 1024
servers, restricting the fault impacts within a single cascaded OpenStack system. Even if
the cascading OpenStack system fails, cascaded OpenStack systems are still manageable.
The system is highly available and fault-tolerant.
Isolation during an upgrade: A single cascaded OpenStack system is upgraded without
affecting other systems, and the system supports coexistence of multiple versions.
Upgrading a single component will not force the whole system to upgrade.
Horizontal expansion: Cascaded OpenStack systems provide horizontal expansion
capabilities at the server and cascaded OpenStack system levels from several to millions
of servers.
Multi-data center management and large-scale deployment: The OpenStack
architecture offloads a single OpenStack system by two-phase scheduling. In phase I, 1
million VMs can run on 100,000 servers, and in phase II, 10 million VMs can run on 1
million servers.
The cascading OpenStack system interconnects cascaded OpenStack systems in driver and agent mode
and provides the cascading service for Nova, Cinder, Neutron, and Ceilometer. As global components,
Keystone and Glance are deployed on the cascading OpenStack system.
The components in the cascading OpenStack system that interconnect with cascaded OpenStack systems
are called proxies.
The cascading OpenStack system typically has only AZ and host aggregate filtering algorithms
configured.
2.4.2 DVR