OOF Beijing M3 API Freeze Checklist
- Shankaranarayanan Puzhavakath Narayanan
- Sastry Isukapalli
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 | ||
Is there a plan to address the findings the API review? | Yes | Move the APIs from Wiki to readthedocs. | 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 | 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? | Yes | VNF scale out is removed from our scope for R2, and moved into R3. Dependencies since M1: MUSIC - as a persistent state store, distributed RPC mechanism MSB - in conjunction with OOM for platform maturity | 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 | OSDF: HAS | ||
Release Management | Are committed Sprint Backlog Stories been marked as "Done" in Jira board? | Yes | ||
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira? | Yes | |||
Have all findings from previous milestones been addressed? | Yes | |||
Development | Has the project team reach the Automated Unit Test Code Coverage expectation? (Refer to artifacts available in Sonar) | No | repo-level coverage: OSDF: 56.5% - https://sonar.onap.org/dashboard?id=org.onap.optf.osdf%3Aoptf-osdf HAS: 42.2% - https://sonar.onap.org/dashboard?id=org.onap.optf.has%3Aoptf-has | |
Is there any pending commit request older than 36 Business hours in Gerrit? | No | |||
Do you have a plan to address by M4 the Critical vulnerabilities in the third party libraries used within your project? | NA | Both repos have 0 critical vulnerabilities currently. | 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/optf/job/optf-has-master-conductor-merge-java/ https://jenkins.onap.org/view/optf/job/optf-osdf-master-osdf-merge-java/ | ||
Are all binaries available in Nexus? | No* | https://nexus.onap.org/content/groups/staging/org/onap/optf/ (Work on OSDF binaries is ongoing) | ||
Integration and Testing | Have 50 % of System Integration Testing Use Cases been implemented successfully in Jenkins? | No | We have been able to successfully run CSIT tests using robot framework in our local environment. However, we are facing logistical issues with our Jenkins jobs uploading the images to nexus3. We have been working with LF Helpdesk on resolving this ONAP Helpdesk#53250, ONAP Helpdesk #53309. | |
Has the project code successfully passed the Daily Build process? | Yes | Goal is to ensure the latest project commit has not broken the Integration Daily Build |