Backlog #3982

Support for openvswitch tagged only port

Added by Stefan Kooman almost 6 years ago. Updated over 5 years ago.

Status:PendingStart date:09/15/2015
Priority:HighDue date:
Assignee:-% Done:


Category:Drivers - Network
Target version:-


I have setup a "nested" hypervisor. The underlying hypervisor (L0) is managed by opennebula. In order to have network isoloation in the guest hypervisor (L1) I have set up a "trunk" port using the "VLAN_TAGGED_ID" attribute (VLAN_TAGG
ED_ID="226,227"). As the virtual network has a AR in it, it is seen as a "ACCESS PORT" as well as a "TRUNK" port. Resulting in the following configuration:

Port "vnet6"
tag: 226
trunks: [226, 227]
Interface "vnet6"

This configuration is treated as a "native vlan" by openvswitch. See discussion here: Currently there is no way to provide a "trunk" only port with OpenNebula. As a virtual network needs to have a AR to get a lease (and thus reducing the trunk port to a native vlan port for one of the defined vlans). How can we come by this problem in OpenNebula? Drop the requirement for a AR? Add a "TRUNK" option for a virtual network? A "pure" trunked interface is very useful in "nested" hypervisor situations.


#1 Updated by Stefan Kooman almost 6 years ago

Ruben S. Montero. commented on this before (in #2345):

Yes I'd say that an specific attribute would be the ideal. Probably we should open an issue for this in the backlog (
instead of reopening this)?

^^ hence I created this issue: 3982

#2 Updated by Ruben S. Montero almost 6 years ago

  • Tracker changed from Feature to Backlog
  • Category set to Drivers - Network
  • Target version set to Release 5.0


#3 Updated by Ruben S. Montero over 5 years ago

  • Priority changed from Normal to High
  • Target version deleted (Release 5.0)

Also available in: Atom PDF