Difference between revisions of "OpenStack cascading solution"
Chaoyi Huang (talk | contribs) |
Chaoyi Huang (talk | contribs) (→Proof of Concept) |
||
Line 70: | Line 70: | ||
{| class="wikitable" | {| class="wikitable" | ||
|- | |- | ||
− | ! | + | ! Member !! E-Mail !! Role |
|- | |- | ||
| Chaoyi Huang || joehuang@huawei.com || inventor, designer of Nova/Cinder/Glance cascading, code reviewer | | Chaoyi Huang || joehuang@huawei.com || inventor, designer of Nova/Cinder/Glance cascading, code reviewer |
Revision as of 01:36, 23 July 2014
Contents
Overview
OpenStack cascading solution is designed for large scale distributed cloud.
OpenStack cascading mainly concentrate on API aggregation, merging multiple child OpenStacks to work as a single Openstack in the tenant access API interface(Nova/Cinder/Neutron/Glance/Ceilometer API). For tenants, it is a single region, and multiple child OpenStacks are not visible which had already been aggregated and hidden by the parent OpenStack. The tenant can see multiple "available zones", and each child OpenStack exactly work internally as Amazon like availability zone.
- 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 Amazon 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…
Architecture of OpenStack cascading
For detailed architecture design, please refer to
- Google Doc: Build large scale distributed cloud with OpenStack cascading
- Slide Share:
The OpenStack cascading includes cascading of Nova, Cinder, Neutron, Glance and Ceilometer. KeyStone will be global service shared by cascading and cascaded OpenStacks, and Heat will consume cascading OpenStack API. Therefore no cascading is required for KeyStone and Heat.
- Nova-Proxy: Transfer the VM operation to cascaded Nova. Also responsible for attach volume and network to the VM in the cascaded OpenStack.
- Cinder-Proxy: Transfer the volume operation to cascaded Cinder.
- L2-Proxy: Finish L2-networking in the cascaded OpenStack, including cross OpenStack networking.
- L3-Proxy: Finish L3-networking in the cascaded OpenStack, including cross OpenStack networking.
- FW-Proxy: implementation not started
- LB-Proxy: implementation not started
- VPN-Proxy: implementation not started
- Sync-Manager: Synchronize image among the cascading and policy determined Cascaded OpenStacks
- Ceilometer-Proxy: Transfer the request to destined Ceilometer or collect information from several Ceilometer. Implementation not started
Advantage of the architecture
[tbd]
Use Case
[tbd]
Meetings
[tbd]
Blueprints
The blueprints are: [tbd]
Proof of Concept
Member | Role | |
---|---|---|
Chaoyi Huang | joehuang@huawei.com | inventor, designer of Nova/Cinder/Glance cascading, code reviewer |
Hongning Wu | wuhongning@huawei.com | inventor, designer of Neutron cascading, code reviewer |
Fan Qin | qinfan@huawei.com | developer of Nova cascading |
Chi Zhang | z.zhangchi@huawei.com | developer of Cinder cascading |
Haojie Jia | jiahaojie@huawei.com | developer of Neutron cascading |
Dong Jia | jiadong.jia@huawei.com | developer of Glance cascading |
Example | Example | Example |
How to Play
[tbd]
Github Repository
[tbd]
Last update
July 2, 2014