openstack/tricircle
Code Issues Proposed changes
RETIRED, Tricircle is to provide networking automation across Neutron.
501 Commits 2 Branches 18 Tags 17 MiB
f6cd0e5061
Go to file
xiulin yin f6cd0e5061 Fix issues of multi-region devstack environment setup 
1. What is the problem
(1) Currently we only add bridge mapping for br-extern in RegionTwo by
default in plugin.sh, so if we only have one node for the tempest
test, we can not test the cases that network is created in physical
network of "extern".
(2) Keystone url is not configured explicitly in tricircle local
Neutron plugin configuration so local Neutron plugin may fail to connect
to central Neutron.
(3) In multi-pod installation, Nova services in node2 fail to talk to
placement API due to placement API configuration problem, which leads
to instance booting error.

2. What is the solution to the problem
(1) Add bridge mapping for br-extern both in RegionOne and RegionTwo
by default.
(2) Configure two options client.identity_url and client.auth_url in
plugin.sh to make sure local Neutron server can correctly connect to
central Neutron server.
(3) Update multi-pod installation guide to add a workaround for the
placement API problem.

3. What the features need to be implemented to the Tricircle
No new features.

Change-Id: I0925ee976a3bc7ce16b5ac19865c08dedb2de423
2017-02-15 16:39:26 +08:00
devstack Fix issues of multi-region devstack environment setup 2017-02-15 16:39:26 +08:00
doc/source Fix issues of multi-region devstack environment setup 2017-02-15 16:39:26 +08:00
etc Fix configuration file generator 2016-11-10 16:52:42 +08:00
releasenotes Update release notes for security group rule deletion 2017-02-13 22:12:22 -05:00
specs Change network type shared_vlan name to vlan 2017-01-17 10:51:24 +08:00
tricircle Merge "Fix get_pod_by_top_id method in common.utils" 2017-02-15 01:48:55 +00: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 Merge "Remove the unused oslo.versionedobjects requirement" 2017-02-14 02:07:58 +00:00
setup.cfg Remove support for py34 2017-02-09 10:42:07 +08:00
setup.py Manual sync from global-requirements 2016-05-26 13:23:29 +10:00
test-requirements.txt Updated from global requirements 2017-02-10 06:01:27 +00:00
tox.ini Support python3 in tricircle 2017-01-11 20:33:32 -05: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.