x/trio2o
Code Issues Proposed changes
Trio2o is to provide APIs gateway for multiple OpenStack clouds to act as a single OpenStack cloud.
251 Commits 2 Branches 12 Tags 4.1 MiB
Python 80.6%
Shell 15.1%
reStructuredText 4.3%
5e0b634248
Go to file
southeast02 5e0b634248 Synchronized patch: Nova API-Gateway Server Action Support(part1) 
1. What is the problem
Originally this patch has been committed to the Tricircle and provided
server action support, but after Tricircle narrowed its scope to
networking automation across Neutron, these API-Gateway features
implemented in this patch were no longer used. However Trio2o needs
these functions, so we plan to synchronize this patch from Gerrit
to Trio2o. You can find the old patch on Gerrit here[1].

The current Nova API-Gateway does not support following server actions:
   os-start: Start server
   os-stop: Stop server
   lock: Lock server
   unlock: Unlock server
   pause: Pause server
   unpause: Unpause server
   resume: Resume a suspended server and change its status to ACTIVE
   suspend: Suspend a server
   shelve: Shelves a server
   unshelve: Unshelves a server
   shelveOffload: Shelf-offloads or removes a shelved server
   migrate: Migrate a server to a host. The scheduler chooses the host
   forceDelete: Force-delete a server before deferred cleanup
   trigger_crash_dump: Trigger a crash dump in a server

2. What is the solution to the problem
Implement the above server actions.

3. What the features need to be implemented to the Trio2o
to realize the solution
Add the above server actions.

[1] https://review.openstack.org/#/c/366606/

Change-Id: Ie364735106f742e326b2aef5d961c418d55376c1
2017-04-12 09:51:31 +08:00
cmd Remove networking related code from the Trio2o 2016-11-14 02:12:48 -05:00
devstack Synchronized patch: Nova API-Gateway Server Action Support(part1) 2017-04-12 09:51:31 +08:00
doc/source Enable tempest test 2017-02-06 00:15:28 -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 Synchronized patch: Nova API-Gateway Server Action Support(part1) 2017-04-12 09:51:31 +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 Updated from global requirements 2017-04-07 06:18:25 +00:00
setup.cfg Synchronize some patches and fix the requirement.txt 2016-12-09 15:16:17 +08:00
setup.py Updated from global requirements 2017-04-07 06:18:25 +00:00
test-requirements.txt Fix the issue in tempest test for volumes 2017-04-10 12:46:05 +08:00
tox.ini Enable tempest test 2017-02-06 00:15:28 -05: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.