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, such as ODTN and the P4 programmable data plane subsystems. I also worked on Alarms Subsystem. Since I joined full-time at ONF I worked in enhancing and supporting many use cases, such as Trellis, ODTN, P4 and P4 Runtime integration and lately SEBA and it's ONOS apps.
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 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 Âµ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.
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 an even greater synergy.