Nominee’s bio

I have been at ONF since 2013, where I work primarily as a software developer and project lead, as well as a platform advocate, mentor, and software designer. I graduated from Stanford with a Bachelor's and Master's in Computer Science.

How long have been working in the ONOS community?

Since 2013, I have been an active contributor to the ONOS community as a developer, reviewer, and mentor. I have been a member of the ONOS TST since its inception in December 2014. I am also a core developer for the Mininet project and currently lead the Stratum project.

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

On the technical front, I’ve contributed to several areas of the project including core systems like intents; southbounds including OpenFlow and P4Runtime; the build system; test frameworks; development and release tools; and project infrastructure. From a community perspective, I’ve given several talks and tutorials on ONOS at conferences and events around the world. I’ve mentored dozens of community members on design and code development.

What are you actively working on in ONOS?

I am currently working device integrations (particularly ones that use P4Runtime and gNMI, e.g. Stratum switches) as well as improving the notion of data plane programmability in the ONOS core to support flexible pipelines (like those defined in P4).

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

I bring years of experience and a breadth of knowledge from my experience as a developer and TST member. I can offer a perspective on project proposals that accurately accesses their feasibility and value in the context of the ONOS project.

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

As the ONOS project continues to grow, code stability remains vital to keeping developers productive. I will advocate for us to focus on continuous testing and more frequent developer releases, as well as the disaggregation of the source code, test, and build systems to accommodate different modules’ maturity and ease the creation of distributions. Additionally, I will push for in-service upgrades, high performance programmatic APIs, and tools for runtime debugging.

  • No labels