The policy-and-docs-in-code Queens goal outlines the work required
for projects to move policy into code and document the operations
and defaults.
This commit replaces occurrences of RuleDefault with
DocumentedRuleDefault where appropriate, which requires additional
attributes when used that supply more documentation in rendered
policy files.
Using DocumentedRuleDefault produces more descriptive generated
policy descriptons in 'configuration' section of tricircle docs.
Change-Id: I5be169e996066ff66d165731cf2bf12aaff38fd4
1. What is the problem?
When writing the manual installation guide, I find that configuration
file generator fails to execute because there is an module import error
in opts.py for local and central plugin configuration. Actually there's
no need to generate configuration sample for plugin since the original
Neutron configuration file will be used, this is left without clearing
during the Tricircle splitting.
2. What is the solution to the problem?
Remove the entry for generating plugin configuration sample in tox.ini.
Also, tox.ini is modified to only install neutron dependency for py27
test, which will speed up pep8, docs and genconfig processes.
3. What the features need to be implemented to the Tricircle to realize
the solution?
No new features
Change-Id: Ie1463a91e7f252943f74f54f80f85e6f10acefd0
1. What is the problem?
Nova API-GW and Cinder API-GW code are still in the repository of
the Tricircle project.
2. What is the solution to the problem?
According to the blueprint for the Tricircle splitting:
https://blueprints.launchpad.net/tricircle/+spec/make-tricircle-dedicated-for-networking-automation-across-neutron
Nova API-GW and Cinder API-GW related code should be removed from
the repository of the Tricircle project.
3. What the features need to be implemented to the Tricircle to realize
the solution?
No new features.
Change-Id: I152bab9c0a7a114f0361a69a3ab2d7037731434f
1. What is the problem
In the current implementation of the Tricircle plugin for neutron,
network type is not supported so users cannot create networks
with network type specified. In the specification of cross-pod
l2 networking feature[1], we decide to support several network
types like local, shared VLAN, shared VxLAN, etc, the first step
is to make the Tricircle plugin be aware of network type.
2. What is the solution to the problem
Handle network type in the Tricircle plugin for neutron.
3. What the features need to be implemented to the Tricircle
to realize the solution
In this patch, we add a framework to load type driver which
processes different network type. The framework is based on
neutron ML2 implemenation, we inherit the ML2 type manager and
create a new Tricircle type manager. Also the Tricircle plugin
is modified to extract network type parameter from request and
insert network type information to response.
[1] https://github.com/openstack/tricircle/blob/master/specs/cross-pod-l2-networking.rst
Change-Id: Ida9b88df6113db46e637a7841ce5c1adaf651eba
The statless design was developed in the experiment branch, the experiment
shows advantage in removing the status synchronization, uuid mapping
compared to the stateful design, and also fully reduce the coupling with
OpenStack services like Nova, Cinder. The overhead query latency for
resources also acceptable. It's time to move the statless design to the
master branch
BP: https://blueprints.launchpad.net/tricircle/+spec/implement-stateless
Change-Id: I51bbb60dc07da5b2e79f25e02209aa2eb72711ac
Signed-off-by: Chaoyi Huang <joehuang@huawei.com>
Implement site create RPC. Now tricircle api can utilize RPC
to notify cascade service to start rpc server for new site.
Partially implements: blueprint implement-api
Ref: https://blueprints.launchpad.net/tricircle/+spec/implement-api
Change-Id: I73879a84d31b5ac9004cfe3f18cb9a984d53099c
Implement site create API. This patch only covers database model
creation and aggregate creation.
Partially implements: blueprint implement-api
Change-Id: I299f367900b7b15ea992fe6f0eaf614f83a1a70e
Implement client wrapper in DAL to access resources in top
OpenStack layer.
Partially implements: blueprint implement-dal
Change-Id: I8b6f5efdb49c87b6aeb4b7aad38f54c842c21d40
This is the base implementation. It adds all the devstack boilerplate
and connects to the network plugins' requests.
Change-Id: Ibd61153e755e1c218503b0671c242ff50b5ebdc8
Hieu LE
zhiyuan_cai
joehuang
Saggi Mizrahi