yahoo-eng-team team mailing list archive

[Mark McClain <1196634@xxxxxxxxxxxxxxxxxx>]

** Changed in: neutron
       Status: In Progress => Won't Fix

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

Title:
  Unable to re-use VLANs for multiple Neutron Networks

Status in OpenStack Neutron (virtual network service):
  Won't Fix

Bug description:
  In some networks, the topology of the networks may require sharing
  different layer 3 domains across the same VLAN - perhaps in different
  availability zones.  However, the core neutron implementations today
  will throw an error if a VLAN segment is re-used with multiple Neutron
  Networks.  If it is attempted, the following error is thrown:

  Traceback (most recent call last):
    File "/usr/lib/python2.6/site-packages/quantum/api/v2/resource.py", line 82, in resource
      result = method(request=request, **args)
    File "/usr/lib/python2.6/site-packages/quantum/api/v2/base.py", line 406, in create
      obj = obj_creator(request.context, **kwargs)
    File "/usr/lib/python2.6/site-packages/quantum/plugins/openvswitch/ovs_quantum_plugin.py", line 466, in create_network
      segmentation_id)
    File "/usr/lib/python2.6/site-packages/quantum/plugins/openvswitch/ovs_db_v2.py", line 158, in reserve_specific_vlan
      physical_network=physical_network)

  
  The code causing this exception can be found here:
   - quantum/plugins/ml2/drivers/type_vlan.py - reserve_provider_segment
   - quantum/plugins/openvswitch/ovs_db_v2.py - reserve_specific_vlan
   - quantum/plugins/hyperv/db.py - reserve_specific_vlan
   - quantum/plugins/linuxbridge/db/l2network_db_v2.py - reserve_specific_network

  To enable this use case, a configuration switch could be added to
  enable re-use of the VLANs for specific reservation.  However,
  consistency must be maintained for when a VLAN is auto-generated for
  use (example - quantum/plugins/openvswitch/ovs_db_v2.py -
  reserve_vlan).  In that case, the flag would not be taken into account
  and would attempt to use an unused vlan still.

  Attached a unified diff which may be used as a basis to provide the
  function for this use case.

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