RETIRED, Tricircle is to provide networking automation across Neutron.
Go to file
zhangxiaohan cd2609fa91 Modify code for release port when delete vm
1. What is the problem?

In a non-local network, delete a vm from one reigon, and use its port to
create a vm in another region, the port in the original region is not
released.

2. What is the solution to the problem?

Release port to down when delete a vm from one region, and change shadow
port 'name' and 'device_id' and 'device_owner' value if shadow port exist.
In the update port, according to the update before the port and the
updated port to determine whether to notify the Central updates.

3. What the features to be implemented in the Tricircle to realize the solution?

Because port be cached in neutron-openvswitch-agent, not delete port
when delete a vm from one region.

Signed-off-by: zhang xiaohan <zhangxiaohan@szzt.com.cn>
Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>
Change-Id: If6819bf67ea2d206cc735039d8c55733dae54ee9
2018-05-28 11:21:20 +08:00
devstack Fix the smoke test error 2018-02-11 09:08:48 +08:00
doc/source Fix indentation in Networking Guide 2018-03-27 15:54:02 +02:00
etc Use DocumentedRuleDefault instead of RuleDefault 2017-10-18 01:02:55 +00:00
releasenotes Update reno for stable/queens 2018-02-13 11:09:12 +00:00
specs Merge "spec for resource deleting" 2018-01-24 06:52:42 +00:00
tricircle Modify code for release port when delete vm 2018-05-28 11:21:20 +08:00
.coveragerc Align project files structure with cookiecutter template 2016-07-05 15:08:41 +08:00
.gitignore Use DocumentedRuleDefault instead of RuleDefault 2017-10-18 01:02:55 +00:00
.gitreview Update .gitreview for new namespace 2015-10-17 22:41:25 +00:00
.testr.conf Add the Tricircle tempest plugin with a sample test case 2016-06-08 12:51:38 +08:00
CONTRIBUTING.rst Align project files structure with cookiecutter template 2016-07-05 15:08:41 +08:00
HACKING.rst Update the documentation link for doc migration 2017-07-19 08:19:40 +00:00
LICENSE Add source code to Tricircle 2014-09-25 15:56:40 +08:00
README.rst fix misspelling of 'neutron' 2018-02-22 11:18:35 +08:00
index.rst [doc-migration] Reorganize the Tricircle doc/source folder 2017-07-26 19:47:05 +08:00
requirements.txt uncap eventlet 2018-04-11 12:06:40 -04:00
setup.cfg QoS implementation(Part1: Qos Plugin) 2017-11-24 16:01:04 +08:00
setup.py Updated from global requirements 2017-03-03 23:01:07 +00:00
test-requirements.txt Updated from global requirements 2018-03-23 02:01:54 +00:00
tox.ini Enable some off-by-default checks 2017-11-22 19:09:41 +08:00

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.