openstack
/
tricircle
Code Issues Proposed changes
RETIRED, Tricircle is to provide networking automation across Neutron.
725 Commits 2 Branches 18 Tags 17 MiB
Go to file
Yipei Niu ff97169485 [Urgent] fix tap_enabled for sfc 
1. What is the problem
A new change Icd4bf90d54f4edb443467b192e4e639fde749d4e is merged in
networking-sfc, making unit tests fail.

2. What is the solution for the problem
Add an attribute "tap_enabled" for PortPairGroup in the unit tests
for sfc, and set it as False.

3. What features need to be implemented to the Tricircle to
realize the solution
N/A.

Change-Id: I0e92117be9a2beed809538412832c6a884fa1b55
 		2017-10-25 08:46:37 +08:00
devstack Merge "Update plugin.sh and document for cellv2 integration" 2017-10-16 01:07:06 +00:00
doc/source Update plugin.sh and document for cellv2 integration 2017-09-20 16:53:01 +08:00
etc Use DocumentedRuleDefault instead of RuleDefault 2017-10-18 01:02:55 +00:00
releasenotes Update reno for stable/pike 2017-08-17 13:59:32 +00:00
specs Spec for smoke test engine 2017-07-10 11:58:54 +08:00
tricircle [Urgent] fix tap_enabled for sfc 2017-10-25 08:46:37 +08: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 Align project files structure with cookiecutter template 2016-07-05 15:08:41 +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 Change links in README to the newest addresses 2017-08-18 11:31:37 +08:00
index.rst [doc-migration] Reorganize the Tricircle doc/source folder 2017-07-26 19:47:05 +08:00
requirements.txt Updated from global requirements 2017-10-15 17:11:09 +00:00
setup.cfg Use DocumentedRuleDefault instead of RuleDefault 2017-10-18 01:02:55 +00:00
setup.py Updated from global requirements 2017-03-03 23:01:07 +00:00
test-requirements.txt Updated from global requirements 2017-09-24 12:30:24 +00:00
tox.ini Use DocumentedRuleDefault instead of RuleDefault 2017-10-18 01:02:55 +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 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.