VNET as reservation is not compatible with VXLAN/802.1Q/OpenVswitch networks if vlan_id is not fixed
|Assignee:||Jaime Melis||% Done:|
|Category:||Drivers - Network|
|Target version:||Release 5.0|
|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.
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.