Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Nominated CandidateReason for Nomination
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

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.

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

DCAE is one of largest project in ONAP containing 30comprising  30+ repository and 40+ active components (independent servicemicroservices/containers) . For Guilin release, DCAE had one biggest challenge to comply with Java 11 and Python 3.7 support. In guilin DCAE team completed java 11 migration for several services and platform components listed below - 

  • RESTConf Collector  (DCAE-Service)
  • PM-Mapper (DCAE-Service)
  • DataFileCollector (DCAE-Service)
  • VES-Adapter (DCAE-Service)
  • SON-Handler (DCAE-Service)
  • Tca-gen2(DCAE-Service)
  • Datalake handler (feeder)
  • InventoryAPI  (DCAE-platform)
  • ServiceChange-handler (DCAE-platform)
  • Dashboard (DCAE-platform)
  • MOD-runtime api (DCAE-MOD)
  • 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

    El-Alto

    Frankfurt.

    Due to number of components involved, the migration was massive effort and was

    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)

    Similar effort was also carrried out for Python 3.x migration. Following DCAE components were migrated to be complaint.

    • Policy-Hander (DCAE-platform)
    • ConfigBindingService (DCAE-platform)
    • Heartbeat MS (DCAE-Service)
    • Policy-library (utils)
    • MOD-Distributor API (DCAE-MOD)
    • MOD-Onboarding API (DCAE-MOD)
    • PMSH Service (DCAE-Service)

    Besides java and python migration, DCAE team also completed performance test for several DCAE MS such as VESCollector, HV-VES, DataFile Collector, PM-Mapper during Guilin releaseReports of performance testing is available below

    Inaddition all security vulnerabilities identified by SECCOM during Guilin M1 were also  resolved across DCAE components.

       


    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:

    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.

    ...