03 Aug 2015
If you have been following my posts, i have written few deep dive and high level posts regarding OVN.
OVN like similar other projects (Midonet, future Dragonflow) takes a different approach of implementing SDN control plane.
Instead of using logically centralized SDN controller, OVN has distributed local controllers which exists at each compute host in the setup.
These controllers all synchronize with each other using a distributed DB solution (OVSDB) which consist of data representing the cloud management system configuration (the logically desired state of the networks as configured by the tenants) and data inserted by the controllers themselves regarding their runtime state.
30 May 2015
I have written several posts about OVN, feel free to search them under the OVN category, in this post i will not cover the high level overview but rather a deep dive into the current L2 implementation and how it is expressed in Openflow flows in OVS.
11 May 2015
If you havent read part 1 of this deep dive introduction, make sure to read it here.
09 May 2015
In this post i am going to do a deep dive introduction to Dragonflow.
Dragonflow is an embedded L3 controller in Neutron that solves the network node bottleneck the SDN way, and overcomes some of the DVR limitations.
It is aligned as an Openstack Neutron L3 Plugin and provide DVR functionality without the use of namespaces or L3 agents in the compute nodes.
26 Apr 2015
In the previous OVN post i have written about OVN high level architecture, the northbound and southbound DB’s and their main motivations.
You can read this post here.
In this post i am going to describe the containers networking support in OVN and how this integrate with Openstack.