Datacenter network bridges

[micush]

Hi,

Why are network bridges, both OVS and Linux, configured at the host level and not at the Datacenter level? To me, bridges should be configured at the Datacenter level so that the bridge definitions can be shared by all clustered hosts within the Datacenter.

I understand that physical NICs cannot be defined at the Datacenter level because they are host dependent. However, a bridge definition can be defined at the Datacenter level and shared by all hosts and physical NICs can be added to the global bridges locally at the host level.

To me this makes much more sense. Backups are Datacenter level items. Firewalling is both a Datacenter and host level item. Storage is a Datacenter level item. Network bridges should be as well.

Can somebody explain it to me why it is not defined this way in PVE? It's one of my biggest peeves of using this software for 8+ years now.

I am very grateful for this fantastic software. It has helped me tremendously throughout the years. However, it would certainly be advantageous to change network bridges to act in this way.

Regards,

micush

 

[spirit]

Hi,
I'm currently working on it, I hope it'll be ready for proxmox 6.0.

 

[micush]

That is fantastic news. Thanks you so much.

 

[guletz]

Why are network bridges, both OVS and Linux, configured at the host level and not at the Datacenter level? To me, bridges should be configured at the Datacenter level so that the bridge definitions can be shared by all clustered hosts within the Datacenter.

I understand that physical NICs cannot be defined at the Datacenter level because they are host dependent. However, a bridge definition can be defined at the Datacenter level and shared by all hosts and physical NICs can be added to the global bridges locally at the host level.

Hi,

Maybe another idea that I have write in the past . I will try again

Any resurce on hosts/datacenter could have some user devined labels (for ex. critical1). And I can set and attach such label on a network iface on enoX on nodeY and enoQ on node Z. Then we could be able to create a bridge with the same label at datacenter ... and with some magic code we can have this bridges on nodes Y and Z.

So at datacenter it will be nice to have some labels resurces: storage labels, virtual network interface labels, VM/CT labels, backup tasks labels and so on.

Now think for a moment: move vdisks with label critical1 from nodes with label core to nodes with labels reserves on storage with label temporary. Or make a pve-zsync for VM label core1 frome nodes with labels .... to ....

Then could be more, dscp has labels (numeric), a gateway ip is also a label, mpls use labels, any zfs property could be a label also.

Thx.