openstack
/
tricircle
Code Issues Proposed changes
RETIRED, Tricircle is to provide networking automation across Neutron.
282 Commits 2 Branches 18 Tags 17 MiB
Go to file
zhiyuan_cai b0789882eb Central and local plugin (part 1, base) 
1. What is the problem
As discussed in the feature specification[1], we are going to
move the process of networking automation from the Nova-APIGW
to Neutron server.

2. What is the solution to the problem
Implement a new Neutron core plugin which runs in local Neutron
server to finish the networking automation process. Also, the
original Neutron core plugin is renamed as central plugin and
needs some changes to work with local plugin.

3. What the features need to be implemented to the Tricircle
   to realize the solution
With this patch, users can boot a virtual machine directly via
the local Nova server. But security group support is not covered.

DevStack script and local.conf sample are also updated.

[1] https://github.com/openstack/tricircle/blob/master/specs/ocata/local-neutron-plugin.rst

Change-Id: I6a3dc5e9af395e3035a7d218264a08b6313a248d
 		2016-10-10 22:58:00 -04:00
cmd Move statless design from experiment to master branch 2016-01-14 12:56:57 +08:00
devstack Central and local plugin (part 1, base) 2016-10-10 22:58:00 -04:00
doc/source Fix some fuzzy descriptions in the installation.rst 2016-09-29 10:20:25 +08:00
etc Add network type support to the Tricircle plugin 2016-06-21 20:11:24 +08:00
releasenotes Enable release notes translation 2016-10-06 20:55:28 +02:00
specs Specification for local Neutron plugin 2016-09-29 09:32:01 +08:00
tricircle Central and local plugin (part 1, base) 2016-10-10 22:58:00 -04: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 Update README and setup description after splitting 2016-10-02 17:05:57 +08:00
requirements.txt Updated from global requirements 2016-10-06 17:03:46 +00:00
setup.cfg Merge "Update README and setup description after splitting" 2016-10-09 01:45:27 +00:00
setup.py Manual sync from global-requirements 2016-05-26 13:23:29 +10:00
test-requirements.txt Updated from global requirements 2016-10-06 17:03:46 +00:00
tox.ini Update flake8 ignore list 2016-09-28 04:08:46 +00:00

README.rst

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 seperate 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.