Built on Micro-Services.
vne.io’s SDN controller is built on loosely coupled components like Redis, Clojure Eco System for API, Graphite and Graphana. Our main controller component is built on Intel DPDK and automated protocol encoders and decoders. We use Redis DB features to connect diverse technologies to work in a cohesive and well integrated environment. This also opens the door for customization where developers can plug in their custom graphing and data collection eco system in to the controller’s output.
We wanted our controller to scale to large number of end points (both white box switches and vSwitches). We leveraged the Intel DPDK technology to handle large number of concurrent TCP sessions and also to handle very high number of messages per session. In our preliminary testing, we could easily get 20K messages/sec handling capacity per CPU thread.
CM automation with NERD API and how to get started.
Our SDN controller has support for NERD Client and API. NERD is our custom API that is a combination of Netconf. and Redfish protocols. We have complete support for Netconf. concepts like Running Configuration and Candidate Configurations. At anytime, there is only one Running Configuration and multiple Candidate Configurations. Users can clone an existing configuration, modify it and activate the configuration as a transaction. As of now our controller supports Openflow1.3, LLDP and STP protocols. We plan to support OVSDB, Openstack ML2 pluggin, BGP-LS with PCEP in future iterations.
To get started, please visit our github page and see the above video for the quick demo on our SDN controller. We plan to provide complete support and many other features on our controller, please stay tuned to this blog or follow our Linkedin page.