requirements_projects:multisite_gap_analysis
This is an old revision of the document!
| Cells | Regions | Heat support multi-regions | Tricircle | Propriety orchestration layer with multi-regions | |
|---|---|---|---|---|---|
| Pros. | A single Nova API endpoint for scaling out nova within a region | Discrete regions with separate API endpoints and no coordination between regions. | Heat as the multi-site orchestration engine for discrete regions | https://github.com/stackforge/tricircle | Propriety orchestration layer as the multi-site orchestration engine for discrete regions |
| Cons. | Only Nova can scale out for multi-site. Using RPC message(including Nova Cinder Neutron) for cross-site communication, difficult for cross-site integration, upgrade, trouble shooting. Image service shared in multi-site, no solution for multi-site image management. No clear Ceilometer solution used in multi-site: Shared or multi-Ceilometer? | Tenant’s resources are discrete and not connected by tenant’s isolated network.Networking across different site has to be set up manually.Lots of discrete service endpoints. No global quota control. | Currently only VPN supported for project level cross-site networking automation.No solution for image management and distribution across multi-sites.Still Lots of discrete Nova /Cinder /Neutron /Ceilometer service endpoints, no good solution for global consistent resource view and quota control. | Only Propriety API exposed, the ecosystem of OpenStack API is masked. Currently only VPN supported for project level cross-site networking automation. No solution for image management and distribution across multi-sites.Still Lots of discrete Nova /Cinder /Neutron /Ceilometer service endpoints, no good solution for global consistent resource view and quota control. | |
| Common Cons. | Only VPN supported for project level isolated cross-OpenStack networking, proper L2/L3 cross-OpenStack networking for VNFs should be identified and developed. | Only VPN supported for project level isolated cross-OpenStack networking, proper L2/L3 cross-OpenStack networking for VNFs should be identified and developed. | Only VPN supported for project level isolated cross-OpenStack networking, proper L2/L3 cross-OpenStack networking for VNFs should be identified and developed. | ||
| Shared services | Keystone, Nova-API, Cinder, Neutron, Glance, Ceilometer | Keystone | Heat | Propriety orchestration layer |
New identified upstream project that could address the issue are more than welcomed to be added in the above table
requirements_projects/multisite_gap_analysis.1424947689.txt.gz · Last modified: 2015/02/26 10:48 by Zhipeng Huang
Except where otherwise noted, content on this wiki is licensed under the following license: Creative Commons Attribution 4.0 International License
