At the OpenDaylight Summit today, developers took to the keynote stage to discuss the success of the recent Lithium release and expectations for the upcoming Beryllium milestone.
Colin Dixon, Technical Steering Committee Chair (TSC) at the OpenDaylight Project and a Principal Engineer at Brocade, said that the thing he’s most proud of during the Lithium release cycle was that it landed on time, without too much pain. He commented that the maturity of the overall project has grown over the last two years, making a stable release cadence possible.
Dixon is also confident that OpenDaylight is now working on the right problems.
“Before I got involved in OpenDaylight, I was busy thinking about what are the really hard problems in SDN,” Dixon said. “Every one of the grand challenges that I wrote down before starting on OpenDaylight are things that OpenDaylight is now trying to tackle.”
Dixon’s grand challenges include application composition, distribution versus centralization, how to actually deploy SDN and how to deal with heterogeneous hardware and be able to expose services in a reasonable way.
“The hardest research problems in the world are problems that OpenDaylight is trying to grab,” Dixon said. “We don’t have solutions for them all, but at least we’re thinking about the right problems.”
Looking forward to the Beryllium release, Dixon said that the two big challenges that he wants to focus on are clustering and documentation. In terms of clustering, Dixon said there needs to be improvement in the APIs to help enable easier clustering.
On the documentation front, Dixon noted that, historically, open-source software hasn’t been very strong with documentation, but that’s something he’s hoping to improve in Beryllium.
“I have personally put a huge amount of time into documentation during the Lithium cycle,” Dixon said.
Dixon encouraged everyone in the OpenDaylight Summit keynote audience to help in the documentation effort, especially those that didn’t contribute code.
“Getting end-users and people that don’t have their noses in the code involved is the only way we’re going to make the documentation better,” Dixon said.
Sean Michael Kerner is a senior editor at Enterprise Networking Planet and InternetNews.com. Follow him on Twitter @TechJournalist.