Skip to end of metadata
Go to start of metadata
Nominee’s bio (and/or LinkedIn profile)
I've been working with the ONOS community off and on for about three years, first in collaborating with Madan Jampani on Copycat and Atomix - the consistent replication framework used in ONOS - and later as a full time employee of ONF since early 2017.
As the author of Atomix and maintainer of distributed stores in ONOS, I've created or contributed to much of the code underlying ONOS's consistent stores, including mastership election, configuration, primitives, etc. More recently, as part of the µONOS effort, I've designed and implemented next generation stores for the µONOS Config, Topology, and RAN subsystems. I also developed the integration testing and benchmarking framework used in µONOS.
What are you actively working on in ONOS?
My current focus is on developing next generation stores and infrastructure for µONOS. As a result of lessons learned in ONOS Classic, I've introduced new techniques for testing and monitoring in an effort to detect and fix distributed systems bugs early on in the development lifecycle.
Why do you feel you would be a good candidate for this position?
I feel I would be a good candidate for this position because my focus on distributed systems problems brings a unique perspective on architectural decisions.
I'm primarily interested in the technical direction of ONOS as we begin to disaggregate the code base and reorient the project towards a micro-services architecture. But having been involved in a variety of open source communities both large and small and as both a user and a contributor, I've seen communities succeed and fail in various ways, and so I've also developed some firm opinions on the management of open source projects as a result. Open source projects are only as strong as their respective communities. I will continue to be an advocate for the types of practices I believe will help strengthen ONOS's user base and community (e.g. tools, documentation, visibility).