Bug #3858

VNET as reservation is not compatible with VXLAN/802.1Q/OpenVswitch networks if vlan_id is not fixed

Added by Rolandas Naujikas about 6 years ago. Updated over 5 years ago.

Status:ClosedStart date:06/30/2015
Priority:NormalDue date:
Assignee:Jaime Melis% Done:


Category:Drivers - Network
Target version:Release 5.0
Resolution:fixed Pull request:
Affected Versions:OpenNebula 4.12


If we create reservation from existing VNET as new VNET it's NETWORK_ID is different from parent NETWORK_ID.
In vlan.rb

options[:vlan_id] = CONF[:start_vlan] + options[:network_id].to_i

In VNET template (in XML) I can find PARENT_NETWORK_ID as real value for NETWORK_ID to be used for such calculation.

In result we see new VXLAN physical device created and network loop also, because they attached to the same BRIDGE.

Associated revisions

Revision 56c6df5a
Added by Jaime Melis over 5 years ago

Bug #3858: inherit vlan_ids in reservations

Revision a9f8dbd1
Added by Ruben S. Montero about 5 years ago

feature #3858, #4376: Remove vlan_id generation from drivers. Remove
VLAN=YES checks that were left behind...


#1 Updated by Ruben S. Montero about 6 years ago

  • Status changed from Pending to New
  • Target version set to Release 4.14

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

  • Category set to Drivers - Network

#3 Updated by Tino Vázquez almost 6 years ago

  • Target version changed from Release 4.14 to Release 5.0

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


#5 Updated by Jaime Melis over 5 years ago

  • Status changed from New to Closed
  • Assignee set to Jaime Melis
  • Resolution set to fixed


Also available in: Atom PDF