@Yan Yang

Yan Yang deeply participated in OVP from 2019, and contributed the design and development of VNF validation which has been applied to commercial VNF testing and certification in OVP.

At the same time, she proposed the end-to-end automation testing solution which is the first time applying ONAP to test scenario and actively promoted the solution in OVP.

In ONAP Gulin release, she proposed the automation enhancement requirements of ONAP components and completed the whole functions delivery, meanwhile actively supported the ETSI Alignment team to provide effective guidance and suggestions.

Yan Yang actively promotes the advanced design concepts of ONAP, promotes cross-team, cross-project, and cross-organization cooperation, and has made outstanding contributions to the innovation and development of ONAP.

@Zhang Min

Min Zhang led the CMCC team for E2E Network slicing Use Case development since Frankfurt. In Guilin Release, she was personally involved in the proposal discussion of the enhanced E2E Network slicing Use Case, the requirement analysis of each project, SDC template design, SO related development,  end to end integration test etc., and led the team to the delivery of the complete template design of 3 domain, improved the NSMF/NSMF Adapter framework and the model design of AAI, which are at the core to the demonstration which initially realizes the solution of connection with the External Core NSSMF, internal Trans NSSMF, and External RAN NSSMF. 

@Krzysztof Opasiak

Krzysztof is a key player of the community. He has a strong Free software background. He is a technical leader. He is able to fix tricky issues in lots of projects, significantly improve the overall quality of the installation to make the cloudnativeness dream possible and move the process more on an Open Source track. He is inspiring and benevolent.

@Sylvain Desbureaux

Sylvain became the OOM PTL in Guilin. He is the main architect of the End to End CI/CD mechanism put in place in daily/weekly and gating chains. This mechanism is a must have to ensure the sustainability of the ONAP solution and to promote it soon as a Production ready solution... He is also working very hard the improve the cloudnativeness of the solution (service mesh, storage class). Using k8s is not enough, lots of complex work is needed to adapt ONAP architecture to k8s and leverage the powerful feature of the infrastructure solution. The community globally underestimated this effort but thanks to him and the OOM project we are still on track.

Last but not least, Sylvain is the initiator of the pythonsdk framework, He developed all the SDC part and put in place the quality rules to ensure the sustainability of the framework.

@Michał Jagiełło

Michal is the main developer of the onap pythonsdk framework. Thanks to his great python skills he was able to finalize the framework that was integrated in CI/CD chain in guilin and replaced the old deprecated onap_tests. Michal helped a lot the new developers jumping into this framework, he helped also to create and review the new tests created in pythonsdk-tests, an ONAP repo hosting the tests run in CI consuming the SDK. He created several use cases. Moreover he helped the seccom to improve the security linked to the docker build chain.

@Jack Lucas

Jack has been active DCAE committer and contributor since ONAP inception, his contribution for DCAE project has been instrumental for delivering several key features and initiatives in recent ONAP releases. In the middle of Guilin release development,  Jack opted for (unplanned) retirement from AT&T however his commitment and resolve to ONAP was un-paralleled - he continued supporting Guilin DCAE commitments made early on and delivered several features on-time,  these include features such as dynamic certificate generation/support for DCAE service, blueprint migration, healthcheck optimization etc.

His expertise on DCAE platform and openness to support the community has also enabled new members contribution smoother. Besides contributions to DCAE project, Jack has also been active contributor into OOM project and assisting adoption/migration of new standards, cloudnative approach ONAP is leaning towards.

Also to highlight, Jack has been supporting ONAP as an independent contributor (without affiliation to any company/sponsors) for last several months. His efforts and dedication for ONAP is extremely commendable.

@Pamela Dragosh

Pam has been leading the ONAP Control Loop Subcommittee since its creation in 2018, advancing significantly the Self-Serve, Model Driven Service Assurance Automation, promoting diversity, welcoming any contributor and any idea. Have a look at the Control Loop Subcommittee Accomplishments from Beijing 2018 - Guilin 2021

In addition, she was serving the ONAP Community as the Policy Framework Project Team Lead from ONAP inception until July 2020, with 4985 commits performed by 108 authors from 8 companies.

@Yuanhong Deng 

