...
Luis Gomez is an SDN Architect at Kratos Defense & Security Solutions. Previously he was a Principal Engineer at Lumina Networks and in the Open Source Software group at Brocade where he spent 7 years integrating, testing and supporting OpenDaylight in customer solutions, before he was a Solution Integration Engineer at Ericsson where he spent more than a decade integrating and testing service provider networks. Luis is also PTL of integration/distribution and committer in the integration/test, releng/builder, releng/autorelease and docs projects as well as test contact for OpenFlow plugin project. Most of Luis contribution is on test infrastructure and system test for OpenDaylight core components.
...
I would like to promote OpenDaylight as a network controller implementation of reference. There are lots of challenges today in the area of open and interoperable standards. And I believe OpenDaylight is one of the best platform to implement these new standards or to speed up their adoption, but also to mutualize companies effort to this end.
During these last years, I had also to take the train on the way and to learn from scratch how to integrate transportPCE to the OpenDaylight official distributions. I think that my experience can benefit the TSC to improve our operating modes inside the community and to attract new contributors. This last topic is getting more and more important since OpenDaylight has now a strong legacy and higher requirements for quality that are faced by newcomers.
@Robert Varga
Picture
Biography
Robert has been involved in OpenDaylight from its start, having co-authored the MD-SAL architecture and designing major portions of its implementation.
He is the overall top contributor on OpenDaylight and has contributed ~16% of all patches merged, touching majority of projects. He is a committer of a wide range of projects — odlparent, yangtools, mdsal, bgpcep, controller, aaa, netconf, vbd, infrautils and coretutorials.
His contributions tend to center around maven build system, overall architecture and high-level design (BGP, PCEP, OpenFlow Boron design, Virtual Bridge Domain), performance/stability-critical pieces of infrastructure and high availability.
His current focus is platform core use cases and related development.
Projects
Committer : odlparent, yantools, mdsal, controller, aaa, netconf, infrautils, openflowplugin, bgpcep
Contributions : All across the spectrum
Statement of Intent
- Drive technical evolution of the OpenDaylight platform
- Achieve fully modular release process
Anil Shashikumar Belur
Biography
Anil has been working with the Linux Foundation and the OpenDaylight Release management (since 2016, Beryllium Release). He currently serves as a TSC member, assisting the project/community on the infrastructure, CI, releases, and automation. He currently maintains some of the LF Releng repositories, performing regular release cycles on Global-jjb and LFTools which are used in many LF projects.
He started his career by experimenting with Linux in the late 90's and has been working with Open source over the last two decades. Prior to that, he worked with Security Engineering Team in Novell, File systems developer with HP and Systems Engineer with RedHat. He has contributed to MIT Kerberos project integration with LDAP in the past. His interests are in the area of Security & IdM, Networking, Systems engineering, Deep learning and DevOps.
Projects
- PTL: releng/builder, releng/autorelease, lf-releng/global-jjb
- Maintains and releases Global-jjb, common-packer, LF ansible and LFTools repos.
- Contributed and made improvements to Openstack Jenkins-job-builder.
- Mentored JJB intern for LF Internship 2018-19. Mentor on Community Bridge
Statement of Intent
- Improve processes and workflows within OpenDaylight, ensuring best practices are shared across LF projects.
- Optimize ODL's CI infrastructure/Jobs with a focus on quality, metrics, and minimize downtime.
- Continue making OpenDaylight Simultaneous Releases in a timely manner.
- Facilitate new developers to contribute to ODL and automate the infrastructure workflows.