Permit to modify network informations
|Assignee:||Ruben S. Montero||% Done:|
|Category:||Core & System|
|Target version:||Release 4.6|
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_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.
feature #2465: virtualnetwork can update VLAN, VLAN_ID, BRIDGE and PHYDEV configuration attributes
#1 Updated by Ruben S. Montero over 6 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.
#5 Updated by EOLE Team about 6 years ago
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_END could be in use without a VM reboot and a new context generation.