Bug #3858
VNET as reservation is not compatible with VXLAN/802.1Q/OpenVswitch networks if vlan_id is not fixed
| Status: | Closed | Start date: | 06/30/2015 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jaime Melis | % Done: | 0% | |
| Category: | Drivers - Network | |||
| Target version: | Release 5.0 | |||
| Resolution: | fixed | Pull request: | ||
| Affected Versions: | OpenNebula 4.12 |
Description
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.
History
#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
Use PARENT_NETWORK_ID
#5
Updated by Jaime Melis over 5 years ago
- Status changed from New to Closed
- Assignee set to Jaime Melis
- Resolution set to fixed
Fixed