[irq]: techie interrupted07/10/2012
“ Each host machine runs the MidoNet agent (MN) which operates on a local copy of the virtual network configuration, and the agent acts upon that configuration when a packet is received on ingress from a vPort (the logical network interface that connects to a virtual machine, or a router for example). Think of the local MidoNet agent as the control plane CPU for the local vswitch on that host. Any special network control packets received on a vPort, such as ARP requests, will be handled and serviced locally by the MidoNet agent. No more ARP broadcasts bothering the network.
Similarly, L2-L4 forwarding lookups and packet processing (NAT, encap, etc.) is handled locally by the MidoNet agent based upon its local copy of the virtual network configuration. And as this happens the MidoNet agent builds the flow state on its local data plane (the Open vSwitch kernel module). The host vswitch data plane does not rely on some nebulous central controller for programming flows — the local agent handles that. This is one significant point of differentiation between Midokura MidoNet and Nicira (VMware).
MidoNet’s decentralized flow state architecture demonstrates that this solution was built for scalability and robustness. „
Similarly, L2-L4 forwarding lookups and packet processing (NAT, encap, etc.) is handled locally by the MidoNet agent based upon its local copy of the virtual network configuration. And as this happens the MidoNet agent builds the flow state on its local data plane (the Open vSwitch kernel module). The host vswitch data plane does not rely on some nebulous central controller for programming flows — the local agent handles that. This is one significant point of differentiation between Midokura MidoNet and Nicira (VMware).
MidoNet’s decentralized flow state architecture demonstrates that this solution was built for scalability and robustness. „
Mind blowing L2-L4 Network Virtualization by Midokura MidoNet
Quote posted at 00:11 Comments
blog comments powered by Disqus