Due to a ransomware attack, the wiki was reverted to a July 2022 version. . We apologize for the lack of a more recent valid backup.
Nominee’s bio (and/or LinkedIn profile)
How long have been working in the ONOS community?
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 can find me on slack as @andrea
What contributions have you made in the past to the ONOS community?
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. I also worked on Alarm Subsystem. Since I joined full-time at ONF I worked in enhancing and supporting many use cases, such as Packet-Optical, 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.
I 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.
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.
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 unique position ad an European Employee could benefit the TST to strengthen the relationship with European community, SPs and Vendors.
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 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 Partners and Members of ONF and representatives of the community at large and that they have clear goals 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.