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
The following table lists the new functional requirements Policy is committing to support for the Honolulu Release:
Requirements | Notes |
---|---|
stretch goal | |
already done | |
already done | |
support only | |
already done | |
POC |
TODO: add a list of EPICs to be included
3- New or modified interfaces
The following changes will be made to the interfaces during the Honolulu release:
- Add a new API to PAP to query the deployment status of all PDP/policy pairs
- In the health check API, include information about the availability of dependent systems (e.g., A&AI, DB, DMaaP)
4- If they are modified, are they backwards compatible?
Yes
6- Interface naming
See ARC Policy Framework Component Description - Honolulu-R8.
7- Consumed API from other projects
See ARC Policy Framework Component Description - Honolulu-R8.
8- Published API
See ARC Policy Framework Component Description - Honolulu-R8.
9- Reference to the interfaces.
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
None
13-Test plan/Testing Strategy
- Unit Testing
- Continue to use junit for java tests
- Continue to use ??? 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 with a full kubernetes installation
14- Any other details that are specific to this functional enhancement or UseCase.
None