Proxmox 2.0 network change reboots

[cloudguy]

Good day,

Are methods / plans available to alter Proxmox’s behavior in how committing network changes are committed and enabled from the web console.
Currently, a reboot is required to commit network changes. Understandably in an environment that has a lot of network changes, this would result in undesirable downtime. Since Proxmox effectively relies on the underlining OS for network configuration, restarting networking from the CLI seems to do the trick.

Questions:

1. Are there any plans of implementing the ability to commit and enable network changes without rebooting the host?
2. Are there any drawbacks from issuing a /etc/init.d/networking restart command from the CLI to immediately commit network changes made in /etc/network/interfaces? (assuming a multi-node proxmox cluster, shared SAN storage, and HA enabled VMs).

Thank you.

 

[mlanner]

Interested in the answer too ...

 

[dietmar]

Understandably in an environment that has a lot of network changes

What kind of environment is that - why do you need to change the network file?

 

[cloudguy]

What kind of environment is that - why do you need to change the network file?

We would be adding network bridges tagged on different VLANs. Our model would involve network isolation using VLANs (assume 1 VLAN = 1 customer). So as a new client is brought on board, we need to provision a new VLAN (bridge). Understandibly we could pre-populate some of these, however dynamic addition of networks / bridges would be highly desired. To manage all this, we are looking into extending proxmox via the exposed API.

 

[dietmar]

We would be adding network bridges tagged on different VLANs.

The plan is to make that work without modifying /etc/network/interfaces

 

[charnov]

Can I resurrect a request to look into integrating OpenvSwitch into the GUI? This would definitely put Proxmox ahead of everyone if it could be integrated and add the capability to manage networking across the entire cluster from one console.

 

[cloudguy]

Can I resurrect a request to look into integrating OpenvSwitch into the GUI? This would definitely put Proxmox ahead of everyone if it could be integrated and add the capability to manage networking across the entire cluster from one console.

What would the potential roadmap for something like OpenVswitch?

Is there a preferred method of committing network changes without reboots in the interim?

 

[e100]

I always just log into the server, edit /etc/network/interfaces, add my new vmbrX interface tagged to the vlan I want then do ifup vmbrX.

 

[Ninjix]

I second e100's method as how I solve the live network re-configuration. I would love see Open vSwitch plugged into Proxmox. I want to be able to provision isolated VLANs for our developer and QA teams. I'm willing to help if anyone is interested.

 

[charnov]

Open vSwitch has been merged into the Linux 3.3 kernel. http://kernelnewbies.org/Linux_3.3#head-d587af5a0e432c20cd96f2fe2b82adabba671df9 and https://lwn.net/Articles/469775/

 

[spirit]

Hi, Openvswitch is not compatible with Openvz, that's why it cannot be implemented in proxmox for the moment.


We are working to create dynamicaly vlan with linux bridge, code is implemented


I'm currently testing it with 100vlans, with and without bonding, seem to works fine


If you want to test,
please install the package (not yet release in proxmox repositories)


http://odisoweb1.odiso.net/qemu-server_2.0-28_amd64.deb


the,just add to your vm config, :


net0: ......., bridge=vmbr0,tag=XXX where XXX is vlanid.


You just need to have a bridge in your /etc/network/interfaces with a ethX or bondX in the bridge, without vlan tagging.


Then, if tag=XXX is specified in vm conf, ethX.vlanid or bondX.vlanid is dynamicly created and go to a new bridge.

(this package also ifup vmbrX, with or without vlan, so no more reboot need)

 

[udo]

Hi spirit,
cool news... will test soon.

Udo