...
Vote to recognize the contributions of
...
your peers to the success in delivering ONAP Amsterdam.
...
To vote on these awards please use THIS LINK.
...
Voting closes 1 PM, Pacific Time,
...
Monday Dec.
...
11th.
Catagories
Top Achievement Award
Citizenship Award
Marketing Award
Code Contribution Award
Project Achievement Award
Innovation Award
Top Achievement Award Anchor top top
| top | |
| top |
Presented to the individual who has demonstrated unparalleled dedication
...
in the formation and prosperity of ONAP,
...
whose exemplar behavior and actions as a champion for an atmosphere of equal cooperation between member companies, individuals and geographies, played a pivotal role in our successful merger of multiple code bases, a timely delivery of the Amsterdam release and a thriving global community.
Nominees:
Helen Chen:
Helen has played a critical role on successfully integrating all code bases and delivering the Amsterdam release on time. Helen's dedication and tireless hours put in related to getting the integration of ONAPs first release completed on time and leading a great set of integration team members from the whole community of diverse companies, across multiple labs , time zones and countries. Helen has also personally helped to get the use cases working in the specific labs. The travel time and hours spent in getting things to work with real network equipment was challenging , (especially with the US holidays), but successful. Besides integration work, she has demonstrated her leadership in leading the discussions with “upstream principal” in the ONAP community, which has helped the community to build a healthier foundation, and in making the hard decision of defining the ONAP deployment strategy, heat vs OOM for this release.
Michael O'Brien
Throughout the Amsterdam release, Michael has humbly demonstrated a singular dedication to the successful integration and interworking of ONAP components and openly sharing all the collected knowledge gained along the way. This journey has involved working with many different teams such as Integration, OOM, Logging & Analytics, SO, AAI, SDN-C, and SDC.
Though the official release is out, Michael’s efforts continue without pause. He’s leading the charge to ensure anyone that wants to use ONAP Amsterdam can do so, without workarounds or close-held expertise. He also is continuing to push cross-collaboration, by helping guide our OPNFV colleagues to a successful demo at Kubecon.
Fun bonus fact: Michael has deployed ONAP more times, and in more varied environments, than anyone else on Earth.
Kang Xi:
His dedication through the integration testing of vCPE for ONAP was critical to the on time delivery. Through multiple test sessions per day through weekends including both writing scripts to streamline the testing but active debugging to help the dev teams find , fix and verify bugs was awesome.
Jimmy Forsyth:
Jimmy had a huge impact on moving A&AI forward in ONAP, taking on the ESR (External System Register) sub-project to AAI and worked to onboard folks from ZTE and Huawei who needed to use AAI in the development of ESR.
Milestone 1 of R1 Amsterdam for AAI. Jimmy defined all project deliverables, including functional architecture, scope, dependencies, test cases, packaging and installation strategy and filled out the Release Planning and Deliverables for Planning Milestone Checklist Templates. He provided onboarding guides for ONAP community members and wrote a full developer’s setup guide which showed how to pull, setup an IDE, build the microservices, and deploy the services in a development environment. This was instrumental in getting VF-C and MultiVim (former Open-O projects) to adopt AAI in ONAP, and he received contributions from VF-C and MultiVIM teams.
Milestone 2 for AAI Amsterdam: Jimmy defined and documented AAI Functional Test Cases and produced a stable document describing the API and made it available on the wiki. He tracked issues in Jira, wrote user stories to integrate internal AT&T features into ONAP, acted as committer (doing code-reviews and merging changes), and solicited help from the ONAP community.
Milestone 3 of ONAP Amsterdam R1: Jimmy worked with PTLs of client applications MSO, SDNC, Policy, APPC, VF-C, ESR to gather requirements for changes needed in support of Amsterdam. He completed API and Data freeze. He led the effort to get 50% of Functional Test Cases automated.
ONAP M4 Code Freeze: Jimmy made sure that Jira issues were either fixed in the current release or assigned to the next release, that 100% of Functional Test Cases were automated, and led the team to achieve 30% SONAR coverage on all 17 AAI microservice and library repository.
Jimmy attended the ONAP conference in Paris/Saclay, represented AAI on a promotional video, and hosted a session on the future of AAI at the conference.
ONAP RC0-RC2: Jimmy provided support for AAI in the Windriver and Rackspace labs, managed Jira and tracked bugs in AAI, supported external users of ONAP AAI on the onap-discuss mailing list, tracked down Jenkins issues, and got all Jira tickets closed by RC2 on 11/9.
Amsterdam R1 AAI delivered. Jimmy made sure all Jira bugs were closed, all docker images were deployed to the public docker hub, all integration testing completed, and that AAI passed the release criteria.
Jimmy was also a key contributor on the VID project earlier in the year. He deployed the 1.0 version of VID for openecomp. As the leader of the VID (Virtual Infrastructure Deployment) OpenECOMP initiative, he was instrumental in the coding, automated builds, named-queries for closed-loop and instantiation of VID. He succesfully deployed the inital 1.0 version of VID. Using Docker, he made VID capable of automatic instantiation in OpenECOMP under rackspace. As a software developer, he contributed significant pieces of the OpenECOMP seed code, multiple bug fixes in the OpenECOMP version, ran black duck/fossology/GREP scans and performed reporting and remediation of issues uncovered by the scan process. He innovated successful Jenkins processes to streamline the build of VID, converted code base to be free of proprietary markings, images, and logos, and remediated FOSS issues, replacing dependencies that were outside Linux Foundation standards with versions that are in compliance. He completed full integration with the openecomp Portal SDK and portal, opening multiple bugs against portal and contributing to their resolution. He merged 100% of non-AT&T specific platform software to ONAP.
As the leader of the OpenECOMP VID, Jimmy integrated VID into the LF, developed Jenkins Job Builder jobs to create builds within the LF infrastructure, and merged 1702 and 1707 ECOMP changes to VID.
...
Citizenship Award Anchor cit cit
| cit | |
| cit |
Presented to the individual who provided the most assistance to others outside of their own project, in the form of education, guidance, code reviews, debugging, bug fixes or similar support, whose behavior also help to impart a
...
culture equal cooperation between member companies, individuals and geographies
Nominees:
Catherine Lefevre:
Catherine made an outstanding job of assisting the ONAP community by supporting teams from all around the world and in different companies, Not only did she spread the ONAP word within AT&T but she also was a supportive voice for most of the contributing companies to ONAP (Ask people in Orange, Huawei, ZTE, LF, Amdocs … I’m sure they know her – in fact pretty much all ONAP projects have probably discussed with her) She was also supporting the most of the milestone achievement and reached out to find help on many fronts when needed. To me she certainly represents the core value of what an open community should be. She has been supportive in many many aspects (including legal, governance) and for all that I think she deserves the title
Michael O’Brien:
Michael is a natural collaborator and team builder. He’s skilled at identifying problems and gathering people together to solve them collaboratively. Michael has an unquestionable work ethic and an unstoppable desire to solve problems; he wants no part of the credit-seeking, inter-company politics that we sometimes encounter in open-source projects like this. In fact, he has a demonstrable track record of modeling exactly the type of open, collaborative ethos we want everybody to have.
Brian Freeman:
Marcus Williams:
As a committer on APPC, CCSDZ, and SDNC projects, Marcus used his prior experience with OpenDaylight community to migrate and integrate the incoming ecomp code into the new ONAP controller architecture.
- Marcus was active developing commits, reviewing other developers work, participating in meetings and on the mailing lists for all of these projects.
- Marcus provided support in developing directed graphs for SDNC to get the vCPE use case working in the final weeks of R1.
Marco Platania:
Marco's dedication to helping with the instantiation of ONAP instances via heat in multiple environments, the work with the VNF developer teams on their applications and leading the vFWCL testing in the final stage was instrumental in Amsterdam. By the nature of the demo team it is cross all projects and he as an example of easy to work with and technical breadth and depth we value in ONAP.
Rich Bennett
Rich has provided unparalleled Documentation support from the very beginning of ONAP (even pre-Amsterdam). Though much of his work has been “behind the scenes”, Rich has been instrumental in insuring the success of ONAP through his work in developing, testing and implementing the technical components and structure needed to support documentation. Among his many contributions:
- Coordinated much of the seed documentation, including initial Developer Guides
- Tested and troubleshot Documentation Tool Chain development
- Established and supported Jenkins job flows
- Tested and implemented Readthedocs structure
- Provided ongoing technical support for all ONAP project teams
- Developed Amsterdam branching strategy
Gildas Lanilis:
He has been proactive in reaching out across projects to help the PTLs and the community. In addition to managing the release process, he has been developing and sharing best practices, branching strategies, and other processes to help the community.
Gary Wu:
• Recognized by the ONAP community as an expert on CI/CD, build process, and environment setup; helped across ONAP project teams with code reviews, debugging, and training in those areas.
• Created and documented the Independent Versioning and Release Process for the ONAP community; assisted ONAP projects on its implementation.
• Implemented, documented, and provided training on CSIT infrastructure and process for the ONAP community.
• Contributed numerous fixes and code-refactoring across multiple projects such as appc, sdnc, mso, and sdc.
Chris Donley:
for his extremely valuable work in the TSC and ARC. The important works include: education, guidance and review on how to develop and communicate in open source team. Whose behavior really help to create a culture equal cooperation between members, it’s really important for ONAP as a new community.
...
Marketing Award Anchor mkt mkt
| mkt | |
| mkt |
Presented to the individual who provided the most support to the Marketing and PR teams, and generated and/or supported development of documentation, videos, tutorials, press/analyst interviews, webinars, etc.
Nominees:
Lingli Deng
Chris Donley
Mazin Gilbert
Alla Goldner
...
Code Contribution Award Anchor code code
| code | |
| code |
Presented to the software contributor who developed the highest quantity of quality code as judged by the PTLs, Committers and Contributors.
Nominees:
Kanagaraj Manickam:
Contributed to ONAP CLI project with high-quality code and made this project to achieve the highest score in quality gate (sonar) with
a. 1st in code coverage (82.5 %) across ONAP projects.
b. ONAP CLI project quality gate Status: green
c. Duplicate code count: 0 (zero)
Implemented maximum no. of commits as well as commands (90%, 79/87 commands) in ONAP CLI project.
Ruijing Guo:
Ruijing Guo worked on multiple projects in ONAP including Policy, SDNC, Multi-VIM etc. His code quality is high. During Amsterdam, overall he submitted 47 commits which caused 160K+ lines were changed. Most of his patches are to merge seed code from OpenECOMP to ONAP and fix critical sonar issues in policy, setup ONAP demo, fix build issues in SDNC, and setup test framework for multi-VIM. The biggest patch he made (https://gerrit.onap.org/r/#/c/6081/) is to replace OpenECOMP with ONAP for policy-engine together with the project PTL Pamela Dragosh. That patch review lasted 10 day and the commit caused 161066 lines added and 161064 lines removed. At the first glance, the commit was mostly physical work however after replacing and renaming, he needed to fix build errors and make the component run correctly. The policy-engine was the biggest part in policy merging, and its code changes were taken very carefully before the commit was merged. Finally it helped the entire policy merging process succeeded.
Seshu Kumar:
Seshu played important role in leading SO project reach the critical milestones, esp the M4 and further where the time was critical. He also helped in resolving some of the blocking issues on time, which helped ONAP deliver the release ontime. Seshu has been the top contributors from the number of commits and ranked amongst the top 5 authors in the ONAP community and has been consistent in his contributions. He has also provided multiple Tech talks on ONAP and SO in various forums and branded ONAP in IIT Madras one of renowned universities.
Dan Timony:
Dan Timoney not only serves as PTL for the CCSDK and SDNC projects but he has also contributed a significant amount of quality code to ONAP for the Amsterdam project. Dan has been on the leading edge of the controller technology in ONAP and his contributions to the CCSDK sets the foundation for multiple controllers to be built upon. Dan consistently ranks near the top of software contributions across the ONAP projects. Besides the quantity of code that Dan has delivered, his deliveries have been high quality with very few defects. Dan’s contributions to Amsterdam, not only around software delivery but also partner collaboration, qualifies him as a worthy recipient of this award.
Jorge Hernandez-Herrero:
Jorge set an incredible high standard when it came to pulling together the Policy code for Amsterdam. He designed and built a telemetry API on top of the Drools PDP Controller which enabled the community to more easily debug Control Loop scenarios. He led a team of developers to enhance the development environment for building and testing Policy Templates that the community will be able to begin utilizing going forward. Jorge set a high standard when accepting code submissions and displayed a keen eye when came to identifying how submissions for one repository would have an effect upon another repository. Jorge also provided the majority of support to the Integration team, forgoing vacation time and weekends, when it came to testing and supporting the Use Case testing.
...
Project Achievement Award Anchor proj proj
| proj | |
| proj |
Presented to the Project which made the most significant technical progress while delivering all milestones on time,
...
serving as a model for other projects to follow.
Nominees:
The Integration Team:
The Integration Team had a tremendous challenge given it was our first release working together. Integration testing was critically important for success to meet our Amsterdam delivery date. Without it – we would not have had an ONAP Amsterdam release. It is where the rubber meets the road. Validation of the code which was delivered that the different projects do work together and we have a platform as well as running use cases.
- They drove both vCPE and VoLTE use case detailed design and talked with ALL projects to get the flow and assets implemented
- Over the course of ~2 months they ran an average of 5 hrs a day of testing, almost 5+ days a week. That is 600+ hours of testing sessions
- They successfully implemented all use cases, vFW/ vDNS (@Integration Lab), vCPE (@Intel/Widnriver Lab) and VoLTE (@CMCC) on time
- The overcome nemerous issues including:
- The initial lack of pairing testing before they got started
- Network connectivity issuers to labs
- Unstable hardware environment
- The staging repo Gerrit failures
The AAI Team:
Throughtput the Amsterdam cycle they have been stepping up to help teams understand how to use AAI and how to either correct they way they were using it or to help work around knowledge gaps and or bugs in the system. The project met their milestones with a process the emphasized teamwork across all the various piece parts of AAI.
The MSB Team:
In Amsterdam, Microservices Bus (MSB) project provides infrastructure to support ONAP Microservices architecture including Service Registration/Discovery, Internal API Gateway, External API Gateway, MSB SDK, etc. By delivering MSB APIs and Functionalities ASAP, MSB has provided a consistent way of service discovery and inter-service communication while OpenEcomp and ONAP were merged. And as a common service project, MSB always tries its best to deliver the milestones on time to support the projects that depend on it.
The CCSDK Team:
The CCSDK project has set the foundation as the software base of all controllers to be built upon. It’s integration with OpenDaylight as well as its directed Graph technology allows projects to quickly build SDN services in the controller space. The directed graph technology allows programmers to easily access the necessary adaptors to enable service provisioning. The contributions of CCSDK were not only used by the Application Controller (APP-C) but also the SDN-C project to quickly build and enable the defined user cases for the Amsterdam release.
...
Innovation Award Anchor inno inno
| inno | |
| inno |
Presented to the Project which delivered a new compelling feature or capability in ONAP (not originally delivered in Open-O or Ecomp) that has significantly impacted ONAP in one or more areas including but not limited to architecture, integration, SDOs or security. integration, SDOs or security.
Nominees:
The ONAP CLI Team for OCLIP - Open Command Line Interface Platform:
Any product/platform in the Telco/IT enterprise provides the CLI as part of it, such as OpenStack, K8s, Docker. So for developing CLI, there are many open-source libraries exist today. Vendor/community make use of these libraries and spend lengthy development cycle for implementing any new commands or enhancing existing commands. This involves lots of effort (time, money, energy) and causes the user to wait for atleast one release-cycle (approx. 6 months) or patch-cycle (approx. 1 month) to get those fix/new commands. This problem is being repeated across different vendors/communities.
OCLIP enables the development of CLI just by authoring valid YAML text, which empowers the users to develop commands by them-selves and no need to wait for release/patch cycle. Also it helps vendors/communities to completely avoid the lengthy development cycle and saves those lengthy efforts. It can be used for any cloud enabled products, which provides feature over HTTP(S). This platform defines Open CLI Specification (OCS), which is similar to the Open API specification (OAS) defined by swagger for REST API. In 87 CLI/commands in the Amsterdam release the ONAP CLI were developed by using this platform. More details:
OCLIP: http://onap.readthedocs.io/en/latest/submodules/cli.git/docs/OCLIP.html
OCS: http://onap.readthedocs.io/en/latest/submodules/cli.git/docs/open_cli_schema_version_1_0.html
Victor Morales for Vagrant:
This project was started as an attempt to deploy ONAP services without relying on a OpenStack deployment. The Vagrant project provides an automated tool to provision ONAP development environment and it can be used during the development cycle. This tool covers some common development tasks such as the cloning source code repositories of specific component, compile java artifacts per component and building Docker images of specific component. The tool has been standardized for its reutilization and since this tool provides an automated provisioning mechanism it’s possible to setup a development environment using a single instruction resulting in a quick way for new developers to easily start to contribute. This is an excellent innovation to save valuable time and get an ONAP environment up and running in no time.
Also adding this tool into a CICD pipeline can help to prevent any compilation failure in the future and guarantee that build image process is working any time. Victor started this project on April 25 [1] and has been doing most of the changes[2] (the rest of the contributions history was missed when it was moved to ONAP integration project). Victor contributed over 100 commits and over 8000 lines of code to this project. For now, Vagrant tool is part of the integration project but it will most likely be moved to its own repo and will be possibly renamed. Helen Chen (PTL of Integration project) is aware of this project and also the SDC developers have been contributing to this as well[3].
[1] https://github.com/electrocucaracha/vagrant-onap/commit/a7c31aba8924e877faa1a611f236c747f67bd057
[2] https://github.com/electrocucaracha/vagrant-onap/graphs/contributors
[3] https://wiki.onap.org/pages/viewpage.action?pageId=15999821
The SDNC Team:
Besides delivering new capabilities like the vCPE resource allocation functions and the vOLTE 3rd party controller adapters the project incorporated changes in requirements as the end to end vCPE flow was being tested. The project delivered a bottoms up DHCP notification based flow that dynamically learns about new VNFs/PNFs on the network through interaction with DMaaP. The project also delivered the mysql to mariadb connector change on an emergency basis to resolve the FOSS issue.
Hui Deng for Modeling:
Hui has contributed one of the most important part “modeling” technology, which has been used fundamental differently between two original open source codes. Under Hui Deng’s leadership of both modeling sub-community and modeling project, modeling team also has spent lot of F2F meeting time to guarantee the success of the two codes, otherwise, without modeling harmonization, there won’t be any possibility for the 1st release of this two open source projects. At the same time, Hui Deng also got support from the community to act as the standard coordinator which allows the modeling team’s communication between ONAP and external SDOs, that also help the consensus of modeling spec. Finally he also host an independent ONAP workshop in December which will help to support the R2 modeling of ONAP by inviting many different SDOs to propose their contributions to ONAP.