D.S

galsagie.github.io

OVN and Distributed Controller · GalSagie

OVN and Distributed Controller · GalSagie My blog about everything related to SDN, NFV, Virtualization and Cloud Home About Site Archives Post Categories Content Tags © 2016. All rights reserved. GalSagie A blog about network virtualization and cloud OVN and Distributed Controller 16 Jan 2015 If you havent heard about it until now, make sure to read the following blog post: OVN, Bringing Native Virtual Networking to OVS. And the more detailed architecture design of OVN in OVS offical documentation. The more relevant and interesting phrase, in my opinion, from that entire blog is this: “Open vSwitch is the most popular choice of virtual switch in OpenStack deployments. To make OVS more effective in these environments, we believe the logical next step is to augment the low-level switching capabilities with a lightweight control plane that provides native support for common virtual networking abstractions.” I have seen a lot of posts regarding this, and it certainly a very interesting project to look for, but i want to tackle this from few interesting views: Policy Reading this architecture reminded me a lot of something else, it reminded me the way Cisco OpFlex is communicated between the controller and the agent running on the end nodes. Similar or not, in my view SDN implementors are starting to realize that we tried to abstract the control from the data plane using only protocols, and maybe thats just not enough. By having an agent / controller / lightweight controller / you name it running on the infrastructure at every end point (hypervisors and physical devices) we can concentrate on two things: Building a common policy language/protocol/API between all IT teams, which is application aware and can be distributed to all the network infrastructure nodes. Without having to worry how every infrastructure piece is going to implement it (Few interesting projects in that area are OpFlex and Congress) Building protocols/standards (many) for locally applying the above policy to software/hardware (For example OpenFlow) Without getting into right or wrong debate, i believe this delegation approach simplifiy things and help the community continue to develop the two aspects seperated from each other. Having a “control” entity in the end nodes can show value in other areas (hint: OAM, wait for my next post to read more about smart agents). There are some solutions already fully distributed, running on the end nodes, Midokura MidoNet is one of them. Virtual Network Function Distribution The trend of NFV is already here, virtual appliances for network functions are already deployed and used in the data center, especially for east-west traffic. The way they are used today is usually as a VM / dedicated node that is used as a logical gateway edge appliance where all traffic goes through. This approach proves to cause bottlenecks and we are seeing more and more solutions that try to distribute these network functions to the infrastructure end nodes (more specifically the hypervisors). Example projects are OpenStack DVR, and NSX micro segmentation approach (distributed firewall). In my opinion this new approach will be used more and more, having a control entity in the hosts can certainly help manage these functions. Context This relates to the last subject but i feel is important enough to stand on its own. The hypervisor is the only place where application meets the network, we can not extract this value or correlation context anywhere else in the network. physical devices usually try to apply sophisticated (performance expensive) DPI methods to extract this context. There are many use cases where a smart control entity (sitting in the hypervisor) can use this information to make better decisions. Tags: NFV · OVN · OVS · SDN ← Previous Post: MSS Clamping As A Tale Of Network Visibility Next Post: NFV Acceleration (Part 1) → Be social and share this post! Related Posts Kuryr and Neutron Existing Resources 15 May 2016 Neutron DB Consistency 14 Feb 2016 Kuryr Support for Docker Pluggable IPAM 30 Dec 2015 Please enable JavaScript to view the comments powered by Disqus.