Deng Yuanhong is responsible for the development and management of VFC and Modeling/etsicatalog projects. She supported ETSI-Alignment  requirement consecutively for multiple releases; organized over 10+ colleagues to actively participate in the Certified ONAP Professional (COP) exam development; and participated in the 2020 LFN Mentorship Project as a mentor, making positive contributions to the expansion of community influence and community development.

@Jorge Hernandez

Jorge has been a key contributor in the Policy Framework team for multiple activities spanning different areas like OOM, Integration, Security, certificates, documents, lab maintenance, release verification and many more.

Together with that, he is an active developer and mentor in the Policy Framework and other projects in ONAP since the very beginning with an “always ready to help” attitude. His expertise in the drools policy engine has helped the community in fixing critical issues across various use cases. He worked very closely with the OOM and integration teams in various improvements and refactoring for improving the installation and robustness of the platform as a whole.

Jorge preempts and solves problems, manages infrastructure, and deals with issues in a calm, quiet, and professional manner and he makes a huge contribution to the ONAP community.

He has also participated in demo and tutorial sessions during LF community events to spread the knowledge to the community.

@Andreas Geißler

Andreas Geissler is a well known actor of the community. He is involved in the documentation project and the integration project. That is why he is dealing with lots of different projects. In Guilin, he also took part to the onap pythonsdk development and he is also reporting results from CI/CD chains setup in DT environement. In rocket chat, on Jira or on the mailing lists he spent a significant part of his time to help the other ONAP contributors.

@Lasse Kaihlavirta

Lasse worked on the refactoring of the CSIT tests. As such he has to deal with all the projects. The task is complex and difficult but the goal is very important. Functional tests are mandatory to ensure the sustainability of the system. The tests shall provide feedback as soon as possible to the developer and not be run (and forgotten) in a standlone ghost system. Lasse analyzed the current situation and suggested an evolution which could be key for the overall quality of ONAP in a near future, he developed a PoC in Guilin and strated discussing with other project in order to bring back the test closer to the code, redesign the build chain in order to build docker on patch submission. He also performed a big cleanup (some fully deprecated very old tests were still run daily - CI resources were lost and it would have last until the end of ONAP without him..). Lasse was promoted as ci-management committer in Guilin.

@ChrisC

Christophe is the SDC PTL but he is also very active an integration. He is helping a lot on all the support channels. He has now a great experience in ONAP and a long history on the different projects which are precious to help the community. He is always available and benevolent. 

@Tony Hansen

Tony has been a key contributor for ONAP. Tony’s wealth of experience and security knowledge has enabled to support different roles interchangeable. As a SECCOM member, Tony has driven and supported many project CII badging improvement which has helped to promote ONAP visibility among LF hosted project. With Tony guidance, several project have attained "Silver", with considerable progress towards "Gold" level in Guilin release. As DCAE committer, Tony has spent lot of time working meticulously with contributors to improve code quality and standard through reviews. During Guilin release, he  also helped the DCAE python project complaince for 3.x and sonar coverage improvements.

@xu ran

As the PTL of UUI project, Ran worked hard in optimizing the quality of UUI codes and improve the usability of the project and improving the stability and security of UUI project, improve the test codes coverage, update the HTTPS certification and update to java 11. In the same time, as UUI serves as the key entrance for enabling new cases, she supported the development of

1) E2E slicing usecase (including support the whole flow of E2E slicing usecase, enable the transport of AN, CN and TN., and support the joint-debugging with other projects, review all the committed codes of UUI and UUI-server and merge those codes and provide the related document and release notes to support the of Guilin release). 

2) Guide China Telecom to finish the POC usecase of IBN. Offer help  in the area of establishing project and development

@Lei Huang (Unlicensed)

As a member and chairman of EUAG during ONAP Guilin release, Lei Huang has made great contributions in building closer relationship between EUAG and ONAP community. In this process, Lei has actively provided CSPs top priorities to ONAP community as release planning guide, and actively explored the ONAP consumption model from the perspective of operators through survey investigation and analysis, relevant white paper, etc., as well as provided industry recommendations to LFN and ONAP community for reference from operators’ perspective. As a communication bridge between EUAG and ONAP community,

