RETIRED, Tricircle is to provide networking automation across Neutron.
Go to file
zhangzs ed7f6ffb61 Update links in CONTRIBUTING.rst
Change-Id: I1b481f3042f6dbb8b748596ec19ef0ddd1e42a83
2018-06-20 10:36:31 +08:00
devstack Fix the smoke test error 2018-02-11 09:08:48 +08:00
doc/source Merge "change trircle endpoint creation method adjust to keystone api" 2018-06-01 07:15:13 +00:00
etc Use DocumentedRuleDefault instead of RuleDefault 2017-10-18 01:02:55 +00:00
releasenotes Update reno for stable/queens 2018-02-13 11:09:12 +00:00
specs Merge "spec for resource deleting" 2018-01-24 06:52:42 +00:00
tricircle Merge "load neutron objects using neutron-lib" 2018-06-01 04:10:19 +00:00
.coveragerc Align project files structure with cookiecutter template 2016-07-05 15:08:41 +08:00
.gitignore Use DocumentedRuleDefault instead of RuleDefault 2017-10-18 01:02:55 +00: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 Update links in CONTRIBUTING.rst 2018-06-20 10:36:31 +08:00
HACKING.rst Update the documentation link for doc migration 2017-07-19 08:19:40 +00:00
LICENSE Add source code to Tricircle 2014-09-25 15:56:40 +08:00
README.rst fix misspelling of 'neutron' 2018-02-22 11:18:35 +08:00
index.rst [doc-migration] Reorganize the Tricircle doc/source folder 2017-07-26 19:47:05 +08:00
requirements.txt load neutron objects using neutron-lib 2018-05-24 15:42:53 -06:00
setup.cfg QoS implementation(Part1: Qos Plugin) 2017-11-24 16:01:04 +08:00 Updated from global requirements 2017-03-03 23:01:07 +00:00
test-requirements.txt Updated from global requirements 2018-03-23 02:01:54 +00:00
tox.ini Enable some off-by-default checks 2017-11-22 19:09:41 +08:00


Team and repository tags



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 Neutron 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.