x/trio2o
Code Issues Proposed changes
Trio2o is to provide APIs gateway for multiple OpenStack clouds to act as a single OpenStack cloud.
242 Commits 2 Branches 12 Tags 4.1 MiB
Python 80.6%
Shell 15.1%
reStructuredText 4.3%
c5951ef907
Go to file
CR_hui c5951ef907 Synchronize some patches and fix the requirement.txt 
1. What is the problem?
   A. After Removing networking related code from the Trio2o, there are
also some patches need to synchroniz.
   B. Kombu 4.0.1 was released and it's breaking everything 4.0.0 was
breaking.

2. What is the solution to the problem?
   A. Synchronize some patches and the IDs of these patches are:
             374559;
             373812;
             373616;
             378159;
             373891;
             375201;
   B. Fix the requirement.txt

3. What the features need to be implemented to the Tricircle to realize
the solution?
No new features.

Change-Id: Ie7e5ee6fc525455afdb0602f5ea7ba2b092f507b
2016-12-09 15:16:17 +08:00
cmd Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
devstack Synchronize some patches and fix the requirement.txt 2016-12-09 15:16:17 +08:00
doc/source Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
etc Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
releasenotes Merge "Enable release notes translation" 2016-11-17 07:44:19 +00:00
specs Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
trio2o Synchronize some patches and fix the requirement.txt 2016-12-09 15:16:17 +08:00
.coveragerc Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
.gitignore Change the gate to OpenStack infrastrucure 2015-12-15 12:09:09 +08:00
.gitreview Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
.testr.conf Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
CONTRIBUTING.rst Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
HACKING.rst Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
LICENSE Add source code to Tricircle 2014-09-25 15:56:40 +08:00
README.rst Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
requirements.txt Synchronize some patches and fix the requirement.txt 2016-12-09 15:16:17 +08:00
setup.cfg Synchronize some patches and fix the requirement.txt 2016-12-09 15:16:17 +08:00
setup.py Manual sync from global-requirements 2016-05-26 13:23:29 +10:00
test-requirements.txt Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
tox.ini Synchronize some patches and fix the requirement.txt 2016-12-09 15:16:17 +08:00

README.rst

Trio2o

The Trio2o provides an OpenStack API gateway to allow multiple OpenStack instances, spanning in one site or multiple sites or in hybrid cloud, to be managed as a single OpenStack cloud.

The Trio2o and these managed OpenStack instances will use shared KeyStone (with centralized or distributed deployment) or federated KeyStones for identity management.

The Trio2o presents one big region to the end user in KeyStone. And each OpenStack instance called a pod is a sub-region of the Trio2o in KeyStone, and usually not visible to end user directly.

The Trio2o acts as OpenStack API gateway, can handle OpenStack API calls, schedule one proper OpenStack instance if needed during the API calls handling, forward the API calls to the appropriate OpenStack instance.

The end user can see avaialbility zone(AZ) and use AZ to provision VM, Volume, through the Trio2o. One AZ can include many OpenStack instances, the Trio2o can schedule and bind OpenStack instance for the tenant inside one AZ. A tenant's resources could be bound to multiple specific bottom OpenStack instances in one or multiple AZs automatically.