yahoo-eng-team team mailing list archive

[Bernard Cafarelli <1918274@xxxxxxxxxxxxxxxxxx>]

** Changed in: neutron
       Status: Fix Committed => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1918274

Title:
  Driver VLAN do not create the VlanAllocation registers if
  "network_vlan_ranges" only specify the network

Status in neutron:
  Fix Released

Bug description:
  "network_vlan_ranges" allows to define a list of physical networks and
  VLAN ranges [1]. But is possible to just define the physical network
  without the VLAN ID ranges; in that case, the VLAN driver should take
  all valid VLAN IDs (from 1 to 4094).

  If no VLAN range is defined, when "VlanTypeDriver._sync_vlan_allocations" is called, the "ranges" variable is:
    ranges = {'physical_net': []}

  We have two options here:
  - Modify the sync method.
  - Change the parser to populate, in case of not passing any VLAN range, the whole list of possible VLAN IDs for this physnet (I think last option is better).

  [1]https://github.com/openstack/neutron/blob/ab78d29c68b3cfdc6732d2ed2bcec0677b1a34f3/neutron/conf/plugins/ml2/drivers/driver_type.py#L68-L76

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1918274/+subscriptions