tricircle/releasenotes/notes/combine-bridge-network-c137a03f067c49a7.yaml
zhiyuan_cai b60ba570bb Combine bridge networks
1. What is the problem?
The current implementation of bridge networks has some problems
when supporting DVR and shared VxLAN network. One blueprint has
been registered[1] and the specification document has also been
submitted[2].

2. What is the solution to the problem?
The logic of bridge network operations will be changed, here lists
some major changes:
(1) Only one bridge network will be created for one project
(2) Bridge network is attached to local router as external network
(3) One local router dedicated for north-south networking will be
    created in the pod hosting real external network. Bridge network
    is attached to this special router as internal network
(4) If the instance port is not located in the pod hosting real
    external network, after floating ip association, one "copy" port
    will be created in the pod hosting real external network. Without
    this port, local Neutron server will complain that it cannot find
    the internal port going to be associated.

3.What the features need to be implemented to the Tricircle
  to realize the solution?
Bring part of the DVR support to cross-pod layer-3 networking

[1] https://blueprints.launchpad.net/tricircle/+spec/combine-bridge-net
[2] https://review.openstack.org/#/c/396564/

Change-Id: I53d1736ab30d3bc508279532609285975988b5f4
2017-01-05 15:44:27 +08:00

5 lines
154 B
YAML

---
features:
- North-south bridge network and east-west bridge network are combined into
one to bring better DVR and shared VxLAN network support.