openstack/tricircle
Code Issues Proposed changes
251 Commits 2 Branches 18 Tags
a0482b8eb6
Go to file
zhiyuan_cai a0482b8eb6 Pre-created port clean during subnet deletion 
1. What is the problem
Before creating bottom subnet, we need to create some ports to
allocate ip address for bottom dhcp port and bottom gateway port.
These pre-created ports are not deleted after bottom resources
are deleted.

2. What is the solution to the problem
Clean these pre-created ports during top subnet deletion.

3. What the features need to be implemented to the Tricircle
   to realize the solution
Pre-created ports now can be cleaned up.

Change-Id: I73c0ef87e4104f1db9926a5972c5f36be94d724a
2016-09-23 13:58:57 +08:00
cmd
Move statless design from experiment to master branch
2016-01-14 12:56:57 +08:00
devstack
Nova_APIGW Server Action Support(part1)
2016-09-22 10:00:23 +08:00
doc/source
Fix the link error in the installation.rst
2016-09-12 17:22:52 +08:00
etc
Add network type support to the Tricircle plugin
2016-06-21 20:11:24 +08:00
releasenotes
Align project files structure with cookiecutter template
2016-07-05 15:08:41 +08:00
specs
Merge "Add cross-pod L2 Networking spec file"
2016-06-17 01:30:39 +00:00
tricircle
Pre-created port clean during subnet deletion
2016-09-23 13:58:57 +08:00
.coveragerc
Align project files structure with cookiecutter template
2016-07-05 15:08:41 +08:00
.gitignore
Change the gate to OpenStack infrastrucure
2015-12-15 12:09:09 +08:00
.gitreview
Update .gitreview for new namespace
2015-10-17 22:41:25 +00:00
.testr.conf
Add the Tricircle tempest plugin with a sample test case
2016-06-08 12:51:38 +08:00
CONTRIBUTING.rst
Align project files structure with cookiecutter template
2016-07-05 15:08:41 +08:00
HACKING.rst
Align project files structure with cookiecutter template
2016-07-05 15:08:41 +08:00
LICENSE
Add source code to Tricircle
2014-09-25 15:56:40 +08:00
MANIFEST.in
Align project files structure with cookiecutter template
2016-07-05 15:08:41 +08:00
README.rst
Fix the link error in the document README.rst
2016-09-11 16:37:17 +08:00
requirements.txt
Updated from global requirements
2016-09-21 11:58:00 +00:00
setup.cfg
py33 is no longer supported by Infra's CI
2016-09-21 08:51:24 +05:30
setup.py
Manual sync from global-requirements
2016-05-26 13:23:29 +10:00
test-requirements.txt
Updated from global requirements
2016-06-25 20:27:57 +00:00
tox.ini
Drop *openstack/common* in flake8 exclude list
2016-09-21 16:34:42 +08:00

README.rst

Tricircle

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.

Description
RETIRED, Tricircle is to provide networking automation across Neutron.
Readme 17 MiB