openstack
/
tricircle
Code Issues Proposed changes
RETIRED, Tricircle is to provide networking automation across Neutron.
795 Commits 2 Branches 18 Tags 17 MiB
Go to file
songbaisen 912a4cb25e Enable mutable config in Tricircle 
1. What is the problem?

   The oslo.config support a 'mutable' parameter to Opts.
   This is only respected when the new method mutate_config_files
   is called instead of reload_config_files.so we need to enable
   mutable config in tricircle.

2. What is the solution to the problem?

   Depend on the two path in oslo.config which are
   Icec3e664f3fe72614e373b2938e8dee53cf8bc5e and
   I1e7a69de169cc85f4c09954b2f46ce2da7106d90 made the Tricircle
   have the ability to mutable config.

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

   Further patches will be needed to make select config options be marked as
   mutable. This change enables support for oslo provided config options
   to be updated via SIGHUP such as log level.

   Signed-off-by: song baisen <songbaisen@szzt.com.cn>
   Co-Authored-By: tangzhuo <ztang@hnu.edu.cn>, zhiyuan_cai <luckyvega.g@gmail.com>

Change-Id: I7b42bfb75913190fa4bd0d892e72fec8f629d7a6
 		2018-03-28 08:43:47 +08:00
devstack Fix the smoke test error 2018-02-11 09:08:48 +08:00
doc/source Fix the misspelling of "octavia" 2017-12-20 16:14:44 +08: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 Enable mutable config in Tricircle 2018-03-28 08:43:47 +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 Change links in README to the newest addresses 2017-08-18 11:31:37 +08:00
index.rst [doc-migration] Reorganize the Tricircle doc/source folder 2017-07-26 19:47:05 +08:00
requirements.txt Updated from global requirements 2018-03-15 09:37:26 +00: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-15 09:37:26 +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 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.