Skip to end of metadata
Go to start of metadata

Recognizing the contributions of your peers to the success in delivering ONAP Beijing.

59 Nominations across 6 categories, representing  33 uniquely names individuals and 11 uniquely named projects

Please see below nomination statements in each category:

Top Achievement Award 

Citizenship Award

Code Contribution Award

Project Achievement Award

Innovation Award

Marketing Award



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 Beijing release and a thriving global community.

Nominees:

(alphabetical by first name)


Alla being a chair of ONAP Use case sub-committee is truly the individual who has demonstrated dedication to ONAP and a lead for an atmosphere of equal cooperation between member companies. She indeed played a pivotal role in the success of ONAP community.
Specifically she dedicates lots of her time to helping with meetings organization (part of f2f meetings program committees), helps new comers to get on speed in ONAP, promotes ONAP at different events and, in general, associated with ONAP success and diversity.
Brian has demonstrated his unparalleled knowledge of ONAP over most of the critical projects. He has provided a lot of support to the integration team and the ONAP global community through answering questions; and himself has done tremendous of works for ONAP pair-wise testing, use cases integration, 72-hours stability testing, etc.  weekend and over mid-night. He gave a lot of brilliant and constructive ideas to help ONAP community execute more smoothly, which greatly helped ONAP release on time.
Gildas was integral to the success of the Beijing release.  From managing dates and tracking progress against deliverables to approving new repositories and committer promotions to helping us all with our release notes, Gildas helped the ONAP community work more efficiently and helped every project succeed.  He was responsive when we ran into issues, and greeted every challenge with a sense of humor.  
Lushing is being nominated for his outstanding efforts to the project and community.  Lusheng has been an excellent team player and great asset to DCAE team. DCAE has been through major architecture changes since ONAP was launched and Lusheng has been instrumental in delivery of DCAE platform and services and successful transitions between ONAP releases. In R2, Lusheng led collaboration with members from Amdocs, Nokia, Tech-M and other ONAP partners to enable successful integration.  With his technical excellence, Lusheng has helped multiple other project, team members as well. Being among Top-10 code contributors is testament to his commitment and contributions made for ONAP community.
Highly respected community advocate and leader. His breadth of experience and passion for open source technologies lead to the deliver of a key innovation (k8s) that makes ONAP easily deployable and solves real world problems like delivering a production-grade service delivery and automation platform. 

Citizenship Award 

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:

(alphabetical by first name)

