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). 

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.

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 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.

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.