Skip to end of metadata
Go to start of metadata

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/NoEvidencesHow to?
Architecture


Has the Project team reviewed the APIs with the Architecture Committee (ARC)?Yeshttps://jira.onap.org/browse/ONAPARC-94


Is there a plan to address the findings the API review?Yes

Move the APIs from Wiki to readthedocs.

OOF/HAS API Specifications

CM API Specifications

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?YesNAIn 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 ManagementAre committed Sprint Backlog Stories been marked as "Done" in Jira board?YesCompleted Stories
Are all tasks associated with Sprint Backlog Stories been marked as "Done" in Jira?YesCompleted Tasks
Have all findings from previous milestones been addressed?Yes

DevelopmentHas 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

Guidance on Code Coverage and Static Code Analysis

Tools: Sonar

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.

HAS: https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/optf-has/039c27a2ef2c4410995ddd23d4353205

OSDF: https://nexus-iq.wl.linuxfoundation.org/assets/index.html#/reports/optf-osdf/2c49e2ebdb7b4535b7c30796e4736463

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?Yeshttps://jenkins.onap.org/view/optf/Goal is to ensure the latest project commit has not broken the Integration Daily Build