...
| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| maximumIssues | 20 |
|---|
| jqlQuery | project in (POLICY) and issuetype in (epic) and (labels != relman OR labels is EMPTY) and (resolution is empty or resolution != Duplicate) and fixversion="Honolulu Release" |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
|
Some of the epics are just investigative for Honolulu
| Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2923 |
|---|
|
, | Jira Legacy |
|---|
| server | System Jira |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2921 |
|---|
|
, | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2921 |
|---|
|
, and | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2919 |
|---|
|
are extensions to the | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | REQ-478 |
|---|
|
POC.| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2484 |
|---|
|
, | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2715 |
|---|
|
, | Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2352 |
|---|
|
are investigative.| Jira Legacy |
|---|
| server | System Jira |
|---|
| columns | key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution |
|---|
| serverId | 4733707d-2057-3a0f-ae5e-4fd8aff50176 |
|---|
| key | POLICY-2605 |
|---|
|
covers miscellaneous technical debt from Guilin and will be completed.
3- New or modified interfaces
The following changes will be made to the interfaces during the Honolulu release:
- Add a new API APIs to the PAP to query the deployment status of all PDP/policy pairs.
- Change return status from 200 to 202 in the PAP deployment APIs.
- In the health check API, include information about the availability of dependent systems (e.g., A&AI, DB, DMaaP)
- Change return status to 202 when policies are being deployed
- provide query method to determine policy status - already available? TBD
These are described in the following page: PAP REST API changes for Honolulu release.
4- If they are modified, are they backwards compatible?
No - due to change of 200 to 202 for policy deployment (TBD: if don't do this change, then it can be "Yes")The PAP API deployment changes are not backwards compatible, nevertheless it is expected minimum impact as its main consumer, CLAMP, is being migrated under the Policy components umbrella.
6- Interface naming
See ARC Policy Framework Component Description - Honolulu-R8.
...
- Unit Testing
- Continue to use junit for java tests
- Continue to use TBD jest for javascript tests
- Dev-to-Dev Testing and
- Communication between Policy components will be tested via Policy-specific CSITs
- There are no plans for individual dev-to-dev testing with other ONAP projects. There are no facilities within Policy to test an interface independent of a use case, nor can other systems provide "sunny-day" responses without being pre-configured. As a result, dev-to-dev testing will take place as part of the integration testing of various use cases. This is unchanged from previous releases.
- Integration
- Integration testing will be done using the integration lab labs with a full kubernetes OOM installation
14- Any other details that are specific to this functional enhancement or UseCase.
...