openstack/tricircle
Code Issues Proposed changes
RETIRED, Tricircle is to provide networking automation across Neutron.
870 Commits 2 Branches 18 Tags 17 MiB
69b845cb16
Go to file
Boden R 69b845cb16 update zuul and tox builds 
This patch updates the config for tox/zuul by:

- Switching the test running over to stestr like all other projects.
- Adding local tox targets for pep8, py27 and py3; see [1].
- Removes the git install of neutron and sfc from the testenv tox
target as those should be applied generically by the testenv target;
zuul will handle them in the gate and testenv:dev locally.
- Zuul.yaml is updated to properly define neutron and
sfc as required projects so they are pulled into the gate.
- Lower constraints job, tox target and constraints added.

[1] https://etherpad.openstack.org/p/neutron-sibling-setup

Change-Id: Ic840eb5b5b078252c6e69f2a94e3aba2e1f43cab
2018-12-05 07:59:55 -07:00
devstack Improvement the Tricircle work with nova cell2 2018-09-12 07:51:14 +00:00
doc/source fix error http links and fix http links to https links 2018-11-24 16:30:23 +08:00
etc Use DocumentedRuleDefault instead of RuleDefault 2017-10-18 01:02:55 +00:00
playbooks Move Zuul job definitions in repo 2018-09-22 09:12:12 +02:00
releasenotes Update reno for stable/rocky 2018-07-23 15:21:43 +00:00
specs fix error http links and fix http links to https links 2018-11-24 16:30:23 +08:00
tricircle use context manager from neutron-lib 2018-11-20 11:54:31 -07:00
.coveragerc Align project files structure with cookiecutter template 2016-07-05 15:08:41 +08:00
.gitignore update zuul and tox builds 2018-12-05 07:59:55 -07:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:41:25 +00:00
.stestr.conf update zuul and tox builds 2018-12-05 07:59:55 -07:00
.testr.conf Add the Tricircle tempest plugin with a sample test case 2016-06-08 12:51:38 +08:00
.zuul.yaml update zuul and tox builds 2018-12-05 07:59:55 -07: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
index.rst [doc-migration] Reorganize the Tricircle doc/source folder 2017-07-26 19:47:05 +08:00
LICENSE Add source code to Tricircle 2014-09-25 15:56:40 +08:00
lower-constraints.txt update zuul and tox builds 2018-12-05 07:59:55 -07:00
README.rst fix misspelling of 'neutron' 2018-02-22 11:18:35 +08:00
requirements.txt update zuul and tox builds 2018-12-05 07:59:55 -07:00
setup.cfg QoS implementation(Part1: Qos Plugin) 2017-11-24 16:01:04 +08:00
setup.py Updated from global requirements 2017-03-03 23:01:07 +00:00
test-requirements.txt update zuul and tox builds 2018-12-05 07:59:55 -07:00
tox.ini update zuul and tox builds 2018-12-05 07:59:55 -07: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 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.