vswitch config changes

[ednt]

Hi,

we want to use vswitch to separate customer VMs from others.
If we get a new customer, we have to add/change the network settings.

It looks, that we need to go to the console, copy the new file and make a manual ifup for the new interface.
And this on each proxmox of the cluster.
We can definately not reboot the server.

Is this really true?

We thought that it is possible with vswitch to do such things 'on the fly' and only via the web gui of proxmox.

Best regards.

 

[wolfgang]

Hi,

If you use the GUI you have to reboot. Also, with openvswitch.
On the shell, you can do network changes without a reboot.

 

[vshaulsk]

Would you be able to clarify the statement:
"On the shell, you can do network changes without a reboot "

Are you saying just make changes in "interfaces" file directly ?
How would I activate the changes without rebooting?

I have tried previously and have not been successful, but I am probably making a mistake somewhere.

 

[wolfgang]

There is no step by step guidance.
This dependence on what you are doing?

If we get a new customer, we have to add/change the network settings.

This can be everything. From BGP to simple VLAN bridge?

 

[ednt]

We want to add a VLAN bridge for each customer.

@vshaulsk
You have to make the changes in the interface file and then ifdown ifup the changed interface.

 

[wolfgang]

We want to add a VLAN bridge for each customer.

Why do you do not use the VLAN Tag on the vNIC in the Hardware configuration?

 

[ednt]

We want to use the VXLAN feature of Open vSwitch to allow a customer net over all his devices in the net.

 

[vshaulsk]

To clarify making changes within the interface file:
- I add another Vlan config or VXlan into the interface file.
- I run ifdown ifup on the Bond or two physical Nics ?

Doesn't the command take down the entire physical interface before bringing it back up? Does that not disrupt all other traffic moving through the physical interface ?

 

[wolfgang]

@ednt
VXLan is not supported in Proxmox VE jet.
I would recommend you to install ifupdown2 to support VXLan through the interfaces file.
Then you can manually edit the network interface file.
After the changes, you can call ifup and the new vmbr is available.

This case is not a problem because there exist no guest interfaces on this bridge.
The Problem with the guest interfaces is, you have to reattach after a destroy/restore a bridge.
This happens if you call ifdown ifup.
If You make the changes through the ip/brctl interface no reattachment is necessary.

 

[spirit]

some doc for vxlan && linux bridge: (with ifupdown2)

https://git.proxmox.com/?p=pve-docs.git;a=blob_plain;f=vxlan-and-evpn.adoc;hb=HEAD