Simply, Brian was awesome helping to get the robot VNF demos running using OOM during the integration testing crunch.  The demos touch various different projects.
One of the busiest people on ONAP, participating on multiple project teams and subcommittees, working closely with release manager, Gildas, to ensure success of projects and meeting of milestones, and going the extra mile to ensure a successful release. She has taken on tasks such as release notes herself, opening up Jira to individual teams to help them get things completed or corrected, and was on day and night to support teams across time zones and countries.
Eric is very active to progress the community in an open way. Eric was behind the creation of openlab with 70+ users from 20 companies (vendor, operators and academic).
Helen Chen has been continuously and tirelessly pulling the cords together to help projects and use case teams successfully deliver the Beijing Release. To make this reality happen, Helen spent her energy around the clock to connect into various labs and help teams investigate issues, reports defects, integrate solutions  and reporting to the community, with a great deal of humor, the progress made.
Manoop as a Portal Project PTL supported other ONAP PTLs regarding the Portal's SDK. Mostly, the SDK support is provided to VID, Policy, AAI, SDC, MSB and CLI. Besides SDK support, he provided help for the pairwise integration with all the on-boarded applications on Portal which ensure the success of end to end integration test for ONAP Beijing release. He coordinated all the efforts required to integrate Portal's SDK with AAF and MUSIC, so that the VID, Policy and AAI applications using SDK can take advantage of the access management, resiliency and scalability features. He also collaborated with OOM team to resolve the deployment and ONAP access issues for a general ONAP user. In support of these activities he performed code reviews under MUSIC and OOM repos. To me he certainly represents the core value of what an open community should be
Marco was leading and performing both change management and scale out testing in parallel those last few months. Previously he was ensuring that the ONAP deployment (Heat) was stable so the different project teams could perform their pair-wise testing activities. He was one of our ONAP champions at the ONS North America event, performing live demos, demonstrating ONAP capabilities. Eager to help anybody, his availability and his team spirit have been unwavering.
Marcus spearheaded the HPA functional requirement testing efforts and was critical to getting HPA functional requirement delivered in the Beijing Release. Marcus spent endless hours and several sleepless nights testing and debugging HPA functionality across five separate ONAP projects. In order to get HPA tested, Marcus first had to ensure that the affected projects were working correctly in general. This entailed endless permutations of pairwise/integration testing and debugging across SO, Policy, AAI and Multi-Cloud projects. Marcus also stepped up and helped test a brand new ONAP project – OOF – that was key to making HPA real. If it were not for Marcus’s efforts, we would not have OOF and HPA as part of the Beijing release.
Besides being the lead of ONAP Logging project, Michael is also a true evangelist of DevOps, ONAP deployment on Kubernetes and as cloud native. Michael is the individual who provided much assistance to many, many others, in the form of education, guidance, bug fixes. Michael's behavior help to promote cooperation between members of other projects: (Portal, OOM, Integration and a dozen more) is exemplary.
During the Beijing release OOM introduced new Helm models of every ONAP component comprising thousands of files.  Not only did Mike define the generic model used for all of the ONAP components but he held multiple training sessions for the community and countless numbers of project-to-project eduction and debugging sessions to ensure that the Helm models faithfully represented the intentions of the project teams.  In many cases Mike created the models for the project teams. In other cases Mike guided the teams and then helped debug the Helm models - often on Kubernetes systems that he created for the teams to use. During all of this Mike remained helpful and cheerful even under the stress of overwhelming number of requests well past project deadlines.  During the integration phase Mike attended a large number of Integration team sessions and was always available on RocketChat to help. Mike is a shining example of how an open-source community can come together across company and geographic boundaries to achieve a common goal.
Pam has consistently worked to expand communications among Project teams.  In addition, Pam regularly vbolunteers to tak on new tasks which benefit the community in general, provides well thought out input during ONAP calls whether it is on PTL or TSC meetings and shares her thoughts on process improvements and lessons learned in a positive and constructive way.
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 tool chain and technical support needed to ensure accurate documentation. Among his many contributions during Beijing:
Troubleshooting a myriad of project level issues and questions related to the wiki, readthedocs, tool chain, etc.
Analyzing terminology errors and developing strategy for project teams to detect and correct without impacting code development or releases
Analyzing and developing methodologies for correcting ReStructred text warnings as well as linkcheck errors
Cleaning up / restructuring existing content to make it more consistent and accurate
Assisting the Release Manager (Gildas) and Project manager (Kenny) with many issues surrounding wiki and release content 
Coordinating the entire Beijing documentation branching process, including cherry picking project level documentation even on vacation to insure everything was correctly mapped
 
Rich has gone well above and beyond to ensure the success and effectiveness of ONAP documentation for Beijing.
Seshu has exhibited tremendous dedication and commitment in making the ONAP Beijing success by providing contributions across different projects. Besides the role of a PTL, Seshu is a member of the architecture, architecture tiger team and security sub committee.
He has helped to SDC in correcting the security vulnerabilities.
OOF team to have passed the pair wise testing milestone criteria on time.
Participated and helped the design and implementation of the functional requirements.
Volunteered SO as a pilot project to the security code scan and OOM (for the runtime) integration project.
Mentored and supported newbees of ONAP, as a result, under his leadership, SO team has code contributions from 14 companies and passed all the Milestones on time. 
As the VF-C PTL, Yang Yan managed the VF-C project very carefully and attentively, leading the project team to complete every milestones of the community on time. She is very attentive in helping others with community-related questions and solving issues with the team members. During Beijing Release, in the integrated testing and test phase, she took the sole responsibility for the VF-C code joint debugging and bug fixing alone, as the other core team members were not able to participate in community activities, and she was also responsible for coordinating and participating in the various testing work of CMCC Integration Lab for both VoLTE and vCPE verification testing, which set the basis for the timely delivery of Beijing and the continued success of the community.



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.

Nominees:

(alphabetically by project)

APPC


Close collaboration, good planning, and execution enabled the APPC team to overcome major obstacles and deliver on their commitments.
  • Started working 72 hour stability test in first sprint with Amsterdam; designed their own automated test suite using jmeter; ran 72 hour test multiple times on various releases as well as deployments (Heat and OOM)
  • First team to demo the APPC 72 hour test to Integration team; automated tests submitted to Gerrit so that others can use
  • Close collaboration with Integration to run ConfigScaleOut from DmaaP to APPC and VNF in prep for E2E use case test
  • Close Collaboration with OOM and SDNC on resiliency; successful partnership, working in an iterative fashion to achieve end goal
  • Provided documented instructions on setting up local developer environment to promote code coverage contribution
  • Provided Training on writing junits for new members joining the project
  • Provide a robust set of documentation on readthedocs
