Technical Steering Team

Ali Al-Shabibi

Have you served on the TST before? If so, for how long?

Yes, I have served on the TST from the very beginning.

Are you a module owner? If so, for how long and for what modules?

As a TST member, I can review and submit any part of the ONOS codebase.

How long have you been making software contributions to ONOS?

I was the first employee of ON.Lab and as such I have contributed to ONOS since it's inception. Furthermore, I was part of the early two member team (Thomas and I) who designed and implemented ONOS as we know it today.

What are your most important software contributions?

As southbound maintainer I am responsible for all southbound matters which involves helping other developers bring in new providers to ONOS. In particular, I have designed and built the OpenFlow suite of providers as well as the ProxyArp, Multicast, Group, Meter, Flow (to name a few) core subsystems in ONOS. Furthermore, I designed and implemented the FlowObjective API which allows ONOS applications to be pipeline unaware and therefore be portable across different hardware switches.

In addition, in February 2015, I helped create CORD which is now mostly known as R-CORD where I serve as technical lead and architect. As part of CORD, I have helped design and build the solution from the ground up. Whether it was ONOS applications for the control of CORD or the design of the hardware POD. R-CORD has had resounding success and it is now undergoing a field trial with AT&T. CORD has now spun off two sister project named E-CORD and M-CORD.

Are you contributing to other related open source projects? Which ones?

I am the creator of OpenVirtex, our Network Virtualization Platform as well as the maintainer of FlowVisor which is a network slicing hypervisor. I have also made contribution to loxigen and floodlight.

David Bainbridge

Jono Hart

Satish Karunanithi

Marc De Leenheer

Have you served on the TST before?

No

Are you a module owner? If so, for how long and for what modules?

I am a module owner for all the optical stuff in ONOS, as well as for most of the OpenFlow subsystem.

How long have you been making software contributions to ONOS?

I joined ON.Lab in January 2013, so in a way I was involved from the very start. At that time though I was mostly working on OpenVirteX, our network virtualization platform.

What are your most important software contributions?

I drove most of the work on packet/optical convergence in ONOS. In doing so, I probably touched on most - if not all - subsystems. For instance, I built most of the optical information model in the core, wrote a few optical intent compilers, helped build the resource management subsystem, wrote a ton of SB code and drivers for weird optical devices, etc. I don't consider myself an architect of grand schemes, but I'll get the job done

A couple of months back, I started the Enterprise CORD project, to offer carrier grade enterprise connectivity (think L2VPN etc.) as well as innovative services using CORD. With my team, we're tackling some of the hardest issues for the community: scalable delegation between multiple layers of control, white boxes for Ethernet aggregation, selection of transport and service APIs, ... At the same time, we've built what we believe to be a really disruptive technology: an optical switch built from commodity components, all controlled using the network OS you know and love...

Are you contributing to other related open source projects? Which ones?

OVX was really my first move into the open source world, and ONOS is my second.

Sho Shimizu

Have you served on the TST before? If so, for how long?

No

Are you a module owner? If so, for how long and for what modules?

I have been a module owner of Intent Framework and Resource Service subsystem since we started the module owner system.

How long have you been making software contributions to ONOS?

I have been contributing to ONOS since June 2014 just after ON.Lab started the partnership program with the industries.

What are your most important software contributions?

I re-designed Intent Framework API to be the present form about 2 years ago, considering both application developers' productivity and extensibility. I have been implementing the core of the framework and wrote many intent compiler implementations. I have been iteratively improving the implementation and doing many code review for incoming patches.

I'm leading Resource Service subsystem design and implementation from July 2015. It's a really important API for us to manage any kinds of resources found in a network like VLAN IDs, MPLS tags, wavelengths, etc. The API provides unified way to allocate/deallocate resources and increase developers' productivity with transaction support.

Are you contributing to other related open source projects? Which ones?

I was contributing to Floodlight, Big Switch Network's OpenFlow Controller as the first external contributor. You can see my name in the commit log. I also contributed small patches to Floodlight Quantum plugin and Atomix, which is distributed coordination framework on top of Raft consensus protocol.

Release Steering Team

Bill Snow

Community Steering Team

David Boswell

-------------------------------------------------------TEMPLATE - Nominees, please copy the following and fill it out under your name on this page