Page History

Nominee’s bio (and/or LinkedIn profile)

LinkedIn Profile

How long have been working in the ONOS community?

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.

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

As the author of Atomix - the Raft consensus protocol implementation underlying many of ONOS's stores - I've created or contributed to much of the code underlying ONOS's consistent stores, including mastership election, configuration, primitives, etc. Additionally, since joining ONF in 2017, I've focused largely on rearchitecting the distributed primitives framework to address instability and improve fault tolerance.

What are you actively working on in ONOS?

In addition to improving the overall stability of ONOS clusters, my primary focus in ONOS is currently on developing, implementing, and testing a protocol for online upgrades of ONOS controllers (ISSU). Additionally, I've been coordinating a long term effort to disaggregate the primitive framework from the ONOS core codebase to expose it to a broader audience. My ultimate goal is to help create a reputation of reliability and usability for distributed ONOS controllers.

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, as the author and/or maintainer of distributed algorithms used in ONOS, I can provide unique perspective on the strengths and limitations of various architectural decisions.

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

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, and while I have no specific changes to propose at this time, I will be an advocate for the types of practices that my experience has taught me will help strengthen ONOS's user base and community (e.g. tools, documentation, visibility).