ADVA Optical Networking will host a joint demo with BT at Mobile World Congress that showcases end-to-end, multi-layer transport network slicing and assurance. We’re particularly delighted to see this illustration of how edge computing and network slicing techniques can enable emerging 5G applications as it is in part made possible by our technology. With the growing anticipation of 5G connectivity, there is a critical need to develop a new transport networking technology that can meet the cost, efficiency and flexibility requirements. This demo marks just the first step in a long-term research collaboration between ourselves, ADVA, BT and other partners in this emerging space.
If you’re attending Mobile World Congress and would like to see a network architecture optimized for a new generation of applications that will enable enhanced mobile broadband, self-driving cars and massive IoT, stop by Hall 7 Stand 7H31 or Stand 7020MR.
“5G is set to enable use cases that go way beyond mobile broadband. By showcasing transport network slicing within an SDN-controlled infrastructure, we’re paving the way for 5G to support different use cases on a common infrastructure that could enable anything from self-driving cars to the massive machine-type communication (mMTC) needed for billions of IoT devices.
“Our demo shows that true end-to-end network slicing is ready for deployment. That means multiple network allocations using the same physical infrastructure can be delivered in parallel, not only in the radio access network (RAN) and mobile core network but also across transport and infrastructure resources. This technology will be vital for generating the flexibility and agility needed to bring incredible 5G applications to life,” said Anthony Magee, director, business development, ADVA.
Maria Cuevas, head, mobile core network research, BT, said, “By showcasing an architecture for wholesale services that can be efficiently reconfigured across all network layers through SDN control, we’re taking a big step forward. But this demonstration is really just the start of an intense period of research into network slicing. Our close collaboration with ADVA and other partners in this space will help us optimize our network for 5G and harness the technology’s potential to shape the future.”
Lumina CEO Andrew Coward, and COO Nitin Serro.
With an impressive turnout, presentations by experts in their field and of course, pizza and beer, the event offered a highly informative networking opportunity for the Open Source Networking community and marked the first OSN User Group Bay Area Meetup.
We kicked off the afternoon in our conference room with the doors wide open to a beautiful, sunny California day and heard first from Lumina customer and industry leader, Verizon with a lively discussion led by Hwa-Jung Han, Director of Emerging Technology, Verizon on building a programmable network infrastructure using Open Source SDN technologies and Verizon’s exploration of a new SDN ecosystem.
Sunny skies in San Jose.
Our very own Anil Vishnoi, Principal Software Engineer provided an overview of new offerings the OpenDaylight community is working on in the current release of Oxygen and upcoming Fluorine release as well as projects that are expanding use cases that users can solve for by using OpenDaylight. We also discussed ONAP with Bin Hu, AT&T, and explored the architectural vision of orchestrating workloads for Multicloud.
We had an energetic presentation from Rajat Chopra, R&D, Redhat who led us through an introduction to networking for large-scale container orchestration systems like Kubernetes, including an overview of requirements, common pitfalls and new technologies on the horizon.
Raymond Paik, Linux Foundation.
Raymond Paik of Linux Foundation followed up that presentation with a brief update on a new tool in the works from OPNFV Lab-as-a-Service and got us all excited about next month’s Open Networking Summit.
As presentations came to a close, we concluded the afternoon’s meetup with more mingling, live music and refreshments. A big thanks to all those who presented and attended; we look forward to see you all at the next one!
Lumina Networks is proud to announce its Founding Gold-level membership for the Linux Foundation’s new networking fund. This is a major consolidation of LF’s networking projects into a larger umbrella networking group. While it won’t change the individual projects for OpenDaylight, ONAP, OPNFV and others, it will definitely raise the stature of networking as one of the Linux Foundation’s primary areas of focus.
As a key contributor and leader of OpenDaylight, I’d like to comment from Lumina Network’s experience on how open source is playing a role in the generational change we are seeing in networking.
Open Source is Fast
Open Source is the quickest way to take ideas from concept to testing. In the past, ideas would be argued within the IETF or ETSI, sometimes for years, before vendors would create a compliant derivative. In the Open Source world, the whole approach is to write code first to prove concepts and try things that others can build upon. Bottom line, if you build your PoCs and ultimately production systems on Open Source platforms, you’re going to be moving quicker.
Open Source Changes the Balance of Power
Second, Open Source is a mechanism you can use to influence your vendors. If the vendor is supporting a platform, you should insist that platform be based on or compliant with the Open Source platform. If your vendor creates applications that run on a platform, you can insist that the application run on the Open Source platform and be portable to different distributions. This clarifies the work needed by the vendor and reduces the need for behemoth RFI/RFP documents to specify platform functions.
Open Source Attracts Innovation
Third and perhaps most important, Open Source will beckon a new class of innovators and technologists within your organization. Let’s face it, most of the “movers and shakers” in the industry are now involved in Open Source projects. When an Open Source community thrives, there’s no better way for the thought leaders in your organization to contribute their ideas at an industry-level and sharpen their skills as technologists.
All of these benefits- faster development cycles, increased influence on the vendor community and advancing the technology skills of your organization are essential in order to compete in the new software-defined world. Think of Open Source first, it’s one of the best ways to get to where you are going quickly.
During our recent webinar hosted by SDxCentral on SD-Core, we took a survey of interest on SD-Core and polled the audience on some of their preferences in where SD-Core will be applied. What is the definition of SD-Core? SD-Core is the term for the set of use cases that involve the evolution of core network technologies, such as MPLS, toward software defined networking. SD-Core is very different from SD-WAN, in that it pertains to the architecture of the service provider’s internal core network.
The term SD-Core is being coined because we at Lumina Networks are seeing the service providers looking to rapidly evolve their core networks and we are involved in several initiatives at major service providers globally. These initiatives involve both PoCs and deployments of various stages. Developments such as SD-WAN, 5G and others are putting pressure on the core networks not just in terms of traffic load, but also in terms of the need for service agility. Most of the market research I’ve seen says that carriers as a group are spending between 3 and 5 Billion dollars (US) per year on core network enhancements.
Our webinar attendees were admittedly parties interested in the SD-Core in the first place, but it’s still interesting to look at the poll results between the various options.
When asked, “if you are planning to evolve your MPLS core-based services, what underlying technologies are you considering?”, the audience was conservative.
The clear winner was adding central control to the existing network. I would interpret that to mean a desire for improved service agility and automation for the existing infrastructure. This also reflects our business at Lumina Networks as much of our NetDev activity centers on adding SDN control capabilities to already-installed switches and routers. Running in close second were the set of protocols that would involve changes to the underlying infrastructure including the desire for whiteboxes, OpenFlow or the very latest technology, P4.
So, for the next question, “what services are you looking to evolve to an SDN-based core network?” The results are not a surprise.
At a glance, this data likely reflects the service that network engineers administer today.
At Lumina Networks, we believe that core networking is ripe for a disruption. Emerging data plane technologies along with advances in open-source-based orchestration and control software are too compelling for service providers to keep doing things the old way. The question will be in how service providers transition their networks to the new technologies while maintaining their core network services. We’ll have more on hybrid core networking in a future Blog. Stay tuned to Lumina Networks!
By Allan Clarke and Anil Vishnoi
Getting started as an upstream contributor to OpenDaylight is not easy. The controller ecosystem is big, there are many projects, and there are millions of lines of code. What is a new ODL developer to do? Here is some pragmatic advice on where to begin to become an active contributor.
One of the easiest ways to get to know a code base is to start fixing bugs. Peruse the ODL bugs list on Bugzilla, say with the NETCONF project. You want to find bugs that aren’t likely being worked on and are of limited scope (to match your limited understanding of the project). Ideally bugs will have an owner assigned to indicate that they are actively being worked on, but it is not always a great indicator. In particular, someone may run across a bug, file a report, then jump into fixing it—and forget to assign it to themselves. This is most likely with the project contributors, so figure out who are the project contributors and look at the date of the report. If it was a project contributor and a newish date, then that bug might be being worked on. You should read through the report and try to decide how much domain knowledge is needed—as a newbie, smaller is better.
Once you have selected a bug to work on, click on the “take” link. Also add a comment to the bug. If someone already is working on it, they should get a notice and respond. You can also try the ODL mailing lists and give notice there. You mainly want to avoid duplicate work, of course.
Reviewing patches is a great way to contribute. You can access patches via Gerrit, and we’ll use the NETCONF patches as an example. Doing code reviews is a great way to not only see existing code but also to interact with other developers.
- If you have some domain expertise and know the code, you can review the functionality that is being pushed.
- If you have neither of these, you can do the review based on Java best practices and good software engineering practice.
Address Technical Debt
ODL uses Sonar for analytics of the upstream project. Here is an example for the NETCONF issues. Note that the ODL project has coding conventions, and the Sonar Qube has some best practices. This list shows violations that should be addressed. As a newbie, you can work on these with little domain knowledge required. You can also see that the code coverage varies for the NETCONF coverage, so adding NETCONF unit tests to boost the coverage in the weakest areas would be very helpful.
Sonar has a lot of interesting metrics. You can explore some of them starting here including coverage, tech debt, etc. If you look at the Sonar dashboard, it will point out a lot of available work that does not require a large span of time to invest. Doing some of this work is a great step towards getting your first patch submitted.
Follow Best Practices
With well over a million lines of code and many contributors from many companies, the ODL project has quite a girth. To manage the code entropy, ODL has some best practices that you should become familiar with. These cover a diverse set of topics, including coding practices, debugging, project setup and workflow. We strongly recommend that you carefully read these. They will save you a lot of time and will pay back your investment quickly. They will help you skate through code reviews. These practices are really time-tested advice from all the ODL developers, so don’t ignore them.
Attribution is an important insight into most if not all open source projects. Attribution allows stakeholders to see who is contributing what, from the individual up through sponsoring companies. It allows both a historical and current view of the project. You can see an example of why attribution is illuminating here. You need to sign up for an ODL account, and a part of that process will be to associate yourself with a company (if applicable). You can also see breakdowns by authors on the ODL Spectrometer.
That’s all for now. Happy trails, newbie.
Watch for Allan’s blog next week where he will share his Top 10 learnings as a new developer contributing to ODL.