1. What is the problem? In tricircle, some files use oslo_log, while others use logging. The oslo.log(logging) configuration library provides standardized configuration for all openstack projects. I think different files in tricircle should use a same logging module and it's better to use oslo_log. 2. What is the solution to the problem? Replace logging module with oslo_log. 3. What the features need to be implemented to the Tricircle to realize the solution? No new features Change-Id: Ib3221f763dbe410b4252e5188d13a5824813846e
|5 years ago|
|cmd||5 years ago|
|devstack||5 years ago|
|doc/source||5 years ago|
|etc||5 years ago|
|releasenotes||5 years ago|
|specs||5 years ago|
|tricircle||5 years ago|
|.coveragerc||5 years ago|
|.gitignore||6 years ago|
|.gitreview||6 years ago|
|.testr.conf||5 years ago|
|CONTRIBUTING.rst||5 years ago|
|HACKING.rst||5 years ago|
|LICENSE||7 years ago|
|README.rst||5 years ago|
|requirements.txt||5 years ago|
|setup.cfg||5 years ago|
|setup.py||5 years ago|
|test-requirements.txt||5 years ago|
|tox.ini||5 years ago|
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.
- Free software: Apache license
- Design documentation: Tricircle Design Blueprint
- Wiki: https://wiki.openstack.org/wiki/tricircle
- Installation guide: https://github.com/openstack/tricircle/blob/master/doc/source
- Tricircle Admin API documentation: https://github.com/openstack/tricircle/blob/master/doc/source/api_v1.rst
- Source: https://github.com/openstack/tricircle
- Bugs: http://bugs.launchpad.net/tricircle
- Blueprints: https://launchpad.net/tricircle
- Release notes: https://github.com/openstack/tricircle/tree/master/releasenotes/notes