> Here some notes about /etc/network/interface management with their provide > script: > > if we defined this kind of openswitch with bond0 or port: > > allow-ovs br0 > iface br0 inet manual > ovs_type OVSBridge > ovs_ports eth0 > > > we need to defined eth0 like this > > allow-br0 eth0 > iface eth0 inet manual > ovs_bridge br0 > ovs_type OVSPort > > > But if we do this, we can't defined the eth0 in the classic way. > So I think it's strange.. > > could be better to be able to do > > allow-ovs br0 > iface br0 inet manual > ovs_type OVSBridge > # ovs_ports eth0 > bridge_ports eth0
I don't think this is a problem (no need to change). We can simply extend our API with the ability to create/parse both types of bridges. > Another important thing: > > openvswitch keep the configuration in /var/lib/openvswitch/conf.db (json > database). > > But if we remove/change configuration in /etc/network/interfaces, on reboot it > doesn't change the conf.db. > So, maybe it's better to delete the conf.db on reboot, and recreate it from > /etc/network/interfaces on start. yes, sounds resonable. _______________________________________________ pve-devel mailing list [email protected] http://pve.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
