Page History

...

I've started working on ONOS in October 2015 through my Internship at ONF, working on Southbound Integration, at the end of my internship I continued working part time with community focus until I joined full time at ONF in February 2017.  You You can find me on slack as @andrea

...

During my internship I built Support in ONOS for different southbound protocols, mainly NETCONF and REST, but also SNMP. I contributed to the development and enhancements of the whole southbound and drivers subsystem, with particular attention to FallBack providers and *Programmable classes (e.g. FlowRuleProgrammable). Many of these elements lay at the foundation of different use-cases and applications of ONOS today, such as ODTN and the P4 programmable data plane subsystems. I also worked on Alarm Alarms Subsystem. Since I joined full-time at ONF I worked in enhancing and supporting many use cases, such as Packet-OpticalTrellis, ODTN, P4 and P4 Runtime integration and lately Trellis and the Trellis troubleshooting Tool.

I'm a member of the P4 Brigade and act as a support role for the Security and Performance Brigade and the Teaching Brigade.

SEBA and it's ONOS apps.

In 2018 and 2019 I was part of the Trellis Team the brought ONOS in production at COMCAST.

Since July 2018 I'm leading the ODTN (Open Disaggregated Transport Network) project, building on the foundations of the ONOS platform we built a solution for Data Centre interconnect, integrating Openconfig Transponders, TAPI Open Line Systems and OpenRoadm ROADMS. ODTN went it's first field trial with Telefonica Del Perù in October 2019, where ODTN controlled two Edgecore packet optical transponders in both long-haul and short-haul scenarios. As ODTN lead I've led the path to a very strong collaboration with TIP and presented ONOS and ONF at many events (TIP summit, OFC, ECOC)

Since march I started also working with the µONOS team on the next generation of ONOS, micro-service based with gRPC interface and deployed on Kubernetes, my particular focus is onos-config, the configuration component of the new architecture, first demonstrated at ONF connect 19I also provide support for many community contributions, mainly in drivers and southbound.

I also ran multiple meet-ups and events as an ONOS ambassadors to share ONOS and spread the word about the project. 

What are you actively working on in ONOS?

Currently I'm working with the Trellis team. My focus at the moment is the Trellis Troubleshooting tool. This tools enables you retrieve flow rules and groups stored in ONOS that a particular packet hits. The tool enables to debug if the configuration and the rules are properly populated for you deployment. It's built with particular attention to the Trellis project but it's also usable on every general network.I'm also participating in the P4 Brigade with attention to P4Runtime southbound integration and gNMI configuration. SEBA team, we are just about to finish the porting of all the apps needed for controlling a POD to onos-2.2. Such porting enables the SEBA to rely on a much stronger platform with LTS relates of many components such ask KARAF, Java 11 and such. As part of the SEBA team I'm also working to support Deutsche Telekom workflows with ANY_VLAN support and FTTB flows.

In ODTN we are working for better Openconfig integration and building the Stratum Integration.

I'm also doing bug fixes and small enhancements across all the Platform with particular attention to the Southbound with attentions to always expand and hardened the ONOS capability to properly interact, control and configure devices. production deloyments.

In µONOS I'm keeping a close tab on the work in doing with onos-ran, although with little active contribution due to the focus on SEBA.

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

I feel I could be a good candidate because I'm deeply involved in the project and I deeply care about it's success and adoption. Having worked with ONOS since a long time I believe I have a good understanding and knowledge of the platform that could enable me to evaluate strength and weaknesses of different decision that are made from an architectural and implementation point of view. 

I also believe that my involvement in the community and brigades enables me to bring in new use-cases, ideas and a different perspective in the TST.  Finally my My unique position ad as an European Employee could benefit the TST to strengthen the relationship with European community, SPs and Vendors.

Also by sitting in the TST and at the same time being involved in SEBA and leading ODTN I could make sure the needs of both projects are accounted for during the TST decisions.

Finally I'm familiar with both ONOS "classic" and µONOS, thus being capable of discussing and deciding for both projects.

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

I'd like to continue pushing and advancing the interactions and the attention of the TST towards the community, both with ONF partners and members and with single ONOS contributors, working in a an even greater synergy.

An example would be push the brigades model even further by making sure that brigades are made from ONF employees, people from I'd like to expand the pool of people participating from Partners and Members of ONF and representatives of the community at large and that they have clear goals thus making sure that the ONOS roadmap is aligned with the ONOS roadmap. This would enable ONOS to achieve results that spread across everybody's interest and get it even more deployed in real networks. needs of anybody using and deploying the code.

As TST member I'd particularly put focus on production needs to make sure the platform is sound for the production deployments that it's currently in and is selected for in the future.