Difference between revisions of "OpenStack cascading solution"
Chaoyi Huang (talk | contribs) (→Repository) |
Chaoyi Huang (talk | contribs) |
||
| Line 24: | Line 24: | ||
* Or, leave customer with splitted resource island without any association… | * Or, leave customer with splitted resource island without any association… | ||
| − | = | + | = OpenStack cascading architecture = |
| + | [tbd] | ||
| + | |||
| + | = Advantage of the architecture = | ||
= Use Case = | = Use Case = | ||
| − | |||
| − | |||
| − | |||
[tbd] | [tbd] | ||
| Line 36: | Line 36: | ||
= Blueprints = | = Blueprints = | ||
| − | |||
The blueprints are: | The blueprints are: | ||
[tbd] | [tbd] | ||
| Line 43: | Line 42: | ||
[tbd] | [tbd] | ||
| − | = How | + | = How to Play = |
[tbd] | [tbd] | ||
Revision as of 08:12, 3 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, etc.
- Difficult for heterogeneous vendor’s infrastructure integration, multi-vendor's infrastructure co-existence 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…
OpenStack cascading architecture
[tbd]
Advantage of the architecture
Use Case
[tbd]
Meetings
[tbd]
Blueprints
The blueprints are: [tbd]
Proof of Concept
[tbd]
How to Play
[tbd]
Github Repository
[tbd]
Last update
July 2, 2014
