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.
Go to file
OpenDev Sysadmins 5362b6d75c OpenDev Migration Patch
This commit was bulk generated and pushed by the OpenDev sysadmins
as a part of the Git hosting and code review systems migration
detailed in these mailing list posts:

Attempts have been made to correct repository namespaces and
hostnames based on simple pattern matching, but it's possible some
were updated incorrectly or missed entirely. Please reach out to us
via the contact information listed at with any
questions you may have.
4 years ago
devstack Improvement the Tricircle work with nova cell2 5 years ago
doc/source Update installation-lbaas.rst 4 years ago
etc Use DocumentedRuleDefault instead of RuleDefault 6 years ago
playbooks OpenDev Migration Patch 4 years ago
releasenotes Add tricircle-status upgrade check command framework 5 years ago
specs fix error http links and fix http links to https links 5 years ago
tricircle gate fix 4 years ago
.coveragerc Align project files structure with cookiecutter template 7 years ago
.gitignore update zuul and tox builds 5 years ago
.gitreview OpenDev Migration Patch 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 OpenDev Migration Patch 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 fix misspelling of 'neutron' 5 years ago
index.rst [doc-migration] Reorganize the Tricircle doc/source folder 6 years ago
lower-constraints.txt gate fix 4 years ago
requirements.txt gate fix 4 years ago
setup.cfg Driver based implementation of Trunk, current implementation is plugin-based. 4 years ago Updated from global requirements 6 years ago
test-requirements.txt update zuul and tox builds 5 years ago
tox.ini Merge "Update UPPER_CONSTRAINTS_FILE for stable/stein" into stable/stein 4 years ago


Team and repository tags



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.