Skip to content
Tricircle is to provide networking automation across Neutron.
Branch: master
Clone or download
Permalink
Type Name Latest commit message Commit time
Failed to load latest commit information.
devstack Replace git.openstack.org URLs with opendev.org URLs Apr 24, 2019
doc/source Replace git.openstack.org URLs with opendev.org URLs Apr 24, 2019
etc Use DocumentedRuleDefault instead of RuleDefault Oct 18, 2017
playbooks OpenDev Migration Patch Apr 19, 2019
releasenotes
specs
tricircle
.coveragerc Align project files structure with cookiecutter template Jul 5, 2016
.gitignore update zuul and tox builds Dec 5, 2018
.gitreview
.stestr.conf update zuul and tox builds Dec 5, 2018
.testr.conf Add the Tricircle tempest plugin with a sample test case Jun 8, 2016
.zuul.yaml
CONTRIBUTING.rst Update links in CONTRIBUTING.rst Jun 20, 2018
HACKING.rst Update the documentation link for doc migration Jul 19, 2017
LICENSE Add source code to Tricircle Sep 25, 2014
README.rst Replace git.openstack.org URLs with opendev.org URLs Apr 24, 2019
index.rst [doc-migration] Reorganize the Tricircle doc/source folder Jul 26, 2017
lower-constraints.txt add provider network segmentation raise Apr 24, 2019
requirements.txt add provider network segmentation raise Apr 24, 2019
setup.cfg Add the penstack-python3-train-jobs template Jun 28, 2019
setup.py Updated from global requirements Mar 3, 2017
test-requirements.txt update zuul and tox builds Dec 5, 2018
tox.ini Add Python 3 Train unit tests Jul 5, 2019

README.rst

Team and repository tags

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.

You can’t perform that action at this time.