...

What is this release trying to address?

Describe the problem being solved by this releaseThe scope of this release will be for the Policy Framework to support the approved use cases for R1. These use cases specifically require policy to support Control Loops for auto healing/auto scaling.

Use Cases

Describe the use case this release is targeted for (better if reference to customer use case).

Use Case: VoLTE(approved)

Minimum Viable Product

...

• Policy Portal Dashboard - Console GUI where Models, Templates can be imported, updated, deleted, as well as, policies can be created, updated and deleted. The console GUI also has a dashboard where PDP's can be grouped and where Operators can control where policies are distributed to.
• Policy PAP web application - Policy backend that manages communication with PDP engines for policy distribution.
• Policy Drools PDP - run-time execution of Control Loop operational policies. Supports queries from other ONAP components to retrieve
• Policy XACML PDP - run-time execution of Control Loop configuration policies of DCAE collectors, analytics and micro services.
• Policy BRMS Gateway - intermediary backend for distributing policies to the Drools PDP and configuration details to the Drools PDP controller.

Functionalities

List the functionalities that this release is committing to deliver by providing a link to JIRA Epics and Stories. In the JIRA Priority field, specify the priority (either High, Medium, Low). The priority will be used in case de-scoping is required. Don't assign High priority to all functionalities.

...

Sub-Components

List all sub-components part of this release.
Activities related to sub-component must be in sync with the overall release.

Sub-components are repositories are consolidate in a single centralized place. Edit the Release Components name for your project in the centralized page.

ONAP Dependencies

List the other ONAP projects your depends onPortal - Our dashboard is compiled with the Portal SDK and is accessed as a "tab" in the Portal web application.

DCAE - We require that DCAE on-board their collectors, analytics, and micro services via the DCAE Design Tool that is currently supported by SDC.

CLAMP - CLAMP calls the Policy API to do create 2 types of policies for Control Loops:

• Create/update DCAE collector, analytic and micro service configuration Policies.
• Create/update the Operational Policy using the Policy YAML SDK

APPC - We are dependent on APPC to extend their Lifecycle API to expose API that implement auto healing/auto scaling for the use cases. The current API is Dmaap-based.

VF-C - We are dependent on VF-C for control loop auto healing/auto scaling.

A&AI - We are dependent on A&AI to work with us on the ability of the Drools Application code/templates to be able to look up Service/VNF/VM topology.

DMAAP - We are dependent on Dmaap for pub/sub of Control Loop messages with DCAE and APP-C.

Architecture

High level architecture diagram

...

Third Party Products mean products that are mandatory to provide services for your components. Development of new functionality in third party product may or not be expected.
List the Third Party Products (OpenStack, ODL, RabbitMQ, ElasticSearch,Crystal Reports, ...).

In case there are specific dependencies  (Centos 7 vs Ubuntu 16. Etc.) list them as well.

...