Nominee’s bio and/or LinkedIn profile

How long have been working in the ONOS community?

I have been working with ONOS since Summer of 2013.

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

Before the initial public release, I was working with Madan to add distributed version of various ~Store implementations and required modification to each subsystems. (e.g., Device, Link, FlowRule, etc.)
After that I was working on a project to integrate ONOS with ODENOS, something like a multi-domain hierarchical network orchestrator.
During the process I have incubated mechanics to provide abstract view to higher-level control using gRPC, etc.
Recently I’ve been working as part of Packet-Optical team, exploring ways to configure Device to realize linear protection.

What are you actively working on in ONOS?

Currently working in area related to packet optical use case to support deployment in transport network.

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

I have been involved since the early days of ONOS, so I believe I have good understanding of it's design philosophy.
Also, I think it'll be good to have diversity in active TST members.

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

There are few areas, where ONOS needs to improve to support network operation, one of them is device configuration as part of service provisioning,
another is enhancement of information model to express dependency between Intents and network resource it has created.
I would like to explore bringing improvements in one of those areas.