Hi there,
[resend again, as it didn't arrive on the list]
yesterday I gave the OpenvSwitch implementation for KVM some thoughts.
Especially the vlan stuff. I came across Dimitris NIC refactoring [1]
which introduces common functions for KVM and XEN networking using
tools/net-common.in for common functionality which is used by
tools/kvm-ifup.in and tools/vif-ganeti.in respectively.
I think this approach is very good, because it keeps networking as
hypervisor indepentend as it can. Now my implementation of vlan uses
vif-openvswitch which comes with XEN 4.3 and is not compatible with
vif-ganeti right now.
vif-openvswitch requires bridge=switch1.onevlan:anothervlan
whereas
vif-ganeti requires bridge=switch1 (which will crash when giving it
switch1.2:3:4 or something)
I would suggest to merge the functionality of vif-openvswitch into
vif-ganeti. This way users stay independent of whether they wanna use
vif-ganeti or vif-openvswitch.
What are your thoughts about that? Do you see any issues I may have
overseen?
Also, I would base my future implementations (QoS for example) on this
structure.
Cheers,
Sebastian
[1]
http://git.ganeti.org/?p=ganeti.git;a=commit;h=4855760b95eaff75c8f4340173f5bdc116cc2a40
