DRAFT PROPOSAL FOR COMMENTS

The content of this template is expected to be fill out for M1 Release Planning Milestone.

...

The scope of this release will be for the Policy Framework to support the approved use cases for R1 Amsterdam.

Additionally, this release will also support continued development of the Policy Framework Platform to support future functionality not required for R1 . These use cases specifically require policy to support Control Loops for auto healing/auto scalingAmsterdam. This body of work will be of a lower priority to the work required to support the Use Cases for the Release.

Use Cases

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

Use Case: VoLTE(approved)

Use Case: vFW/vDNS (Approved)

Use Case: Residential Broadband vCPE (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.

...

DMAAP - We are dependent on Dmaap for pub/sub of Control Loop messages with DCAE and APP-Cbetween the other ONAP components involved in Control Loop.

Architecture

High level architecture diagram

...