IntegrationThe Integration Team has been playing a critical and challenging role for the successful release of ONAP Beijing. Effectively they are the last runner in the release relay race and almost always trying to make up time when other trams miss their schedules. They have been working closely with almost all other projects on maintaining and coordinating of project pair-wise testing, lab resources and environment, overcoming a number of challenges through the release: network connectivity issues, slowness of Jenkins, unstable hardware environment, etc. to make sure the success ONAP release as a whole. At Beijing release, they accomplished several major achievements:
  • Improved CI process: finished automating vFW / vDNS and have them hooded with Jenkins systems running continuously 7/24.
  • Re-implemented Amsterdam use cases with the new APIs and some flow changes: vCPE, VoLTE
  • Coordinating and participating new requirements integration, Change Management, manual scaling, HPA.
  • Finished the 72 hours stability testing with both HEAT and OOM deployment, and resilience testing with OOM. Many weekend and night hours added by the team to do so.

OOM

WINNER

Moving from "experimental" to a core component of ONAP, the OOM project has been instrumental for the Beijing Release becoming one of the cornerstones regarding S3P requirements (resiliency). In true agile fashion, the OOM team delivered a huge number of stories, tasks and bug fixes (http://onap.readthedocs.io/en/latest/submodules/oom.git/docs/release-notes.html),  to deliver ONAP on Kubernetes. All while providing almost daily education and support to the development and integration teams, to meet S3P goals for the Beijing release. Issues worked through included a Kubernetes and Helm version change, a radical new way of deploying ONAP using a helm chart umbrella chart providing the ability to upgrade, rollback, dynamically change configuration.  The project was on time, had usable documentation on RTD, the code reviews process was thorough yet not to restrictive (Design patterns and quality were enforced by the committers).  The support provided to the other projects during last minute patches and bugs (AAF, OOF, NBI, MUSIC etc) to meet deadlines in my opinion was above and beyond the norm.  In many instances, the OOM team cherry picked patches from other teams and addresses issues themselves in the interest of time.
Portal PlatformThe team has collaborated with AAF, OOM and MUSIC teams to try new integration aspects to pave the path for the other projects. The Portal Platform Project team has met all the release milestones on time and always reviewed with the release manager, architecture and security committees ahead of time to save from the last minute changes. 
CLAMPThe CLAMP Team served as a model for other projects. They were the pilot team to assess the CII Badging, providing their feedback to the security sub-committee but also providing guidelines to the other project teams concerning the CII form. They were helping several project teams concerning their license and security issues. They were reviewing and were updating the Helm Charts used by OOM for the Music and the OPTF projects. They have also implemented a new capability, the CLAMP Dashboard - with one or two clicks, Operators should be able to get the most critical KPIs and reports of Running Control Loops. They met all the milestone criteria in a timely manner. Ron Shacham, one of the CLAMP team members, drove all the control loop testing on the different use cases, building effective partnership with different project teams. Finally they performed full ONAP OOM Deployment (except VF-C, Usecase UI) based on the Beijing release note, providing feedback and improvement suggestion to the ONAP Community.
VF-CVF-C is the main part of the integration between the former OpenECOMP and OPEN-O efforts. VF-C brings the ETSI NFVO and GVNFM architecture/features into ONAP with high-quality code, which serves to make ONAP a more logical and acceptable choice for CSP. In order to better integrate with other ONAP projects, VF-C completed integration and testing with 10 projects, delivering 17th components. All the milestones completed on time. VF-C aligned R2 unified data model and as the key component, made outstanding contributions to support integration testing.
VNFSDKWhen it comes to achievement in hitting the milestones and a role model for other to get inspiration from, without a doubt VNFSDK is the exemplary project that deserves the award in this category. From a process perspective, the VNFSDK project team has been responding ahead of time and without needing to be asked twice for any items. More importantly, the VNFSDK project team constantly monitored what really mattered to make an Agile Delivery: CSIT, vulnerability fixing, Sanity Check, Code Coverage and the whole enchilada that show what a great project team they are. Furthermore, from a functionality perspective, the team delivered the significant contribution in the Beijing Release to certify VNFs in the whole ONAP ecosystem, thus is helping operators with their time to market strategy.

Project Innovation Award 

Presented to the Project which delivered a new compelling feature or capability in ONAP (not originally delivered in Amsterdam, Open-O or Ecomp) that has significantly impacted ONAP in one or more areas including but not limited to architecture, integration, SDOs or security. 

Nominees:

(alphabetically by project)


Ryan and Scott drove a critical security feature with AAF team to enable securing web based API access via ODL, without need to modify any ODL jars. Through their work, Ryan writing the requirements to AAF team and working on designed and execution, and Scott assisting with the testing, this key security feature would not have been possible. Now API access via ODL APIDOC Explorer is authorized via AAF
CLAMP (dashboard)Service assurance and closed loop monitoring is one of the target goals of ONAP, the Dashboard as part of Beijing is a significant step towards this goal.
External APIThis project introduces a new component (NBI) to facilitate integration with existing BSS or IT application. It is fully aligned with TMF API and was designed with strong collaboration with MEF. It outlines how it is possible to use ONAP platform using standard API defined by various organizations.
Modeling TeamONAP Modeling Team has made a  tremendous contribution to the ONAP project by providing unified Information Model Spec and corresponding Data Model Implementation. They coordinated with multiple standard organizations (ETSI/MEF/IETF/ONF) and published the model that fulfills the requirements from usecases/S3P.  All the while they accomplished several major achievements:
  • Published the unified Resource Model Specification.
  • Contributed to SDC to support resource design and on-boarding by using the unified model.
  • Validated the VoLTE/vCPE(WIP) usecase by using the unified model with the SDC, UUI, SO, AAI, VFC and MultiCloud projects.
MUSIC

MUSIC is a novel state management service specifically tailored for multi-site geo-distributed replication through flexible, fine-grained consistency  with a rich suite of recipes that each ONAP component/microservice can simply configure and use for their state-management needs. MUSIC is currently being used for multi-site state management by the Homing and Allocation Service (HAS) that is part of OOF and the ONAP Portal.

In terms of impact, MUSIC is a fundamental service that helps ONAP components to achieve 5 9s of availability on 3 9s or lower software, by enabling state management across geo-distributed sites in a reliable, scalable, highly available and efficient manner.

Portal PlatformThe Portal Project made innovative contributions to ONAP through seamless integration with MUSIC and AAF which most of the other ONAP projects have not integrated yet. AAF for access managment and MUSIC for resiliency and scalability are integrated into Portal's SDK. Partnering applications like Policy, VID, AAI, SDC can now take advantage of using these features. The SDK framework is designed in such a way that these features are pluggable, meaning the applications can choose to use them or not after upgrading to the latest SDK. This has significantly impacted ONAP under integration area by exposing such features as out-of-box features in SDK.

APPC

WINNER

The APPC Team played a leadership role for VNF scale out use case. They have also developed a Self Serve Design approach: Controller Design Tool. This tool supports VNF Self-Service Onboarding for all API actions. The team demo'd to the Integration team first their 72 hour stability test run. They submitted jmeters to deployment project. They were leading with SDNC in the OOM support and Resiliency testing. They delivered ODL in last sprint in spite of getting it in last sprint from CCSDK. Finally they drove the Application Authorization framework project, wrote the story to that project and led the integration activities. Lots of good stuff done by a small project team !
VNFSDK - (Dovetail Integration)In the Beijing release, the VNFSDK team integrated with OPNFV's Dovetail testing framework, which is used for the OPNFV Verified Program.  The team demonstrated how we can use VNFSDK validation tools to test VNFs and report results back to LF back-end databases.  This project demonstrates a model for cross-community work. It also sets the stage for VNF compliance testing under the LFN umbrella following the Casablanca release.  

Marketing Award 

Presented to the individual who provided the most support to various Marketing and PR teams, and generated and/or supported development of documentation, videos, tutorials, press/analyst interviews, webinars, etc.

Nominees:

(alphabetically by first name)

Chris assists in the ONAP PR and marketing efforts on an almost constant basis, supporting briefings and helping with messaging. In addition to helping ensure that ONAP is always shown in the best light, he also assists on-boarding to new LFN Member companies to help get them up to speed on ONAP.
Together as a team, Martial and Christophe represented ONAP in EMEA by participating to the 2018 FOSDEM - Free and open source software developers' European meeting. They have also developed several webinars, videos, tutorials to demonstrate closed loops capabilities and the CLAMP dashboard (With One or Two clicks, Operators should be able to get the most critical KPIs and reports of Running Control Loops). 
He is very active to promote ONAP within the projet in the marketing committee and during various events (various presentations during ONS Summit). He also proposed the first LFN case study with Orange: https://www.linuxfoundation.org/lfn-resource/case-study-lf-networking-lfn-projects-power-next-generation-orange-networks/
Marco deserves to be recgonoized for representing ONAP so well at the ONS conference in Los Angeles.  Marco has a broad understanding of the ONAP platform and helps where ever he can.
May has been great about helping to organize the China PR/Marketing working group and in to getting things translated and disseminated in-region. She has also assisted the Modeling team in coordinating events.




Code Contribution Award 

Nominees are automatically chosen from the Top-10 contributors of merged code.  The Community will then vote for the individual they feel produced the highest quality code.

Nominees:

(alphabetically by first name)

Dan Timoney WINNER
Fu Jinhua
Gary Wu
Kanagaraj Manickam
Lusheng Ji
Sébastien Determe
Subhash Kumar Singh
Venkata Harish Kajur
Yun Huang
Yunlong Ying


  • No labels