| Thread Previous • Date Previous • Date Next • Thread Next |
Public bug reported:
Currently when restarting neutron, neutron do following setup
a) set controller 127.0.0.1
b) set out-of-band mode
between a) and b), ovs runs with in-band mode and it has hidden flow in
bridge. The hidden flow causing odd dataplane flow.
To avoid that potensial odd dataplane flow we should do one of below:
a) configure the controller and set it to out-of-band in a single db transaction, i.e. "ovs-vsctl set-controller br-tenant tcp:127.0.0.1:6633 -- set controller br-tenant connection-mode=out-of-band" or
b) configure disable-in-band to true for the bridge before configuring the controller, i.e. “ovs-vsctl set bridge br-tenant other-config:disable-in-band=true”
** Affects: neutron
Importance: Medium
Assignee: Slawek Kaplonski (slaweq)
Status: Confirmed
** Tags: ovs
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1992953
Title:
Disable in-band flow management in the ovs bridges
Status in neutron:
Confirmed
Bug description:
Currently when restarting neutron, neutron do following setup
a) set controller 127.0.0.1
b) set out-of-band mode
between a) and b), ovs runs with in-band mode and it has hidden flow
in bridge. The hidden flow causing odd dataplane flow.
To avoid that potensial odd dataplane flow we should do one of below:
a) configure the controller and set it to out-of-band in a single db transaction, i.e. "ovs-vsctl set-controller br-tenant tcp:127.0.0.1:6633 -- set controller br-tenant connection-mode=out-of-band" or
b) configure disable-in-band to true for the bridge before configuring the controller, i.e. “ovs-vsctl set bridge br-tenant other-config:disable-in-band=true”
To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1992953/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
