1.What is the problem? In nova-apigw, there are some servers with volume attachments are not implemented: * List volume attachments for an instance; * Attach a volume to an instance; * Show a detail of a volume attachment; * Update a volume attachment; * Detach a volume from an instance. 2.What is the solution to the problem? This patch add three feature: * We can get the volume identified by the attachment ID. * We can get a list of all the attacned volumes. * Detach a volume identified by the attachment ID from the given server ID. 3.What the features need to be implemented to the Tricircle to realize the solution? The above three features. Change-Id: I76ad72ca5d54fca7c2c463b5c41f2a4151f11eb8
|7 years ago|
|cmd||7 years ago|
|devstack||7 years ago|
|doc/source||7 years ago|
|etc||7 years ago|
|releasenotes||7 years ago|
|specs||7 years ago|
|tricircle||7 years ago|
|.coveragerc||7 years ago|
|.gitignore||7 years ago|
|.gitreview||8 years ago|
|.testr.conf||7 years ago|
|CONTRIBUTING.rst||7 years ago|
|HACKING.rst||7 years ago|
|LICENSE||9 years ago|
|README.rst||7 years ago|
|requirements.txt||7 years ago|
|setup.cfg||7 years ago|
|setup.py||7 years ago|
|test-requirements.txt||7 years ago|
|tox.ini||7 years ago|
The Tricircle provides an OpenStack API gateway and networking automation funtionality 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 Tricircle and these managed OpenStack instances will use shared KeyStone (with centralized or distributed deployment) or federated KeyStones for identity management.
The Tricircle presents one big region to the end user in KeyStone. And each OpenStack instance called a pod is a sub-region of the Tricircle in KeyStone, and usually not visible to end user directly.
The Tricircle 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, and deal with tenant level L2/L3 networking across OpenStack instances automatically. So it doesn't matter on which bottom OpenStack instance the VMs for the tenant are running, they can communicate with each other via L2 or L3.
The end user can see avaialbility zone(AZ) and use AZ to provision VM, Volume, even Network through the Tricircle. One AZ can include many OpenStack instances, the Tricircle 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.
- Free software: Apache license
- Design documentation: Tricircle Design Blueprint
- Wiki: https://wiki.openstack.org/wiki/tricircle
- Installation with DevStack: https://github.com/openstack/tricircle/blob/master/doc/source/installation.rst
- Tricircle Admin API documentation: https://github.com/openstack/tricircle/blob/master/doc/source/api_v1.rst
- Source: https://github.com/openstack/tricircle
- Bugs: http://bugs.launchpad.net/tricircle
- Blueprints: https://launchpad.net/tricircle