Nominee’s bio and/or LinkedIn profile

David's LinkedIn Profile

How long have been working in the ONOS community?

I have worked in and around the ONOS community for about 2 to 3 years. When I was first introduced to ONOS it was before ONOS had opened it source code to the public; which gave limited opportunity for Ciena to work directly with ONOS. While Ciena supported ONOS, at that time Ciena started to develop with OpenDaylight (ODL). About 1.5 to 2 years ago Ciena shifted its technology focus from ODL to ONOS. Since this shift, my focus has been helping to manage the hardening of ONOS in preparation for a Ciena production release as well as help with the development of the CORD solution.

What contributions have you made in the past to the ONOS community?

My past contributions to the ONOS community are more focused on architectural and directional input than high volumes of code. I did provide some of the original work, which has since been redone, for the Docker containerization of ONOS. I contribute to the community through providing help on the #slack channels and email list (as well as ask my share of questions). I have contributed to the community through public presentations at conferences and shows.

What are you actively working on in ONOS?

My current active contributions (code) are focused on the CORD solution. I am engaged in ONOS through the team I manage that works to harden ONOS as well as team members that work on the virtualization brigade. I take an active role in terms of setting direction and course correction for the hardening team. This team has done some very important work including discovery and resolution work on clustering issues and event ordering issues. This team is also working on performance evaluation and general stability of ONOS under long running, high stress scenarios.

Why do you feel you would be a good candidate for this position?

The short answer is that I have the outside perspective that is focused on producing a carrier class, production release. I bring the alternative perspective to a lot of architecture discussion, focusing on how to provide a quality core while providing the ability to independently develop solutions on top of ONOS.

Are there any changes you would like to bring to the community if elected into this position?

I think the ONOS community is a vibrant community with good participation. As such, I don't see any significant changes I would bring in terms of community organization or input. Where I see that I will have most impact is to continue to push for a disaggregated, micro service based controller where only a few core capabilities are in process and other services (intents, analysis, troubleshooting) are external to this core process. I see a continued push for a smaller, lighter core process and use of off the self components instead of home grown technologies. My focus is less on network research and more on delivering an SDN controller that can confidently be deployed in large customer production networks.