1- Brief Project Overview (brief as it should be known)
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, i.e. the functional enhancements, if applicable
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 (point to an example)
Refer to ARC Policy Framework Component Description - Honolulu-R8.
7- Consumed API from other projects
Refer to ARC Policy Framework Component Description - Honolulu-R8.
8- Published API
Refer to ARC Policy Framework Component Description - Honolulu-R8.
9- Reference to the interfaces.
Refer to https://docs.onap.org/projects/onap-policy-parent/en/latest/offeredapis.html.
10- What are the system limits?
.
11- Involved use cases, architectural capabilities or functional requirements.
12- Listing of new or impacted models used by the project (for information only).
- 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)
13-Test plan/Testing Strategy
- Unit Testing
- Dev-to-Dev Testing and
- Integration