quantum agent using a namespace does not work with nec plugin
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Fix Released
|
Medium
|
Akihiro Motoki |
Bug Description
DHCP agent with namespace does work with NEC OpenFlow plugin.
NEC plugin uses an Open vSwitch as an OpenFlow switch and the bug is basically from OVS behavior in OpenFlow mode.
1) The current OVSInterfaceDriver creates an port with type=internal using ovs-vsctl add-port. At this timing the port is UP.
2) Next the created is moved to the dhcp-agent namespace. Then the port status becomes DOWN.
$ sudo ovs-ofctl show br-int
OFPT_FEATURES_REPLY (xid=0x1): ver:0x1, dpid:000072a1d4
n_tables:255, n_buffers:256
features: capabilities:0xc7, actions:0xfff
1(tap7d6fba03-f9): addr:f0:
config: PORT_DOWN
state: LINK_DOWN
LOCAL(br-int): addr:72:
config: PORT_DOWN
state: LINK_DOWN
OFPT_GET_
This happens since the created port disappears from the default namespace.
OVS vswitchd log /var/log/
Usual OpenFlow controllers respect the OpenFlow port status. Since DHCP server (dnsmasq) is connected to the down port, DHCP server disappears from the virtual network.
This behavior can be avoided if we use a similar approach used in BridgeInterface
summary: |
- NEC plugin does work with namespaces + quantum agent using a namespace does not work with nec plugin |
Changed in quantum: | |
milestone: | none → folsom-rc1 |
importance: | Undecided → Medium |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Changed in quantum: | |
milestone: | folsom-rc1 → 2012.2 |
Changed in quantum: | |
status: | Fix Committed → Fix Released |
Fix proposed to branch: master /review. openstack. org/12714
Review: https:/