DCAE R4 Release Sign-Off Milestone Checklist

Owned by Vijay Kumar
Last updated: Jun 05, 2019
3 min read

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 Area

Checkpoint

Yes/No

Evidences

How to?

Practice Area

Checkpoint

Yes/No

Evidences

How to?

Product Management

Are committed Product Backlog Stories been coded and marked as "Closed" in Jira?

Yes

completed (100)

Getting issues...

Not completed (0)

Getting issues...



Note: DCAE POC Stories are not tracked as release deliverable hence excluded via label



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

IN-progress

Except 1 documentation task (in-progress)



Getting issues...



Provide the project features list under the form of a bulleted list.

Yes

  • New microservices suite of collectors/event processors/analytics:

    • Collectors: RESTConf collector

    • Event Processors: VESMapper, PM-Mapper, BBS-EventProcesor

    • Analytics/RCA: SON-Handler,Heartbeat

  • Common SDK for DCAE components

  • Multisite K8S cluster deployment support for DCAE services (via K8S plugin)

  • Support helm chart deployment in DCAE using new Helm cloudify plugin

  • DCAE Healthcheck enhancement

  • Dynamic AAF based topic provisioning support through Dmaap cloudify plugin

  • Dashboard Integration (UI for deployment/verification)

  • PolicyHandler Enhancement to support new Policy Lifecycle API’s

  • Blueprint generator tool to simplify deployment artifact creation

  • DCAE component enhancements for security, logging, resilience enhancements



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



DCAE had number of stretch-goals for Dublin, most of which were delivered, except TCA-gen2. This was a new analytics service identified among stretch goal  - intended to replace TCA-cdap version. This had to be descoped during M4 due to resource/time constraint for Dublin.  This has no impact to R4 or regression usecases

PNDA integration was another stretch goal, which dint have much progress in Dublin due to resource constraint. Community support will be needed to enable applications deployment into PNDA and seemless integration with rest of DCAE/ONAP components.



Release Management

Have all issues pertaining to FOSS been addressed?

Yes





Have all findings from previous milestones been addressed?

Yes





Development

Are all the Jenkins jobs successfully passed (verify + merge jobs)?

Yes

As of 6/5 PM - https://jenkins.onap.org/view/dcaegen2/

https://jenkins.onap.org/view/Merge-Jobs/

Are all binaries available in Nexus Release repository?

Yes

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



Are all Docker images available In Nexus?

Yes

https://nexus3.onap.org/#browse/browse:docker.release (search for dcaegen2)





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

Yes

https://git.onap.org/integration/tree/version-manifest/src/main/resources/docker-manifest-staging.csv



https://git.onap.org/integration/tree/version-manifest/src/main/resources/java-manifest.csv



OOM to Tag Release + Version in Helm Chart

Yes





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

Yes (for Dublin branch)

All Dublin CSIT are passing https://jenkins.onap.org/view/dcaegen2/

Following two master CSIT are failing (appears transient issue - to be checked further)

dcaegen2-master-csit-prh-testsuites

dcaegen2-collectors-restconf-master-csit-testsuites

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

https://jenkins.onap.org/view/dcaegen2/

Goal is to ensure the latest project commit has not broken the Integration Daily Build 

Has the project passed the Integration Sanity Tests

Yes



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?

Yes

DCAE Pair Wise Testing for Dublin Release



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

In-progress

#1 and #2 are completed, single Jira on #2 in-progress

Project doc - https://docs.onap.org/en/dublin/submodules/dcaegen2.git/docs/index.html

Release Notes - https://docs.onap.org/en/dublin/submodules/dcaegen2.git/docs/sections/release-notes.html

One task on Doc updates WIP (DCAEGEN2-1593 )



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