RETIRED, Tricircle is to provide networking automation across Neutron.
Go to file
CR_hui e3e533f666 Fix README.rst
1.What is the problem?
All links in the README must be under openstack.org not github.com
or google.com

2.What is the solution to the problem?
We fix the README.rst and index.rst

3.What the features need to be implemented to the Tricircle
  to realize the solution?
No new features.

Change-Id: I9f9e8f8334c93a11826d7fdf50d8c9fea86502a9
Closes-Bug: #1605188
2016-12-08 18:06:01 +08:00
cmd PEP8 failed when import i18n more than one 2016-12-02 03:12:44 +00:00
devstack Fix register tricircle endpoint failed 2016-12-02 12:50:27 +08:00
doc/source Fix README.rst 2016-12-08 18:06:01 +08:00
etc Fix configuration file generator 2016-11-10 16:52:42 +08:00
releasenotes Add release notes for the master branch 2016-10-26 09:17:23 +08:00
specs Specification for local Neutron plugin 2016-09-29 09:32:01 +08:00
tricircle Merge "PEP8 failed when import i18n more than one" 2016-12-02 05:52:42 +00: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
README.rst Fix README.rst 2016-12-08 18:06:01 +08:00
requirements.txt Updated from global requirements 2016-12-01 21:18:49 +00:00
setup.cfg Changed the home-page link 2016-12-01 09:04:50 +00:00
setup.py Manual sync from global-requirements 2016-05-26 13:23:29 +10:00
test-requirements.txt Updated from global requirements 2016-12-01 21:18:49 +00:00
tox.ini PEP8 failed when import i18n more than one 2016-12-02 03:12:44 +00:00

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