It’s already 2015 and it feels like 2014 passed by too fast. With its two first releases in 2014, the year has been an important one for the OpenDaylight project. The helium release was a good step in the right direction and brought a tenfold improvement to the hydrogen release. The project focus also shifted from the API Driven Service abstraction to a set of Model-Driven Service Abstraction using a shared datastore. Here is a couple of OpenDaylight SDN Predictions on what is coming next for the OpenDaylight project.
#1 – Clustering
Initial work on clustering happened in the Helium release where the Akka Framework was leveraged to provide a clustered version of the Datastore. The current work is about providing easier configuration and default clustering behavior within OpenDaylight as well as hardening the previous implementation. Applications will have to be adapted to take advantage of this cluster in order to coordinate migration or connectivity in a variety of use cases.
#2 – Modularization
In helium we broke the controller in features, this was hard to follow and use for humans. OpenDaylight will be fixing this and make the components even more consumable. The components will finally allow for proper OpenDaylight modularity. We will then see a variety of use case specific mix & match for all the components. OpenDaylight is not a controller but really a platform to address a variety of SDN use-cases.
#3 – Communities
We dropped the ball in 2014 with the OpenStack integration. In 2015 a lot of work will likely go at having OpenDaylight work with other communities such as OpenNFV , OpenStack and even CloudStack. Moreover, OpenDaylight will be working more closely with organizations such as the Open Networking Foundation to implement a variety of emerging standards.
#4 – Application & Intents
#5 – Full Stack
OpenDaylight was initially scoped as a controller and applications layers. However with Intel recently joining in Q4 2014, the new DPDK vswitch proposal shows that OpenDaylight will see tackle the rest of the SDN stack including vSwitch and Network Operating System.
What I am the most excited about for 2015 is the fact that OpenDaylight is now started to be used in real use-case deployments. As it is still heavily a work in progress, I have seen only specific well-tested use-case based deployments and not a generic “download and use” scenario. We will get there but as any large community project it is difficult to get a coherent final solution if innovation is allowed everywhere. As such more is left to users, should you have inquiries about adopting OpenDaylight in 2015 don’t hesitate to get in touch.
Happy 2015 to all of you!