Versions Compared

Old Version 1

changes.mady.by.user James Hahn

Saved on

compared with

New Version Current

changes.mady.by.user Jorge Hernandez

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

1-

...

Project Overview

...

The Policy subsystem of ONAP maintains, distributes, and operates on the set of rules that underlie ONAP’s control, orchestration, and management functions.  See Policy Framework Project Proposal (5/11/17) for more information.

2- New component capabilities for Honolulu-R8

...

3- New or modified interfaces

The following table lists the new functional requirements Policy is committing to support for the Honolulu Release:

Requirements

Notes

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-429

stretch goal

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-441

already done

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-439


Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-437

already done

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-398

support only

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-396

already done

Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-473

POC

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-478

POC


The following epics are in scope for Honolulu, though are not required:

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject in (POLICY) and issuetype in (epic) and (labels != relman OR labels is EMPTY) and (resolution is empty or resolution != Duplicate) and fixversion="Honolulu Release"
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176


Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2923
,
Jira Legacy
serverSystem Jira
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2921
,
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2921
, and
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2919
are extensions to the 
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyREQ-478
 POC.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2484
 , 
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2715
 , 
Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-2352
 are investigative.

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176
keyPOLICY-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 new 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)

These are described in the following page:   PAP REST API changes for Honolulu release.

4- If they are modified, are they backwards compatible?

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.

7- Consumed API from other projects

...

Project

...

API Dependency

...

Notes

...

APi Specs

(Swagger)

See ARC Policy Framework Component Description - Honolulu-R8.

8- Published API

...

Project

...

API

...

Notes

APi Specs

...

See ARC Policy Framework Component Description - Honolulu-R8.


9- Reference to the interfaces.(Reference to the the swagger.json file(s) whenever possible)

See https://docs.onap.org/projects/onap-policy-parent/en/latest/offeredapis.html.

10- What are the system limits?

No more than one PAP may be run at a time.

11- Involved use cases, architectural capabilities or functional requirements.

Policy is used in the following use cases:

  • vFW
  • vDNS
  • vCPE
  • CCVPN
  • 5G

12- Listing of new or impacted models used by the project

...

  • Identify any High Level Information Model Requirements.   See: ONAP R7 Modeling High Level Requirements
    • Models based on information exchanges from Use Cases
    • Models documenting existing implementations
    • Forward looking models that may be implemented in future releases
  • Describe how exposed APIs are mapped to information models

(list all the relevant Jira tickets)

None

13-Test plan/Testing Strategy

  1. Unit Testing
    1. Continue to use junit for java tests
    2. Continue to use jest for javascript tests
  2. Dev-to-Dev Testing  and
    1. Communication between Policy components will be tested via Policy-specific CSITs
    2. 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.
  3. Integration
    1. Integration testing will be done using the integration labs with a full OOM installation

14- Any other details that are specific to this functional enhancement or UseCase.

None