openstack
/
tricircle
Code Issues Proposed changes
RETIRED, Tricircle is to provide networking automation across Neutron.
547 Commits 2 Branches 18 Tags 17 MiB
Go to file
zhiyuan_cai fde488c99e Shared VxLAN (Part5: bulk create shadow port) 
1. What is the problem?
VLAN network has some restrictions that VxLAN network doesn't have.
For more flexible networking deployment, we consider supporting
cross-pod VxLAN network.

We are going to use shadow agent/port mechanism to synchronize VTEP
information and make cross-pod VxLAN networking available, as discussed
in the specification document[1].

In the previous implementation, we use a loop to create shadow ports
one by one. When there are large numbers of shadow ports need to be
created, the large numbers of API requests will affect the performance.

2. What is the solution to the problem?
Use bulk creation API to create shadow port.

3. What features need to be implemented to the Tricircle
to realize the solution?
This is the fifth patch for cross-pod VxLAN networking support, which
introduces the following changes:

(1) Use bulk API to create shadow ports
(2) Do not create resource routing entries for shadow ports

[1] https://review.openstack.org/#/c/429155/

Change-Id: I8b2dc98d84385433727e55584c80e1054fce406f
 		2017-03-30 11:58:01 +08:00
devstack Support WSGI deployment for Tricircle Admin API(part1) 2017-03-25 05:17:37 -04:00
doc/source Support WSGI deployment for Tricircle Admin API(part1) 2017-03-25 05:17:37 -04:00
etc Fix configuration file generator 2016-11-10 16:52:42 +08:00
releasenotes Support WSGI deployment for Tricircle Admin API(part1) 2017-03-25 05:17:37 -04:00
specs Merge "Cross-pod VxLAN network spec" 2017-03-30 01:13:54 +00:00
tricircle Shared VxLAN (Part5: bulk create shadow port) 2017-03-30 11:58:01 +08:00
.coveragerc Align project files structure with cookiecutter template 2016-07-05 15:08:41 +08:00
.gitignore Change the gate to OpenStack infrastrucure 2015-12-15 12:09:09 +08: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 Align project files structure with cookiecutter template 2016-07-05 15:08:41 +08:00
LICENSE Add source code to Tricircle 2014-09-25 15:56:40 +08:00
README.rst Change release note link to OpenStack docs site 2017-02-09 09:21:37 +08:00
requirements.txt Updated from global requirements 2017-03-21 15:02:21 +00:00
setup.cfg Support WSGI deployment for Tricircle Admin API(part1) 2017-03-25 05:17:37 -04:00
setup.py Updated from global requirements 2017-03-03 23:01:07 +00:00
test-requirements.txt Updated from global requirements 2017-03-03 23:01:07 +00:00
tox.ini Remove .testrepository/times.dbm from tox.ini 2017-03-28 22:30:18 +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 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.