yahoo-eng-team team mailing list archive
-
yahoo-eng-team team
-
Mailing list archive
-
Message #02453
[Bug 1177841] Re: network_vlan_ranges in ovs_quantum_plugin.ini is never used
** Changed in: quantum
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to quantum.
https://bugs.launchpad.net/bugs/1177841
Title:
network_vlan_ranges in ovs_quantum_plugin.ini is never used
Status in OpenStack Quantum (virtual network service):
Invalid
Bug description:
In quantum/plugins/openvswitch/agent/ovs_quantum_agent.py,
(stable/grizzly) lines 143 and 146 set lower and upper bounds for VLAN
ranges. Lines 167-169 then set those bounds as the
available_local_vlans:
167 self.available_local_vlans = set(
168 xrange(OVSQuantumAgent.MIN_VLAN_TAG,
169 OVSQuantumAgent.MAX_VLAN_TAG))
Then, if we jump forward to def provision_local_vlan (lines 291-310),
specifically 304:
304 lvid = self.available_local_vlans.pop()
we see that lvid is set to the first value on the stack, but this
value has never been read in from ovs_quantum_plugin.ini nor the
quantum DB, so it will always default to whatever the lower bound
(MIN_VLAN_TAG) is hardcoded to.
quantum-server looks to parse this properly, as it inserts the correct
tuples into the DB.
To manage notifications about this bug go to:
https://bugs.launchpad.net/quantum/+bug/1177841/+subscriptions