openstack
/
tricircle
Code Issues Proposed changes
RETIRED, Tricircle is to provide networking automation across Neutron.
You cannot select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
934 Commits
5 Branches
15 Tags
17 MiB
master
stable/ussuri
stable/train
stable/stein
experiment
rocky-eol
queens-eol
pike-eol
ussuri-em
ocata-eol
train-em
stein-em
8.0.0
8.0.0.0rc1
rocky-em
queens-em
7.0.0
7.0.0.0rc1
pike-em
ocata-em
6.0.0
5.1.0
5.0.0
4.3.0
4.2.0
4.1.0
fortest-eol
newton-eol
icehouse-eol
4.0.0
3.4.0
mitaka-eol
3.3.0
3.2.0
3.1.0
3.0.0
2.1.0
2.0.2
2.0.1
v2.0.1
v2.0.0
stateful
poc-kilo
poc
v1.2.1
v1.2
v1.1
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'cac23fb92a'
${ noResults }
Go to file
OpenStack Release Bot cac23fb92a Update TOX/UPPER_CONSTRAINTS_FILE for stable/train 
Update the URL to the upper-constraints file to point to the redirect
rule on releases.openstack.org so that anyone working on this branch
will switch to the correct upper-constraints list automatically when
the requirements repository branches.

Until the requirements repository has as stable/train branch, tests will
continue to use the upper-constraints list on master.

Change-Id: I831ad5f5373f6e78a35ed1aa7a7833465c2b4304
 		4 years ago
devstack correct document link change openstack.org to opendev.org 4 years ago
doc/source clear the devspecs 4 years ago
etc Use DocumentedRuleDefault instead of RuleDefault 6 years ago
playbooks OpenDev Migration Patch 4 years ago
releasenotes Update master for stable/stein 4 years ago
specs correct document link change openstack.org to opendev.org 4 years ago
tricircle fix unit testcase can not pass 4 years ago
.coveragerc Align project files structure with cookiecutter template 7 years ago
.gitignore update zuul and tox builds 5 years ago
.gitreview Update .gitreview for stable/train 4 years ago
.stestr.conf update zuul and tox builds 5 years ago
.testr.conf Add the Tricircle tempest plugin with a sample test case 7 years ago
.zuul.yaml Add Python 3 Train unit tests 4 years ago
CONTRIBUTING.rst Update links in CONTRIBUTING.rst 5 years ago
HACKING.rst Update the documentation link for doc migration 6 years ago
LICENSE Add source code to Tricircle 9 years ago
README.rst Replace git.openstack.org URLs with opendev.org URLs 4 years ago
index.rst [doc-migration] Reorganize the Tricircle doc/source folder 6 years ago
lower-constraints.txt add provider network segmentation raise 4 years ago
requirements.txt add provider network segmentation raise 4 years ago
setup.cfg Add the penstack-python3-train-jobs template 4 years ago
setup.py Updated from global requirements 6 years ago
test-requirements.txt update zuul and tox builds 5 years ago
tox.ini Update TOX/UPPER_CONSTRAINTS_FILE for stable/train 4 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 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.