neutron

support vlan_min + vlan_max config opts in ovs plugin

Bug #1012223 reported by dan wendlandt
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
neutron
Invalid
Undecided
Yaguang Tang

Bug Description

currently OVS plugin in vlan-mode assumes all VLANs are available for allocation. The administrator should be able to specify a range (or even a set of ranges) for allocation.

dan wendlandt (danwent)
tags: added: low-hanging-fruit
dan wendlandt (danwent)
Changed in quantum:
status: New → Confirmed
Yaguang Tang (heut2008)
Changed in quantum:
assignee: nobody → Yaguang Tang (heut2008)
Revision history for this message
Yaguang Tang (heut2008) wrote :

should we also follow nova when create a network ,offer a optional params to specify the vlan the network belongs to?

Revision history for this message
Gary Kotton (garyk) wrote : Re: [Bug 1012223] Re: support vlan_min + vlan_max config opts in ovs plugin

Hi,
I think that this bug may be addressed in the "provider network"
blueprint. I suggest that you be in touch with Robert Kukura
<email address hidden> (he is currently working on this).
Thanks
Gary

On 06/13/2012 02:03 AM, Yaguang Tang wrote:
> should we also follow nova when create a network ,offer a optional
> params to specify the vlan the network belongs to?
>

Revision history for this message
Robert Kukura (rkukura) wrote :

Yes, I am currently implementing what you describe as part of https://blueprints.launchpad.net/quantum/+spec/provider-networks. I am adding configuration to the openvswitch plugin to specify the VLAN tag range from which networks are dynamically allocated, similar to the linuxbridge plugin. The "provider" extension will allow VLAN tags to be explicitly assigned during network creation, either inside or outside of that range. Additionally, the 2nd phase of this BP will add support for using multiple network devices, with separate VLAN tag spaces for each device.

I believe that this bug should be closed once the 1st phase of that BP is implemented.

-Bob

Revision history for this message
dan wendlandt (danwent) wrote :

Turns out this is a duplicate, as it will be handled as part of the BP Bob mentioned in comment #3 above.

Changed in quantum:
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.