Technical Steering Team

Ali Al-Shabibi

David Bainbridge

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

No, I have not served on the ONOS TST before

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

No, I am not module owner within ONOS

How long have you been making software contributions to ONOS? 

While I have been aware of the work going on in ONOS for about two years, I have only become more directly involved with ONOS for about a year. I have directly contributed minor changes to ONOS as I believe that ONOS is a part of a large micro service ecosystem.  Thus the majority of my effort is understanding how ONOS functions in the broader scope and integrates with platforms like Kubernetes and
Swarm.

What are your most important software contributions?

As stated my most important contributions are not direct contributions to the ONOS code base. Instead I feel my most important contributions are open source code that integrate the ONOS notification system with Kafka and / or RabbitMQ so that micro services that execute outside the ONOS process can participate in the SDN ecosystem. Additionally, I have created open source wrappers around ONOS such that it can participate in frameworks like Kubernetes where the scale of a micro service is controlled by an external entity. Bringing this more global view to ONOS is one key to its success, as ONOS will mostly be deployed as a component of a larger solution and not the solution itself. This is demonstrated by the CORD solution.

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

I have contributed to the OpenDayLight project in the past and been project technical lead for the ODL discovery project as well as the ODL intent project. I have contributed to other open source projects such as OpenTSDB. In general, when I develop code in and around ONOS I do so as open source, thus the integration projects I have done with ONOS are technical open source projects, but I may be the sole contributor.

Jono Hart

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

Yes, I was added to the TST in September 2015.

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

As a current TST member I have module owner privileges for the entire codebase.

How long have you been making software contributions to ONOS? 

I joined ON.Lab and the ONOS project in November 2012, so I have been heavily involved in the ONOS project almost since the very beginning. I was a member of the core team that worked on the initial ONOS prototype, and I’ve worked in a number of different areas of the current codebase, so I have a large breadth of knowledge of the ONOS architecture and codebase.

What are your most important software contributions?

I have been driving the work on routing applications in ONOS, beginning with SDN-IP, which was one of the first applications used to showcase the ONOS platform. I’ve built on top of that work to create the BgpRouter application (now part of Atrium) and the vRouter application, as well as a number of other applications as part of the CORD use case.

I’ve contributed to the design and implementation of many of the core subsystems, including proxy ARP, the intent framework, the interface subsystem and more. I undertook the initial implementation of the EventuallyConsistentMap primitive which is now the base for many of the distributed stores in ONOS. Recently Ali and I designed and implemented an extension framework for our northbound APIs which enables ONOS applications to utilize new switch behaviors without having to deform the core architecture. 

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

I’m a core contributor to the CORD project, and I've made some small contributions back to Mininet.

Yuta Higuchi

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? 

Yes, for the whole code base since the beginning of ONOS release.

How long have you been making software contributions to ONOS? 

We have been involved since the launch of ON.lab, I myself have been involved with ONOS code base since June, 2013.

What are your most important software contributions?

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.    
Recently I’ve been working as part of E-CORD team, exploring pieces needed to create a hierarchy of ONOS, such as mechanics to provide abstract view to higher-level control using gRPC, etc.

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

Just fixing tools, etc. which I was using at that moment. Trema, Cucumber-ruby, ODENOS, mosh.

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.

Patrick Liu

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

No. However, I am the member of ONOS Release Steering Team (RST) for about a year.  

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

I am not Module Owner.

How long have you been making software contributions to ONOS?

I started the work on ONOS project back to end of March, 2014. I involved in the initial ONOS prototyping work and the major contribution were in Use Cases such as IP+Optical, IP RAN,  and HA. After ONOS became open source project one year ago, I served as a technical leader and architect for Huawei's ONOS development team. and led this development team to contribute in NB protocols, Core Modules, Interface to OpenStack Neutron, Virtual Tenant Network(VTN) and Service Function Chaining (SFC). Right now, I am leading the design of Yang Shell Project - Add YANG service model support capability for ONOS.  

What are your most software contributions?

1. YANG Shell Project (in design phase), which adds YANG model support for ONOS and fills the gap between ONOS and its competing open source controller project.
   1. ONS 2016 YANG model support in ONOS speech: https://www.youtube.com/watch?v=lOv5kDbIIJM&feature=youtu.be
   2. Project wiki: YANG Models in ONOS
2. Virtual Tenant Network (VTN) manager and Service Function Chaining (SFC) Application for ONOS.  and the interfaces to OpenStack Neutron. Through adding these features in ONOS, we successfully pushed ONOS as an option of SDN controller into OPNFV Release Software Stack.
   1. Project wiki: ONOS Framework (ONOSFW) for OPNFV
   2. OPNFV Release B: http://artifacts.opnfv.org/opnfvdocs/brahmaputra/docs/platformoverview/softwarearchitecture.html#software-architecture
3. IP RAN use case, which contributed the WAN required features to ONOS such as Tunnel Manager, MPLS Label Manager and Flow Rule Extension.
   1.  https://www.youtube.com/watch?v=dsrs6uD_Fgk
4. Defined the behaviors and requirements of ONOS HA, which provides the guideline for system testing of HA feature.   
5. Defined the first ONOS OpenFlow based ROADM model (Thank NEC and ATT folks for such a great team work on inventing this model). This model is used by current IP+Optical use case.   

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

Yes. I am the committer of ONOS Framework (ONOSFW) project in OPNFV community. as one of the key members in ONOSFW project, I participated in each cycles of the project, which includes initiating the idea, making the proposal, system design, till successfully released in OPNFV Release B.      

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 designed the basic structure of the current Intent Framework API 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 reviews for incoming patches.

I have been leading Resource Service subsystem design and implementation since 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. I also contributed small patches to Floodlight Quantum plugin and Atomix, which is distributed coordination framework on top of Raft consensus protocol.

Real World Deployment  Steering Team ( Proposal ) 

Service Provider's ON.lab Partners:  (AT&T, VZ, SK, NTT, China-UniCom) + potential EE/BT, Reliance, Orange, Telecom Italia, 

System Integrators & Collaborators ( Vendors, Content Owners, Gaming Industry, IEEE, 3GPP, 5G America, 

Use Cases: IOT, VR/AR, Gaming, Health ( Critical IOT) , Education, Smart Cities

CORD reference platforms and blue prints for deployable sites 

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

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

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

How long have you been making software contributions to ONOS? 

What are your most important software contributions?

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