Proxmox 2.1 interface changes require reboot?

[squeeb]

This feels very "Windows 95" esque.

Why is there a requirement to reboot your server if you make any changes to the network interfaces?

I've been moving the interfaces.new into the place of interfaces and ifup'ing the new or changed interface and it works fine.

Any reason why it's been done this way?

 

[tom]

some changes needs a reboot. some not. so to be 100 % sure, reboot.

as soon as you run in production, changes to the network config should not be done anymore, especially in a cluster setup.

 

[awesome]

as soon as you run in production, changes to the network config should not be done anymore, especially in a cluster setup.

If will I add new VLANs to proxmox, can it break my cluster configuration?

 

[e100]

If will I add new VLANs to proxmox, can it break my cluster configuration?

I have not had an issue adding bridges for vlans, but I suppose if I messed up and did something to break the network it might cause my machine to fall off the network and get fenced.

I do not think it works with containers but with KVM you do not need to create a bridge for each vlan just set the tag to your vlan id.

 

[awesome]

I have not had an issue adding bridges for vlans, but I suppose if I messed up and did something to break the network it might cause my machine to fall off the network and get fenced.

I do not think it works with containers but with KVM you do not need to create a bridge for each vlan just set the tag to your vlan id.

Ok, thanks for explanation.
I used mixed VM's - OpenVZ with KVM, therefore when I need new VLAN I create new vmbr interface.