DRAFT PROPOSAL FOR COMMENTS

The following items are expected to be completed for the project to Pass  Release Sign-Off Milestone.

Release Sign-Off Milestone overview is available in wiki.


Usage

  1. Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
  2. Fill out the Yes/No column
  3. Provide link to evidence (when necessary)
Practice AreaCheckpointYes/NoEvidencesHow to?
Product ManagementAre committed Product Backlog Stories been coded and marked as "Closed" in Jira?

Yes for OOM.

For the offline installer sub project, stories are remaining open as per discussion with Jim on acceptable exceptions. These stories will be delivered independently of Dublin sign-off.

T Key Summary Assignee Reporter P Status Resolution Created Updated Due
Loading...
Refresh


Are all tasks associated with committed Product Backlog Stories been marked as "Closed" in Jira?YesSee above.
Provide the project features list under the form of a bulleted list.YesRelease notes up for review and to be merge d shortly: https://gerrit.onap.org/r/#/c/oom/+/89388/

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

Yes

Deferred to El Alto

  • Full integration of an Ingress Controller for Northbound access control and reduction of NodePorts
  • Automatic upgrade support for SDC, SDNC
  • Database Consolidation for more project teams (only SDC, A&AI, SDNC, SO delivered as PoC)
  • Helm Chart ownership transfer for more projects (only A&AI was delivered as PoC)

Release ManagementHave all issues pertaining to FOSS been addressed?N/A

Have all findings from previous milestones been addressed?Yes

DevelopmentAre all the Jenkins jobs successfully passed (verify + merge jobs)?Yeshttps://jenkins.onap.org/view/oom/job/oom-master-merge-helm/https://jenkins.onap.org/view/Merge-Jobs/
Are all binaries available in Nexus Release repository?Yes

There are Helm Chart artifacts in the Staging repo in Nexus:

https://nexus.onap.org/content/sites/oom-helm-staging/master/


Once the Dublin branch is cut for OOM (awaiting sign off from Integration), artifacts will move to https://nexus.onap.org/content/sites/oom-helm-release/4.0.0-ONAP/

This is a manual LF initiated activity.


Are all Docker images available In Nexus?N/A

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

OOM to Tag Release + Version in Helm ChartN/A

Integration and Testing

Have all CSIT Use Cases (created by each project team) passed?


It should include at least 1 CSIT that will be run on


Lab-xxx-OOM-Daily Jenkins Job

N/A
Goal is to increase our confidence the latest commit did not break the major functionality. Jenkins CSIT Jobs
Has the project code successfully passed the Daily Build process?N/A
Goal is to ensure the latest project commit has not broken the Integration Daily Build 
Has the project passed the Integration Sanity TestsN/A

Integration sanity tests in Dublin Release cover:

  • ONAP deployment
  • All components health check
  • VNF onboarding and service creation for vFW use case
  • Model distribution for vFW
  • vFW instantiation
  • vFW closed loop
  • vFW deletion

No test failure reported on http://onapci.org/grafana/d/8cGRqBOmz/daily-summary?orgId=1

No Integration Blocking Issue with no workaround: Dublin Release Integration Test Blocking Issues

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

N/A

Documentation

Has your team completed (reviewed, submitted and cherry picked) all documentation planned for the Dublin Release?

  1. Release Notes
  2. Project Documentation
  3. No remaining Documentation tickets
Yes

JIRA Query

project != "Sandbox Project" AND project != "ONAP TSC" AND project != CI-Management AND (labels=Documentation OR project=Documentation) AND status != Closed ORDER BY fixVersion ASC, status DESC, priority DESC, updated DESC