...
...
...
...
...
...
...
...
...
...
...
...
...
Recognizing the contributions of your peers to the success in delivering ONAP Amsterdam.
>>>>> VOTE HERE! <<<<<
...
There were 87 nominations representing 53 uniquely names individuals and projects, and 571 votes cast.
Winners were announced on Dec. 11, 2017 and are highlighted in each section
Catagories
Top Achievement Award
...
Brian has demonstrated unparalleled dedication. At the ONAP Launch, he built demos and wiki pages supported by Marco Platania, focusing on vDNS and vFW.
He also provided a lot of support to the community by answering a lot of questions. He regularly provides his technical perspective for the benefit of the community
Brian was able to demonstrate Clearwater vIMS On-boarding and Instantiation with no code change within a very limited time. He played a pivotal role in our successful Amsterdam release, driving all the testing activities related to the vCPE use cases (testing debugging and fixing any issue that was identified), working jointly with Intel (debugging, fixing), the Integration project and any impacted PTLs including weekends and evening while he has no PTL role and is not a committer for any project.
Catherine Lefevre: WINNER
Catherine has worked tirelessly across many groups and companies, evangelizing ONAP, representing ONAP in various different forums in EMEA & locally. Working closely with Gildas on many aspects of the release and providing support to TSC to help drive various activities to keep release on track.
Chris Donley:
By applying consistently his longtime experiences and roles in numerous Open Source projects, in ONAP Chris has demonstrated his capability to reach consensus by listening to all opinions and documenting thoroughly the key decisions items. In a lot of circumstances, Chis brings suggestions to get things moving in the best interest of the community. Chris has this unique way of articulating his thoughts that makes you adopting his leadership. With his role as Architecture sub-committee Chair, Chris has tremendously helped in the merger of both communities and has been instrumental to deliver ONAP.
...
As our release manager Gildas worked relentlessly to ensure that we stayed on track with deliverables, often spending large periods of time with the PTLs and the LF to work through issues and always looking for work-arounds to problems in addition to developing numerous templates and process recommendations to help improve the lives of the Dev community and make things easier for all involved. Throughout the release he balanced "tough love" and a great sense of humor in all of his dealings.
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.
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. 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.
...
Brian worked tirelessly across many teams and in different capacity from architecture input, use case support, individual projects support, and integration testing support to drive completion and delivery of Amsterdam Project.
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
Chris Donley: WINNER
Chris has performmmed 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.
...
In addition to the code that he was developing in the context of the CLAMP project, Sebastien has increased the test coverage beyond the original test coverage target. He added jUnit test cases in various areas of the project even if he was not responsible of the associated source code.
Seshu Kumar: WINNER
If there is someone who can do something to make a difference and impact positively the community it is Seshu. 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.
...
Although this project was not originally part of the ONAP launch and was not identified as a Amsterdam gating project, the CLAMP project delivered all milestones on time. In addition, CLAMP is one of the key components of the Control Loop that it provides the necessary automation to proactively respond to network and service conditions without human intervention. Along the Release, CLAMP always got things right the first time. There is barely anything CLAMP had to redo. The Team is mastering all the aspects of the development lifecycle, processes and tool chain. CLAMP is excellent to get things running as it should, and should be treated as “Best in Class” for all its deliverables.
The Integration Team: WINNER
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. Along the way thet had to covercome a number of challenges: The initial lack of pairing testing before they got started, Network connectivity issues to the labs, Unstable hardware environment, The staging repo Gerrit failures. All the while they accomplished several major achievements:
...
The Multi Cloud design and implements of keystone proxy and extensible API framework which simplified largely the integration between OPENO and OPENECOMP modules.
By keystone proxy, the modules currently depend on OpenStack including SO, APPC, and DCAE can consume Multi VIM/Cloud resource LCM functions by configurations changes which is proven valuable for the tight delivery cycle of R1 and deliver of vFW and vCPE use cases. By the elastic framework, Multi Cloud well supported non-OpenStack functions including FCAPs and provided a way to expose special capabilities from different backends. Based on this framework, Multi Cloud successfully support the requirements from VFC and help the delivery of VoLTE use case.
The OOM Team: WINNER
The OOM project has made a tremendous contribution to the ONAP project by bringing an overall Operations Manager environment. In addition, with it's first implementation focusing on ONAP On Containers, it provides a significantly more accessible deployment environment allowing ONAP to run on a potential new user or developer's laptop instead of a very large, and expensive set of VMs. These innovations will prove highly advantageous to the ONAP community at large.
...
- Led Tel Aviv hackathon, in partnership with local AT&T and Cloudify teams
- Spoke at L123 mini-summit
Chris Donley:
- Lead writer of architecture whitepaper, with Paul Bartoli of AT&T; coordinated all feedback within the Architecture committee
- Regular speaker on behalf of ONAP at events around the globe
- Contributed key architecture overview video
...
- Site host for OSN Day, Paris
- Site host for OSN Day, Paris
Lingli Deng: WINNER
- Regular speaker on behalf of ONAP at events around the globe
- Contributed 2 technical videos in English, 3 in Chinese
- Led review team for VoLTE whitepaper
- Frequent coordinator of Chinese contributions to marketing and marketing-related activities
...