RETIRED, Tricircle is to provide networking automation across Neutron.
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
OpenDev Sysadmins 775db474ca OpenDev Migration Patch 1 year ago
devstack Use tricircle cli instead of curl command 3 years ago
doc/source Fix bugs in tricircle Admin API 3 years ago
etc Fix configuration file generator 4 years ago
playbooks OpenDev Migration Patch 1 year ago
releasenotes Add release note for job pagination feature 3 years ago
specs Spec for smoke test engine 3 years ago
tricircle fix the test errors with stable pike make it work with python3 2 years ago
.coveragerc Align project files structure with cookiecutter template 4 years ago
.gitignore Change the gate to OpenStack infrastrucure 5 years ago
.gitreview OpenDev Migration Patch 1 year ago
.testr.conf Add the Tricircle tempest plugin with a sample test case 4 years ago
.zuul.yaml OpenDev Migration Patch 1 year ago
CONTRIBUTING.rst Align project files structure with cookiecutter template 4 years ago
HACKING.rst Update the documentation link for doc migration 3 years ago
LICENSE Add source code to Tricircle 6 years ago
README.rst update links in README file 3 years ago
index.rst [doc-migration] Reorganize the Tricircle doc/source folder 3 years ago
requirements.txt Updated from global requirements 3 years ago
setup.cfg Update the documentation link for doc migration 3 years ago
setup.py Updated from global requirements 4 years ago
test-requirements.txt Updated from global requirements 3 years ago
tox.ini fix the test errors with stable pike make it work with python3 2 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 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.