Versions Compared

Key

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

...

Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre committed Product Backlog Stories been coded and marked as "Done" in Jira?Yes

Jira
serverONAP JIRA
jqlQueryproject = POLICY AND issuetype = Story AND status = Closed AND resolution = Done AND fixVersion = "Casablanca Release"
counttrue
serverId425b2b0a-557c-3c0c-b515-579789cceedb


Are all tasks associated with committed Product Backlog Stories been marked as "Done" in Jira?Yes

Jira
serverONAP JIRA
jqlQueryproject = POLICY AND issuetype = Sub-task AND status = Closed AND fixVersion = "Casablanca Release"
counttrue
serverId425b2b0a-557c-3c0c-b515-579789cceedb


Provide the project features list under the form of a bulleted list.Yes
  • The policy team introduced a new application into the framework that provides integration of the Service Distribution Notifications from SDC to Policy. S3P Performance and 72 hours stability performed.
  • The policy team established AAF Root Certificate for HTTPS communication and CADI/AAF integration into the
    MVP applications. In addition, many java dependencies were upgraded to clear CLM security issues.

  • Enhancements were made to support Scale Out Use Case to enforce new guard policies and updated SO and A&AI APIs.

  • A new Apex PDP engine was ingested into the platform. S3P Performance, Resiliency and 72 hour performed.
  • The policy team made enhancements to the Drools PDP to further support S3P Performance.

  • POC support work for Control Loop Coordination Policies

  • Policy support for HPA, CCVPN and 5G OOF PCI Use Case was developed.

Summarize any functionalities that were planned at Release planning and not delivered at Release Sign-Off

Yes
  • The team worked on Spike's for re-building the distribution of policies to PDP engines.
  • S3P Resiliency for the new Policy SDC Distribution Application was not done.
  • Need to add https and CADI/AAF to the Policy SDC Distribution Application and the Apex PDP Engine.

Release ManagementHave all issues pertaining to FOSS been addressed?Yes

Have all findings from previous milestones been addressed?Yes

DevelopmentAre all the Jenkins jobs successfully passed (verify + merge jobs)?YesNOTE: Verify/Merge jobs are only for master branch. Beijing branch will not be instituted unless a maintenance release is necessary.

Are all binaries available in Nexus Release repository?Yes

https://nexus.onap.org/content/repositories/releases/org/onap/policy/



Are all Docker images available In Nexus?Yes



Are the Java and Docker manifest updated with the same version as in Nexus Release repository?Yes

Integration and Testing

Have all CSIT Use Cases (created by each project team) passed?Yes
Goal is to incease our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs
Has the project code successfully passed the Daily Build process?Yes
Goal is to ensure the latest project commit has not broken the Integration Daily Build 

Has the project done the integration testing with related dependent projects?

Yes

Documentation

Has your team contributed and completed work in the following documentations in ReadTheDocs:

  1. Release Notes
  2. Project Documentation
Yes

ReadTheDocs Release Notes:

https://onap.readthedocs.io/en/casablanca/submodules/policy/engine.git/docs/release-notes.html

ReadTheDocs Project Documentation:

https://onap.readthedocs.io/en/casablanca/submodules/policy/engine.git/docs/index.html

https://onap.readthedocs.io/en/casablanca/submodules/policy/apex-pdp.git/docs/index.html

https://onap.readthedocs.io/en/casablanca/submodules/policy/distribution.git/docs/index.html