Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 9 Next »

The following items are expected to be completed for the project to Pass the M3 API Freeze Milestone.

M3 Release Architecture 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/NoEvidencesNote
Architecture


Has the Project team reviewed the APIs with the Architecture Committee (ARC)?YPresented during ARC meeting on 08/22 10AM EDT


Is there a plan to address the findings the API review?YDiscussion during ARC call. Decision: waiting for integration team decision on ONAP deployment plan.The most concerning issue brought up was integration with MSB and OOM. The action items will be very different if Integration deploys ONAP using Heat template v.s. using OOM.
Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval?YNA

Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone?

NIf Yes, please a link to the evidence of these changes.
Provide link to the API Documentation.DCAE API Documentation

Release ManagementAre committed Sprint Backlog Stories been marked as "Done" in Jira board?Y

Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?Y
Most of these backlog stories are for DCAEGEN1 code. We have no plan to work on them because soon DCAEGEN1 will be deprecated.
Have all findings from previous milestones been addressed?YProvide link to JIRA findings
DevelopmentHas the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar)YGoal: 30-50% for Incubation project

Three Java projects (dcaegen2-analytics-tca, dcaegen2-collectors-ves, dcaegen2-platform-inventory-api) coverage rates are show on SONARQUBE server.

Additional projects coverages are verified by running coverage.py or language local tool on local dev machines:


Python projects

Project/subprojectLOCCoverageEvidence
dcaegen2/platform/cli184074%
dcaegen2/platform/plugins/docker8939%
dcaegen2/platform/plugins/relationships16761%
dcaegen2/platform/plugins/dcaepolicy6278%
dcaegen2/platform/plugins/cdap17658%
dcaegen2/platform/cdapbroker
32%
dcaegen2/utils/python-discovery-client14760%
dcaegen2/utils/python-dockering45543%
dcaegen2/utils/onap-dcae-cbs-docker-client3287%
dcaegen2/utils/onap-dcae-dcaepolicy-lib10672%
dcaegen2/platform/configbinding12955%
dcaegen2/platform/policy-handler76251%


, Other languages

Project/subprojectLOCCoverageEvidence
dcaegen2/platform/servicechange-handler (CLJ)
29.82%sch-index.html
dcaegen2/platform/cdapbroker (Erlang)
32%
Is there any pending commit request older than 36 Business hours in Gerrit?N

Are all the Jenkins jobs successfully passed ( Merge-Jobs)?YProvide link to evidenceBecause most of DCAEGEN2 codebase is NOT Java/Mvn, integration with ONAP CICD process is still in progress.
Are all binaries available in Nexus?YProvide link to evidence

Because most of DCAEGEN2 codebase is NOT Java/Mvn, integration with ONAP CICD process is still in progress.

Awaiting for LF to setup Pypi server.

Integration and Testing

Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins?

Y

https://jenkins.onap.org/view/CSIT/job/dcaegen2-master-verify-csit-testsuites/

https://jenkins.onap.org/view/CSIT/job/dcaegen2-master-csit-testsuites/

12/12 test cases passed
Has the project code successfully passed the Daily Build process?Y
Because most of DCAEGEN2 codebase is NOT Java/Mvn, integration with ONAP CICD process is still in progress.
  • No labels