I have not yet seen any real openflow switch hardware, and I guess there is a single ovs daemon running side, right? If so, just curious why the ovs daemon is designed to create and manager a group of bridges (each bridge can represent an Ethernet switch), rather than a single Ethernet switch? Can someone pls advise or correct me if I am wrong?
It looks that emulation testbed like mininet is running a single ovs daemon in the hypervisor and create/manage a group of Ethernet switches in the hypervisor. A follow-up question would be if in the real hardware one ovs manages one ethernet switch, would it be more realistic for the emulation testbed to model every Ethernet switch in a VM and run an ovs daemon inside the VM? kevin
_______________________________________________ discuss mailing list [email protected] http://openvswitch.org/mailman/listinfo/discuss
