openstack
/
tricircle
Code Issues Proposed changes
RETIRED, Tricircle is to provide networking automation across Neutron.
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.
262 Commits
6 Branches
14 Tags
17 MiB
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'c58970a9eb'
${ noResults }
Go to file
Jenkins c58970a9eb
Merge "Implement force detach volume" 		7 years ago
cmd Move statless design from experiment to master branch 7 years ago
devstack Nova_APIGW Server Action Support(part1) 7 years ago
doc/source Fix the link error in the installation.rst 7 years ago
etc Add network type support to the Tricircle plugin 7 years ago
releasenotes Align project files structure with cookiecutter template 7 years ago
specs Merge "Add cross-pod L2 Networking spec file" 7 years ago
tricircle Merge "Implement force detach volume" 7 years ago
.coveragerc Align project files structure with cookiecutter template 7 years ago
.gitignore Change the gate to OpenStack infrastrucure 7 years ago
.gitreview Update .gitreview for new namespace 8 years ago
.testr.conf Add the Tricircle tempest plugin with a sample test case 7 years ago
CONTRIBUTING.rst Align project files structure with cookiecutter template 7 years ago
HACKING.rst Align project files structure with cookiecutter template 7 years ago
LICENSE Add source code to Tricircle 9 years ago
README.rst Fix the link error in the document README.rst 7 years ago
requirements.txt Updated from global requirements 7 years ago
setup.cfg The framework of dynamic pod binding 7 years ago
setup.py Manual sync from global-requirements 7 years ago
test-requirements.txt Updated from global requirements 7 years ago
tox.ini Drop *openstack/common* in flake8 exclude list 7 years ago

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.