OOF Dublin M3 Deliverables for API Freeze Milestone Checklist

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?

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?

Yes*

This is a stretch goal in our release planning: OOF Dublin M1 Release Planning#Whatisthisreleasetryingtoaddress?

Jira stories have been created and tracked for this.

key	summary	type	created	updated	due	assignee	reporter	priority	status	resolution

Loading...

Refresh

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?

Update OOM NodePort List

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?

Replace vulnerable packages
Document false positives in the release notes if it is not possible to replace the vulnerable packages
Document vulnerabilities inherited in dependencies: include the name of the dependency and any mitigations that can be implemented by an ONAP user
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 repository

Architecture

Has the Project team reviewed the APIs with the Architecture Committee (ARC)?

Yes

ONAPARC-406 - Getting issue details... STATUS

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?

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?

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.

Yes

CMSO: CMSO API v1_v2, New CMSO APIs in Dublin

HAS: OOF-HAS Homing Specification Guide, Traffic Distribution

OSDF: API Specifications for OOF Applications

FGPS: FGPS Dependencies and APIs

Release Management

Are committed Sprint Backlog Stories been marked as "Closed" in Jira board?

Yes.

Getting issues...

Are all tasks associated with Sprint Backlog Stories been marked as "Closed" in Jira?

Yes