Feature #2465
Permit to modify network informations
| Status: | Closed | Start date: | 11/15/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Ruben S. Montero | % Done: | 0% | |
| Category: | Core & System | |||
| Target version: | Release 4.6 | |||
| Resolution: | fixed | Pull request: |
Description
Hello,
On an ONE 4.2, I created several virtual OpenvSwitch networks, like for example:
oneadmin@nebula:~$ onevnet show 3 VIRTUAL NETWORK 3 INFORMATION ID : 3 NAME : admin USER : oneadmin GROUP : oneadmin CLUSTER : nebula TYPE : RANGED BRIDGE : ovsbr0 VLAN : Yes VLAN ID : 30 USED LEASES : 0 PERMISSIONS OWNER : um- GROUP : u-- OTHER : --- VIRTUAL NETWORK TEMPLATE NETWORK_ADDRESS="10.0.3.0" NETWORK_MASK="255.255.255.0" RANGE IP_START : 10.0.3.1 IP_END : 10.0.3.254 VIRTUAL MACHINES
I would like to change some of the attributes:
- VLAN_ID to integrate with physical switches VLANs numbering policy
- BRIDGE as I configured a new OpenvSwitch bridge to integrate with physical switches
- IP_START, IP_END as I entered theses numbers without care since we use DHCP, now I would like to make ONE and DHCP leases match
I could destroy and re-created the virtual network but I'll need to modify all templates to use the new number, the in-place editing will prevent this.
I tested with one of theses networks updating directly the database, but it's quite cumbersome and error prone.
Regards.
Associated revisions
feature #2465: virtualnetwork can update VLAN, VLAN_ID, BRIDGE and PHYDEV configuration attributes
feature #2465: Fix parsing of empty strings.
feature #2465: Migrator copies vnet config attr to the template
feature #2465: Compile new parsers
History
#1
Updated by Ruben S. Montero over 7 years ago
Yes this is an interesting feature by itself. Moving this to feature to be evaluated for 4.6.
Note that in 4.4 we are going to use reference by names. So in case you need it, you can recreate the network with the same name and the templates will use the name reference, so there'd be no need to change them.
#2
Updated by Ruben S. Montero over 7 years ago
- Tracker changed from Request to Feature
#3
Updated by Ruben S. Montero over 7 years ago
- Target version set to Release 4.6
#4
Updated by Ruben S. Montero over 7 years ago
- Status changed from Pending to New
#5
Updated by EOLE Team over 7 years ago
Hello,
I think some attributes could be applied without a restart of the VM:
- VLAN_ID: modify the VLAN tag of the OVS port
oneadmin@host: sudo ovs-vsctl set port <PORT NAME> tag=<VLAN_ID>
- BRIDGE: delete the interface from the old bridge and add it to the new
oneadmin@host: sudo ovs-vsctl del-port <OLD BRIDGE> <PORT NAME> oneadmin@host: sudo ovs-vsctl add-port <NEW BRIDGE> <PORT NAME> oneadmin@host: sudo ovs-vsctl set port <PORT NAME> tag=<VLAN_ID>
But I don't think the IP_START and IP_END could be in use without a VM reboot and a new context generation.
#6
Updated by Jaime Melis over 7 years ago
- Assignee set to Ruben S. Montero
#7
Updated by Ruben S. Montero over 7 years ago
- Status changed from New to Closed
- Resolution set to fixed
- BRIDGE
- PHYDEV
- VLAN
- VLAN_ID
Fixed networks can modified leases, so the only attributes left to be modified is the IP Range.