openstack
/
tricircle
Code Issues Proposed changes
RETIRED, Tricircle is to provide networking automation across Neutron.
538 Commits 2 Branches 18 Tags 17 MiB
Go to file
southeast02 c361c8b98c Remove .testrepository/times.dbm from tox.ini 
1. What is the problem
When running tox for the first time, if you run "tox -e py35" ahead of
"tox -e py27", then "tox -e py27"  will fail. And if you run "tox -e
py27" ahead of py35 test, the py35 execution fails with an error saying
"db type could not be determined". In other case, If you execute "tox
run" instead of running py27, py35, pep8 and pypy test respectively, the
py35, pypy and pep8 can all pass the test except the py27. This bug is
reported here[1].

2. What is the solution to the problem
This issue can be solved by removing .testrepository/times.dbm
from tox.ini.

3. What the features need to be implemented to the Tricircle
to realize the solution
None.

[1] https://bugs.launchpad.net/testrepository/+bug/1229445

Change-Id: I497aa835fc5551b7422741216aa1c702f7aa6f0b
 		2017-03-28 22:30:18 +08:00
devstack Shared VxLAN (Part1: shadow agent) 2017-03-13 14:02:40 +08:00
doc/source Shared VxLAN (Part1: shadow agent) 2017-03-13 14:02:40 +08:00
etc Fix configuration file generator 2016-11-10 16:52:42 +08:00
releasenotes Enable allowed address pairs 2017-03-20 15:23:46 +08:00
specs spec on asynchronous job management 2017-03-20 14:50:53 +08:00
tricircle Fix the note description error 2017-03-22 20:06:50 +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 Shared VxLAN (Part1: shadow agent) 2017-03-13 14:02:40 +08: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.