...
Practice Area | Checkpoint | Yes/No | Evidences | How to? | |||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Security | Has the Release Security/Vulnerability table been updated in the protected Security Vulnerabilities wiki space? | Yes | R4 VID Security/Vulnerability - Full Content | 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? | Yes | 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? | Yes | OOM NodePort List | Update OOM NodePort List | ||||||||||||||||
Has the project provided the communication policy to OOM and Integration?Yes | No | Will address, tracking with
| 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? | Yes | See Jira tickets in R4 VID Security/Vulnerability - Full Content |
| ||||||||||||||||
Architecture | Has the Project team reviewed the APIs with the Architecture Committee (ARC)? | Yes | Architecture walk through to understand how each project contributes on Release Use Case. ARC to organize the walk through. | ||||||||||||||||
Is there a plan to address the findings the API review? | n/a | Link to plan | 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 | 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? | Evaluating | Yes |
| 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. | Yes | https://onap.readthedocs.io/en/latest/submodules/vid.git/docs/offeredapis.html | |||||||||||||||||
Release Management | Are committed Sprint Backlog Stories been marked as "Closed" in Jira board? | Yes | https://jira.onap.org/secure/RapidBoard.jspa?rapidView=61&projectKey=VID&view=planning.nodetail&epics=visible&selectedVersion=10473 | ||||||||||||||||
Are all tasks associated with Sprint Backlog Stories been marked as "Closed" in Jira? | Yes | ||||||||||||||||||
Have all findings from previous milestones been addressed? | n/a | Provide link to JIRA findings | |||||||||||||||||
Development | Is there any pending commit request older than 36 Business hours in Gerrit? | No | https://gerrit.onap.org/r/#/q/project:vid+status:open+NOT+status:draft | Gerrit Query: status:open label:verified -is:draft -label:Code-Review=-1 AND -label:Code-Review=-2 AND is:mergeable age:1week | |||||||||||||||
Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | Yes | Goal: 55% for Incubation project in the current release | Guidance on Code Coverage and Static Code Analysis Tools: Sonar | ||||||||||||||||
Are all the Jenkins jobs successfully passed ( Merge-Jobs)? | Yes | https://jenkins.onap.org/view/vid/job/vid-master-merge-java/ | |||||||||||||||||
Are all binaries available in Nexus? | Yes | https://nexus3.onap.org/#browse/... | |||||||||||||||||
Integration and Testing | Have 50% of System Integration Testing Use Cases been implemented successfully in Jenkins? It should include at least 1 CSIT that will be run on Lab-xxx-OOM-Daily Jenkins Job | Yes | https://jenkins.onap.org/view/vid/job/vid-master-csit-healthCheck/ | ||||||||||||||||
Has the project code successfully passed the Daily Build process? | Yes | https://jenkins.onap.org/view/vid/job/vid-master-docker-version-java-daily/ | Goal is to ensure the latest project commit has not broken the Integration Daily Build | ||||||||||||||||
Has the project passed the Integration Sanity Tests? | No |
Issue is addressed by resolving the following:
| Integration sanity tests in Dublin Release cover:
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 | ||||||||||||||||
Modeling | Has the Project team provided links to Data Models (e.g, JSON, YANG, Swagger, etc.) for all Shared Information (e.g., APIs, API Payload, Shared Design Model)? | No | It is a non-blocking item for M3 - The Modeling team is gathering information |
...