Recognizing the contributions of your peers to the success in delivering ONAP Amsterdam.
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
Top Achievement Award
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.
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.
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 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 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.
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.
Since the early involvement in merger negotiation of OPENO and OPENECOMP, she has been making extraordinary contribution to the ONAP community, from the design of merge architecture for Amsterdam release, the organization of business scenarios of VOlTE use case, to diving the discussions of key technologies and landing the whole implementations, e.g. the hierarchical workflow integration in SO, the collection and correlation of cross-layered alert/data into DCAE/Close loop, SDC business modeling and so on. Lingli is an evangelist of the community. She’s devoted to a culture that promotes fairness, a sufficient degree of openness, and a context for China developers to enroll and contribute to the whole community. She is an ambassador of the community. She keeps active participation in community activities promoting the pluralistic environment with global operators and vendors to commercial prospects of ONAP.
Manisha is one of the A&AI contributors and has worked diligently to establish A&AI in ONAP. Manisha helped A&AI reach the goal of 100% automated builds and instantiation by leading the A&AI project to follow recommended guidelines and processes, defining configuration and troubleshooting issues. She led the team to contribute 100% of non-AT&T specific code to ONAP, though managing the user story backlog and helping to move the submission process forward.
As dev liaison/project lead for AAI for OpenECOMP Release 2, she created/assigned Jira user stories and tasks and worked with our internal scrum teams to deliver the code on schedule, and managed image/artifact tagging/release branch, versioning etc. in Gerrit. She played a key role in formulating the documentation and proposed AAI as a project at the ONAP Developer’s conference in Middletown in May. She also presented the A&AI project at the Beijing Developer’s Conference, where AAI was approved as an ONAP project. She smoothly transitioned the role to a team member as she took on a new role. As a committer for Amsterdam and Beijing releases, she reviewed and merged submissions to A&AI in ONAP and provide guidance on architecture issues as necessary. As one of the development leads for A&AI, she defined a process to identify non-AT&T specific code, track and improve the time taken for the integration of code from/to ONAP.
Maopeng Zhang makes great contributions in ONAP NFV domain, who imports the ETSI NFVO and GVNFM architecture/feature in the ONAP, which make the ONAP more popular and acceptable in the CSP. He makes great contributions in the VFC integration with ONAP SDC, AAI, SO, multivim, and Policy, and also cooperate with different VNF vendo in the ONAP Amsterdam release. Maopeng Zhang takes part in the usecase, Model, architecture subcommittee and prompt the VoLTE case successfully implication as well. He also present the ONAP integration in the GNTC meeting.
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. Altough 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.
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
Bin is the core committer from MultiCloud project. Beisdes his great contribution to MultiCloud project, he provided help for the pairwise integration with APPC project, DCAE project and SO project, which ensure the success of end to end integration test for ONAP Amsterdam Release. He also volunteered to support Integration lab as well as VoLTE physical lab to resolve many issue with regards to infrastructure cloud.
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 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.
Dan has provided assistance to many people through responses on the onap-discuss mailing lists, wiki question answers, presentations of the end to end platform, and working with many projects to create an end to end integration test of the platform. For example, he ranks 4th on emails sent list and provided assistance on broad range of topics at detailed technical levels.
Eric always made himself available to other teams whereever and whenever thet needed his help. He produced a great deal of documebntation and played a key role in making necessarry updates and changes in Readthedocs for the release.
Gary is 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. He has 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 and Contributed numerous fixes and code-refactoring across multiple projects such as appc, sdnc, mso, and sdc. Gary has been influential into defining the appropriate way to understand the difference between the 2 former communities and propose a solution to deliver efficiently all binaries into the repository manager. Thanks to his deep knowledge of the whole tool chain, Gary has diligently conducted to success numerous members who were desperately looking for help to move forward.
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.
AS the PTL of integration project, Helen made outstanding contribution to the whole ONAP community. Especially in the stage of integration testing, she led her team members to actively communicate with each project, successfully completed the test and verification of all use cases in Amsterdam release.She showed good leadership and aslo made many constructive suggestions on community-related issues for Amsterdam release.
Huabing provides lots of help to support ONAP projects to leverage the microservice infrastructure capability provided by MSB, including tutorials in F2F meetings, education in Zoom meetings, code examples, timely response to community mails and lab support. To save the integration efforts of all the projects, he aslo developed kube2msb registrator that can register the microservices to MSB automatically, which significantly accelerate the integration process.
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.
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.
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.
Pam is extremely active and engaged in many aspects of the community outside of her project. She is always willing to help and does a great job helping to bridge the gap. She both provides suggestions and listens to the input of others to find the best ways to address an issue, whether the root cause is technical, political or social.
Randa is the ONAP APPC PTL. In addition to the deliverables related to her project, she has been instrumental for the certification of the Multi-Vim project, driving all the associated testing activities, involving the other impacted projects.
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 Rich 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 and Developed Amsterdam branching strategy.
Code Contribution Award
Presented to the software contributor who developed the highest quantity of quality code as judged by the PTLs, Committers and Contributors.
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.
Honghui's work on hierarchical binding based integration with the third party SDN controller. HongHui is an active contributor in multi-vim/cloud project. He also plays an important part in the integration of use cases. In VoLTE use case, there is a requirement to connect two data centers by using EVPN/VXLAN. Normally, this is done by connecting OpenStack with some specific networking hardware. Networking hardware vendor will provide solution of connecting based on OpenvSwitch. However, there is no EVPN support in VIO (VMware Integrated OpenStack), nor did VIO support OpenvSwitch. And VIO is deployed in one of the data center. So, there is problem of connecting two data centers. To solve this problem, HongHui did some investigation about how OpenvSwitch connects to the specific networking hardware, how OpenStack orchestrates such connection and how VMware VDS (virtual distributed switch) works. And then he delivered a driver to connect VMware VDS and specific networking hardware. There are only about 100 lines of code in the driver. However, the code, which has been proven by VoLTE use case, can be said neat and stable.
As the main committer of VF-C, Jinhua Fu made outstanding contributions to the implementation of VF-C's main functions in Amsterdam release, including not only code contributions and testing, but also technology sharing. It did a lot of tentative work and provided effective guidance to all team members. From ONAP community Git contribution rankings(2017-06-01~2017-12-05), His code contribution also ranked in the top three.
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.
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.
Lusheng Ji was a committer and major contributor to DCAE open source seed code and a substantially new version, DCAEGEN2. In delivering DCAEGEN2, Lusheng contributed to Amsterdam use cases, establishment of test labs, and integration tests.
Murali Mohan Murthy Potham (Murali P):
He was the top contributor in the VNFSDK project, leading the development of the marketplace component. As part of the work, he migrated from mysql to PostgreSQL and refactored significant portions of the web ui. This resulted in significantly REDUCING the size of the vnfsdk codebase. I think Murali deserves credit for putting clean code over lines of code as our driving metric.
Patrick Brady was a committer on the APPC project; he delivered high quality code, but also debugged issues in other projects (e.g. CCSDK) and made these changes in those other projects to unblock APPC. He made extensive contributions to the code base and was prime for the Gerrit/GIT repo management.
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.
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.
In Amsterdam version, Yunlong undertook and completed several important functions of VFC project development and testing, contribute a lot of code, become one of the main contributors to VFC Project, from Onap community Git contribution rankings(2017-06-01~2017-12-05), Yunlong is the highest contributor.
Project Achievement Award
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.
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 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.
The CLAMP Team:
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:
- 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 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 SDC Team:
The SDC project had significant changes needed to support new functionality being added to the Amsterdam release in support of features added by the VF-C, Holmes and other new projects. The team worked very hard to understand those requests/requirements and add the needed functionality to support these key activities in the community.
The VFC Team:
VF-C comes from OPEN-O, as the main part of the integration between OpenECOMP and OPEN-O, VF-C completed Network Services and VNF lifecycle management and FCAPS management functions with high-quality code. In order to better integrate with other ONAP projects, VF-C did a lot of integration and testing work.In Amsterdam release, VF-C completed integration and testing with 9 projects, delivering 15 components. All the milestones completed on time. VF-C also integrated with three vendors’ commercial components in VoLTE use case, such as VNFM and EMS. VF-C team also made outstanding contributions to support VoLTE use case integration testing.
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.
Architecture Subcommittee “Tiger Team”
This team was led by Parviz Yegani. While most of the components in ONAP came from either OPEN-O or ECOMP, the tiger team is re-imagining ONAP from a cloud-native perspective and taking active steps to blend the two architectures, while introducing new concepts designed to make ONAP fit into emerging opportunities.
The 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
The Modeling Team:
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.
The MSB Team:
ONAP aims to provide a scalable and resilient network automation platform with the microservice approach. In Amsterdam, MSB project provides microservice infrastructure for ONAP including service registration/discovery, reliable inter-service communication and external API gateway to expose ONAP services to external systems, which fills up the missing part of the initial codes and allows ONAP continually evolve towards a carrier-grade open platform.
The Multi-Cloud Team:
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.
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.
The SO Team:
If there is a project without which ONAP could not run, it is Service Orchestration. Residing at the top of the pyramid, SO has made all the impossible tasks to accommodate the needs of 2 dependent projects and to interface with them seamlessly. Despite the challenges, methodically SO team has demonstrated his expertise and skills to converge toward a working solution
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 and has been doing most of the changes. 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.
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.
- Led Tel Aviv hackathon, in partnership with local AT&T and Cloudify teams
- Spoke at L123 mini-summit
- 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
- European City Tour lead and London site host and speaker; also help co-sponsor and co-organize Paris event
- Significant contributor to:
- ONAP core messaging and FAQ
- Initial ONAP U proposal
- Leader of Amsterdam promotion activity in China
- Organized press release translation between Huawei & ZTE; also contributed member quote sheet translation
- Organized CMCC-Huawei Amsterdam launch ceremony in China, with video
- Primary driver of Chinese press coverage, with at least 9 unique articles
- Contributed 2 use case videos
- Designated SME/reviewer for Residential vCPE whitepaper