openstack
/
tricircle
Code Issues Proposed changes
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.
831 Commits
6 Branches
14 Tags
17 MiB
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from 'stable/rocky'
${ noResults }
Go to file
OpenDev Sysadmins 79691440a8
OpenDev Migration Patch 		4 years ago
devstack Fix the smoke test error 5 years ago
doc/source Merge "change trircle endpoint creation method adjust to keystone api" 5 years ago
etc Use DocumentedRuleDefault instead of RuleDefault 6 years ago
playbooks OpenDev Migration Patch 4 years ago
releasenotes Update reno for stable/queens 5 years ago
specs Merge "spec for resource deleting" 5 years ago
tricircle Merge "use db utils from lib" 5 years ago
.coveragerc Align project files structure with cookiecutter template 7 years ago
.gitignore Use DocumentedRuleDefault instead of RuleDefault 6 years ago
.gitreview OpenDev Migration Patch 4 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
requirements.txt use db utils from lib 5 years ago
setup.cfg QoS implementation(Part1: Qos Plugin) 5 years ago
setup.py Updated from global requirements 6 years ago
test-requirements.txt Updated from global requirements 5 years ago
tox.ini Update UPPER_CONSTRAINTS_FILE for stable/rocky 5 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.