Difference between revisions of "OpenStack cascading solution"
Chaoyi Huang (talk | contribs) |
Chaoyi Huang (talk | contribs) |
||
| Line 10: | Line 10: | ||
* '''Cascaded OpenStack''': the child OpenStack, provisioning the VM, Volume and virtual Networking resources | * '''Cascaded OpenStack''': the child OpenStack, provisioning the VM, Volume and virtual Networking resources | ||
| − | = | + | = Challenges when building large scale cloud = |
| − | + | To build large scale OpenStack based cloud, for example, the cloud includes 1 million VMs or 100k hosts. There are big challenges | |
| + | |||
| + | Naturally, there are two ways to do that: | ||
| + | 1. scale up a single monolithic OpenStack region, but | ||
| + | * It’s a big challenge for a single OpenStack to manage scale for example 1 million VMs or 100K hosts. | ||
| + | * Can not obtain real fault isolation area like EC2’s available zone, all of the cloud are tighten up into one OpenStack because of shareing RPC message bus and database. | ||
| + | * Single huge monolithic system bring high risk with OAM & trouble shooting, and big challenge for even the most skilled Op team to handle SW rolling upgrade and configuration changes. | ||
| + | * Difficult for heterogeneous vendor’s infrastructure integration, multi-vendor's infrastructure co-existing is high demand for large scale cloud | ||
| + | 2. setup hundreds of OpenStack Regions with discrete API endpoint, but | ||
| + | * Have to buy or develop his own cloud management platform to integrate the discrete cloud into one cloud, and also, OpenStack API ecosystem is lost. | ||
| + | * Or, leave customer with splitted resource island without any association… | ||
| + | |||
| + | = Why OpenStack cascading works for large scale distributed cloud = | ||
= Use Case = | = Use Case = | ||
Revision as of 05:20, 2 July 2014
Contents
Overview
OpenStack cascading solution is designed for large scale distributed cloud.
- The parent OpenStack expose standard OpenStack API
- The parent OpenStack manage many child OpenStacks by using standard OpenStack API
- Each child OpenStack functions as a EC2 like available zone and is hidden by the parent OpenStack
- Cascading OpenStack: the parent OpenStack, providing API and scheduling and orchestration of Cascaded OpenStacks
- Cascaded OpenStack: the child OpenStack, provisioning the VM, Volume and virtual Networking resources
Challenges when building large scale cloud
To build large scale OpenStack based cloud, for example, the cloud includes 1 million VMs or 100k hosts. There are big challenges
Naturally, there are two ways to do that: 1. scale up a single monolithic OpenStack region, but
* It’s a big challenge for a single OpenStack to manage scale for example 1 million VMs or 100K hosts. * Can not obtain real fault isolation area like EC2’s available zone, all of the cloud are tighten up into one OpenStack because of shareing RPC message bus and database. * Single huge monolithic system bring high risk with OAM & trouble shooting, and big challenge for even the most skilled Op team to handle SW rolling upgrade and configuration changes. * Difficult for heterogeneous vendor’s infrastructure integration, multi-vendor's infrastructure co-existing is high demand for large scale cloud
2. setup hundreds of OpenStack Regions with discrete API endpoint, but
* Have to buy or develop his own cloud management platform to integrate the discrete cloud into one cloud, and also, OpenStack API ecosystem is lost. * Or, leave customer with splitted resource island without any association…
Why OpenStack cascading works for large scale distributed cloud
Use Case
[tbd]
Architecture
[tbd]
Meetings
[tbd]
Blueprints
The blueprints are: [tbd]
Proof of Concept implementation and demo
[tbd]
How To Install and Test
[tbd]
Repository
[tbd]
Last update
July 2, 2014