she will continue to support the provision of operators’ release work plans and top priorities for ONAP community, promote the implementation of operator requirements in ONAP release, and further explore the deeper cooperation between EUAG and ONAP community in future, as well as provide broader industry ecological recommendations in subsequent 5G and NFV testing white papers.

@Paweł Wieczorek

Pawel developed lots of security tests introduced in Frankfurt and improved in Guilin. He transformed the seccom requirements into tests executable in daily/weekly chains. He created the nonssl security check as well as the version test tracking the olf python2.7 and java8 versions. Pawel is a skilled Go and python developer. He integrated thes tests quickly into the complex integration chains.

@Bartek Grzybowski

Bartek is involved in integration project. He is systematically adding robust verification jobs in any new integration repository (integration but also simulators, use cases) in order to ensure an automated verification process. He introduced coala as a multi language linters. He was granted as ci-management committer and is very responsive on the support rocket chat channel.

DCAE Project 

DCAE is one of largest project in ONAP comprising  30+ repository and 40+ active components (microservices/containers) and was approved to “Mature” state in Guilin by TSC members. Following are some key updates done w.r.t to S3P improvements inaddition to supporting multiple Usecases/Functional requirements in-parallel (DCAE was one of high impact project for Guilin release - Guilin Impact View per Component)

• Security : Java 11 and Python 3.x migration (identified as TSC MUST-HAVE) presented a huge challenge due to number of components impacted. However we were successful in migrating several DCAE components in Guilin release. 

Following components were migrated to Java11 during Guilin release
DCAE Services:  RESTConf Collector, PM-Mapper,  DataFileCollector, VES-Adapter, SON-Handler,  Tca-gen2, Datalake handler (feeder)
DCAE Platform: InventoryAPI, ServiceChange-handler, Dashboard, MOD-runtime api, Bp-generator (DCAE-MOD)
*These were addition to VESCollector, HV-VES Collector, PRH, SDK upgraded in Frankfurt.

Below components were migrated to Python 3.x in Guilin
DCAE Platform: Policy-Hander,  ConfigBindingService, Policy-library (utils), MOD-Distributor API, MOD-Onboarding API
DCAE Services: Heartbeat MS, PMSH Service

Due to number of components involved, the migration was massive effort and coorindated and supported by different companies and community members (notably from Nokia, Ericsson, AT&T, Huawei, Wipro, ChinaMobile)   

• Unit test coverage requirements has also been adhered strongly for all existing and new components. Cover coverage for all DCAE components on avg is >70% - https://sonarcloud.io/organizations/onap/projects?search=dcaegen2&sort=name (total LOC for active components > 100K)

• Performance test improvements: Completed performance test for VESCollector &  HV-VES in this release (these are inaddition to DataFile Collector, PM-Mapper done in earlier release). Reports of performance testing is documented below
  VES Collector Performance Test
  HV-VES Performance Test
  PM-Mapper performance baseline
  Datafile Collector (DFC) performance baseline results

• All security vulnerabilities identified by SECCOM (at M1) has been resolved and delivered part of Guilin release.

