Trio2o is to provide APIs gateway for multiple OpenStack clouds to act as a single OpenStack cloud.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenDev Sysadmins 4dad7184b0 OpenDev Migration Patch 2 months ago
devstack devstack install trio2o service endpoint with port 19996 9 months ago
doc/source Pod1 and RegionOne already exits after devstack installation 9 months ago
etc Remove networking related code from the Trio2o 2 years ago
releasenotes Merge "Enable release notes translation" 2 years ago
specs Remove networking related code from the Trio2o 2 years ago
trio2o update trio2o image filter 3 months ago
.coveragerc Remove networking related code from the Trio2o 2 years ago
.gitignore Change the gate to OpenStack infrastrucure 3 years ago
.gitreview OpenDev Migration Patch 2 months ago
.testr.conf Remove networking related code from the Trio2o 2 years ago
CONTRIBUTING.rst Remove networking related code from the Trio2o 2 years ago
HACKING.rst Remove networking related code from the Trio2o 2 years ago
LICENSE Add source code to Tricircle 4 years ago
README.rst Remove networking related code from the Trio2o 2 years ago
requirements.txt Updated from global requirements 2 years ago
setup.cfg [urgent]Adapt new Keystone URL 2 years ago
setup.py Updated from global requirements 2 years ago
test-requirements.txt Fix the issue in tempest test for volumes 2 years ago
tox.ini Enable tempest test 2 years ago

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.