...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery status != Closed AND status != Done AND project ! = "Sandbox Project" AND project = POLICY and Type = EPIC and fixVersion = 'Amsterdam Release' ORDER BY priority DESC, updated DESC serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=Policy and issuetype in (story) and fixVersion = 'Amsterdam Release' serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
...
Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.
...
DMAAP - We are dependent on Dmaap for pub/sub infrastructure for Control Loop messages between the other ONAP components involved in Control Loop.
AAF - We are dependent on AAF for client libraries to support authentication of Dmaap Topics and ability to establish who can pub/sub topics for Control Loop.
SDC - We are dependent on being able to integrate with the SDC Distribution API in order to receive notification of service distribution. (Stretch)
...
List the API this release is expecting from other releases.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.
Prior to the delivery date, it is a good practice to organize an API review with the API consumers.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| AAI | REST Web Service for AAI | We are dependent on that team to provide us this. | ||
| Control Loop Event Messages | Dmaap messages published by DCAE when a Control Loop Event occurs. | We are dependent on that team to provide us this. | ||
| APP-C | Dmaap message LCM API for auto healing/auto scaling/Restart/Reboot/ModifyConfig | We are dependent on that team to provide us this. | ||
| VF-C | API for auto scaling/auto healing | We are dependent on that team to provide us this. | ||
| SO | API for auto scaling | We are dependent on that team to provide us this. | ||
| DMAAP | API for publish/subscribe to DCAE Control Loop Events and APP-C API | We are dependent on that team to provide us this. |
API Outgoing Dependencies
API this release is delivering to other releases.
...
| Jira Legacy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
Resources
Fill out and provide a link toward the Resources Committed to the Release centralized page.
Release Milestone
The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.
...
Each project must edit its table available at Project FOSS.
Board policy (including IPR)
...
Charter Compliance
The project team comply with the ONAP Charter.
Release
...
Key Facts
Fill out and provide a link toward the centralized Release Artifacts.