...
| Info | ||
|---|---|---|
| ||
|
| Practice Area | Checkpoint | Yes/No | Evidences | How to? |
|---|---|---|---|---|
| Security | Has the Release Security/Vulnerability table been updated in the protected Security Vulnerabilities wiki space? | Table in in the protected Security Vulnerabilities wiki space corresponds to the latest NexusIQ scan | PTL reviews the NexusIQ scans for their project repos and fills out the vulnerability review table | |
| Has the project committed to enabling transport level encryption on all interfaces and the option to turn it off? | Requirements and test cases for transport layer encryption have been created for all interfaces not currently supporting encryption. | |||
| Has the project documented all open port information? | ||||
| Has the project provided the communication policy to OOM and Integration? | Recommended Protocols | |||
| Do you have a plan to address by M4 the Critical and High vulnerabilities in the third party libraries used within your project? |
| |||
| Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | OOM Dublin - M3 Architecture Review (passed review March 5, 2019) OOM provides no external APIs. | Architecture walkthrough to understand how each project contributes on Release Use Case. ARC to organize the walkthrough. |
| Is there a plan to address the findings the API review? |
| N/A | OOM Dublin - M3 Architecture Review (passed review March 5, 2019) OOM provides no external APIs | The plan could be as simple as a Jira issue to track the implementation of findings or a documented plan within the wiki. | |
| 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. | In the case some changes are necessary, bring the request to the TSC for review and approval. |
Is there any changes in the scope, functionalities, deliverable, dependency, resources, API, repositories since M1 milestone? | No | If Yes, please a link to the evidence of these changes. | Critical point to understand is that change is inevitable, and that right timing and clear communication to the community will ease the process of accepting changes. |
| Provide link to the API Documentation. | N/A | OOM provides no external API's. | |
| Release Management | Are committed Sprint Backlog Stories been marked as "Closed" in Jira board? | Yes |
| Stories are marked done as completed | |||
| Are all tasks associated with Sprint Backlog Stories been marked as "Closed" in Jira? | Yes | Tasks are marked done as completed | |
| Have all findings from previous milestones been addressed? |
| Yes | See Dublin Risks #16,17 | |||
| Development | Is there any pending commit request older than 36 Business hours in Gerrit? | No | See search | |
| 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 | Helm/Kubernetes do not have unit tests and is not supported by Sonar. See Sonar OOM Results Guidance on Code Coverage and Static Code Analysis Tools: Sonar | |||||||||||||||||||||
| Do you have a plan to address by M4 the Critical and High vulnerabilities in the third party libraries used within your project? | Yes |
| Ensure by M4 the Nexus-IQ report from “Jenkins CLM” shows 0 critical security vulnerability. Open the Nexus-IQ report for the details on each repo. | ||||||||||||||||||||
Are all the Jenkins jobs successfully passed ( Merge-Jobs)? |
| Yes | https://jenkins.onap.org/view/oom/ | ||
| Are all binaries available in Nexus? |
| Yes | Helm charts for Dublin 4.0.0 can be found in public helm repo: https://nexus.onap.org/content/sites/oom-helm-staging/master/ | |
| Integration and Testing | Have 50% of System Integration Testing Use Cases been implemented successfully in Jenkins? |
| N/A | Auto Continuous Deployment via Jenkins and Kibana | 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 | https://jenkins.onap.org/view/oom/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build |
| Has the project code successfully passed the daily Integration sanity test (in another words, no blocking issue reported on the project)? | Yes | Check blocking issue page |