• Stability and Security test improvements :  Number of DCAE components test (VES, PRH, HV_VES, Bulk-PM Flow) has been included under Smoke test and security test in Guilin release which are executed part of gating/daily job  (https://logs.onap.org/onap-integration/daily/onap_daily_pod4_master/) to verify usecase/flows for ONAP

Policy Framework Project

Policy Framework is one of the core project in ONAP to enable multiple automation & orchestration use cases. Being such a critical project, the team has always kept S3P (Stability, Security, Scalability & Performance) improvement & alignment as one of the top priority whether being upgrade to JDK 11, python 3, keeping on top of license & security scans, SECCOM issues, monitoring the CLM jobs etc. In fact in some of the areas (ex - JDK 11) we were the one’s to pioneer and take a lead in the work.

In Guilin release, we completed all the TSC must have requirements related to S3P. Along with additional requirements to improve the platform like returning non-zero exit codes in case of errors, ability for logging to STDOUT, certificate handling, improved health check etc. To strive for best quality deliverables, we have been always on top of sonar issues and maintaining above 80% code coverage. With some repos as high as 95% coverage.

We were also approved as “Mature” project in ONAP after proposal being reviewed by respective committees and TSC. 

In terms of maintaining S3P work release over release, we have a very good structure in place to keep track of test artifacts, documenting the test plan, executing the actual tests & finally documenting the results. Please find below the details:

1. Maintaining the test artifacts : We have created a maven module called “testsuites” in each of the policy framework run time component. And all the artifacts (JMeter test plan, scripts, docker compose etc.) are stored in the module. The same is updated before every release. Below are the links for Guilin release artifacts.
   
   Lifecycle API - https://github.com/onap/policy-api/tree/guilin/testsuites
   PAP - https://github.com/onap/policy-pap/tree/guilin/testsuites
   Drools-PDP - https://github.com/onap/policy-drools-applications/tree/guilin/testsuites
   Apex-PDP - https://github.com/onap/policy-apex-pdp/tree/guilin/testsuites
   Xacml-PDP - https://github.com/onap/policy-xacml-pdp/tree/guilin/testsuites 
   Policy Distribution - https://github.com/onap/policy-distribution/tree/guilin/testsuites
   
   
   

2. Documenting the test plan : We have created detailed document to explain how to setup & execute S3P tests for each policy framework run time component. The same is updated before every release. Below are the links for Guilin release test plan documents.
   
   Lifecycle API - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/api-s3p.html
   PAP - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/pap-s3p.html
   Drools-PDP - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/drools-s3p.html
   Apex-PDP - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/apex-s3p.html
   Xacml-PDP - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/xacml-s3p.html 
   Policy Distribution - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/distribution-s3p.html
   
   
   

3. Execution of the tests : The test plan is executed in Windriver & Nordix labs with latest version of ONAP components installed before every release.

4. Store the S3P results : We store the results of S3P testing release over release in the official ONAP docs for the community to have easy access and understand the improvements. Below are the links for Guilin release test results.
   
   Lifecycle API - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/api-s3p.html#test-results
   PAP - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/pap-s3p.html#test-results
   Drools-PDP - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/drools-s3p.html#stability-test-of-policy-pdp-d
   Apex-PDP - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/apex-s3p.html#stability-test-result
   Xacml-PDP - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/xacml-s3p.html#id2
   Policy Distribution - https://docs.onap.org/projects/onap-policy-parent/en/guilin/development/devtools/distribution-s3p.html#test-results
   
   

On top of above, we have done significant refactoring of OOM helm charts for Policy Framework in Guilin release to make the installation more robust & resilient. Thereby improving the overall charts and aligning to the global standards set by the OOM team.

Integration Project

The Integration Team has significantly improved the gating process, testing sets, and security checks and have leveraged Xtesting from OPNFV:

• Guilin Docker version follow-up

• Guilin Readiness dashboard

• Guilin Integration Non functional Use Cases

• They moved pythonsdk-tests leveraging the new onapsdk.

They also have organised an Integration Hacktoberfest 2020

They have presented a lot of knowledge share, best practices during the LFN DDF events, PTL calls, etc

They have also provided a lot of visibility, metrics about the Guilin Release readiness, giving a taste of the SW quality provided by the different project teams.

Control Loop automation using ONAP      -   @Ram Krishna Verma,  @Former user (Deleted) 

Shared and Non shared Slice order processing by core NSSMF -   @Thamlur Raju (Unlicensed), @Vamshi Namilikonda, @Malinconico Aniello Paolo, @Former user (Deleted), @Aleem Raja, @Milind Jalwadi (Unlicensed)

E2E Network Slicing demo based on Guilin deliverables -  @Zhang Min, @HeTengjiao, @LUKAI, @Henry Yu, @LIN MENG, @wangyaoguang, @Swaminathan Seetharaman

Recognizing Integration team member who are supporting the Integration PTL to re-enforce the importance of Integration activities:

@Paweł Wieczorek,  @Krzysztof Kuzmicki ,  @Marcin Przybysz

Recognizing the people who have the most improved CSIT Tests:

@Former user (Deleted), @Ajay Deep Singh, @James Hahn

@Dan Timoney

@James Hahn

@Morgan Richomme