Views: 571
Open Virtual Switch was initially conceived in a university environment, with a flow-based model providing the development primitive, and a central controller determining what those flows actually looked like. The use of OVS as a virtual switch in the IaaS market (and to be specific, in the OpenStack IaaS market) came about because the resources who supported OVS and its enterprise equivalent understandably wanted to ensure that there was an open model for integrating their services into OpenStack.
….
Source: Battle of the Switches – Open Virtual Switch vs. Linux Bridge
After all, as Leonardo da Vinci said, “Simplicity is the ultimate sophistication.”
Open Virtual Switch was initially conceived in a university environment, with a flow-based model providing the development primitive, and a central controller determining what those flows actually looked like. The use of OVS as a virtual switch in the IaaS market (and to be specific, in the OpenStack IaaS market) came about because the resources who supported OVS and its enterprise equivalent understandably wanted to ensure that there was an open model for integrating their services into OpenStack.
Source: Battle of the Switches – Open Virtual Switch vs. Linux Bridge