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
- Use the "Copy" and "Move" options (available under the ..., top right of this page) to duplicate this template into your project wiki.
- Fill out the Yes/No column
- Provide link to evidence (when necessary)
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | OOM Casablanca - M3 Architecture Review | M3 Architecture successfully reviewed August 21. NOTE: OOM provides no external APIs. |
| Is there a plan to address the findings the API review? | N/A | OOM Casablanca - M3 Architecture Review | M3 Architecture reviewed August 21 - no actions identified NOTE: OOM provides no external APIs | |
| Does the team clearly understand that no changes in the API definition is allowed without formal TSC review and approval? | Yes | NA | OOM provides no external API's. | |
Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone? | No | |||
| Provide link to the API Documentation. | N/A | OOM Provides no API's | ||
| Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | Stories are marked done as completed | |
| Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | Tasks are marked done as completed | ||
| Have all findings from previous milestones been addressed? | Yes | See Casablanca Risks | ||
| Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | N/A | Helm/Kubernetes do not have unit tests and is not supported by Sonar. See Sonar OOM Results | |
| Is there any pending commit request older than 36 Business hours in Gerrit? | No | See search | ||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | Yes | https://onap.readthedocs.io/en/beijing/submodules/oom.git/docs/oom_cloud_setup_guide.html | No known Vulnerabilities. Versions as per the link are in use in Casablanca with exception that Helm will upgrade to 2.9.1. Docs will be updated to align with this change. | |
| Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Yes | https://jenkins.onap.org/view/oom/ | ||
| Are all binaries available in Nexus? | No | Blocked waiting on See Casablanca Risks # 6. | ||
| Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | N/A | OOM is not directly in the flow for use cases. Functional testing of ONAP using ROBOT health checks, validates OOM deployments as seen in Auto Continuous Deployment via Jenkins and Kibana | |
| Has the project code successfully passed the Daily Build process? | Yes | Builds are on demand per project - (not daily build) Build link TBD - will be output of OOM-752 - Getting issue details... STATUS |
