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.
Jenkins 07468d25c2 Merge "Add configuration guide in the Tricircle" 5 years ago
cmd Merge "Unify the usage of the log module" 5 years ago
devstack Trival fix some typo 5 years ago
doc/source Merge "Add configuration guide in the Tricircle" 5 years ago
etc Fix configuration file generator 5 years ago
releasenotes Add release notes for the master branch 5 years ago
specs Merge "Layer-3 networking and combined bridge network spec" 5 years ago
tricircle Merge "Add configuration guide in the Tricircle" 5 years ago
.coveragerc Align project files structure with cookiecutter template 5 years ago
.gitignore Change the gate to OpenStack infrastrucure 6 years ago
.gitreview Update .gitreview for new namespace 6 years ago
.testr.conf Add the Tricircle tempest plugin with a sample test case 5 years ago
CONTRIBUTING.rst Align project files structure with cookiecutter template 5 years ago
HACKING.rst Align project files structure with cookiecutter template 5 years ago
LICENSE Add source code to Tricircle 7 years ago
README.rst Add configuration guide in the Tricircle 5 years ago
requirements.txt Updated from global requirements 5 years ago
setup.cfg Enable tricircle commands 5 years ago
setup.py Manual sync from global-requirements 5 years ago
test-requirements.txt Updated from global requirements 5 years ago
tox.ini PEP8 failed when import i18n more than one 5 years ago

README.rst

Team and repository tags

image

Tricircle

The purpose of the Tricircle project is to provide networking automation across Neutron servers in multi-region OpenStack clouds deployment.

Each OpenStack cloud includes its own Nova, Cinder and Neutron, the Neutron servers in these OpenStack clouds are called local Neuron servers, all these local Neutron servers will be configured with the Tricircle Local Neutron Plugin. A separate Neutron server will be installed and run standalone as the coordinator of networking automation across local Neutron servers, this Neutron server will be configured with the Tricircle Central Neutron Plugin, and is called central Neutron server.

Leverage the Tricircle Central Neutron Plugin and the Tricircle Local Neutron Plugin configured in these Neutron servers, the Tricircle can ensure the IP address pool, IP/MAC address allocation and network segment allocation being managed globally without conflict, and the Tricircle handles tenant oriented data link layer(Layer2) or network layer(Layer3) networking automation across local Neutron servers, resources like VMs, bare metal or containers of the tenant can communicate with each other via Layer2 or Layer3, no matter in which OpenStack cloud these resources are running on.

Note: There are some our own definitions of Layer2/Layer3 networking across Neutron. To make sure what they are, please read our design documentation, especially "6.5 L2 Networking across Neutron". The wiki and design documentation are linked below.

The Tricircle and multi-region OpenStack clouds will use shared KeyStone(with centralized or distributed deployment) or federated KeyStones.

The Tricircle source code is distributed under the terms of the Apache License, Version 2.0. The full terms and conditions of this license are detailed in the LICENSE file.