DRAFT PROPOSAL FOR COMMENTS

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

...

Scope

What is this release trying to address?

...

• Platform Maturity Guidelines (Highest Priority)
• 50% JUnit Test Coverage (Highest Priority)
• Integration with OOF to support Hardware Enabled Placement Policies (Medium Priority)
• Control Loop Enhancements for Scale Out (Lowest Priority)
• SDC Distribution Integration (Lowest Priority)
• Policy Lifecycle API (Lowest Priority)

Use Cases

A best effort will be applied to support Integration testing for the existing R1 Use Cases assuming there are NO changes made to those Use Cases.

Hardware Platform Enablement In ONAP - Dependency will be on Intel to supply the required resources. A best effort will be applied to support Intel resources in lieu of Platform Maturity Guidelines and JUnit Test Code Coverage 50%.

VNF Scale Out (TBD - Not enough resources as of 1/8/2018)Hardware Platform Enablement In ONAPvDNS only - requirements planning) - We will do as much work as possible prior to Cassablanca for supporting the auto scale out use case. Dependent on the amount of requirements planning the APP-C team can do.

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.

...

...

...

• Integration with SDC to support future Policy Design GUI integration into SDC
  • We are waiting or SDC to produce their SDK for integration at the end of Beijing
• Policy Lifecycle API
  • Not enough resources or time to fully implement this and make it available to other Components. We expect to have at the very least appropriate documentation, models, and swagger yaml files. 
• Distribution of PDPs across the network - in lieu of support future performance requirements for Control Loops (Eg. a Control Loop must address an issue within X milliseconds of detection in an automated fashion)
  • PDP distribution needs to be enhanced to support multiple PDP's being located in edge, core, global datacenters. (i.e geo-distribution)
  • This should also support high availability and resiliency within each datacenter
  • PDP's designed as Microservices and deployed via OOM registering with MSB

Release Deliverables

Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.

Sub-Components

Activities related to sub-components must be in sync with the overall release.

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

...

High level architecture diagram

At that stage within the Release, the team is expected to provide more Architecture details describing how the functional modules are interacting.

Indicate where your project fit within the ONAP Archiecture diagram.

Block and sequence diagrams showing relation within the project as well as relation with external components are expected.

Anyone reading this section should have a good understanding of all the interacting modules.

Policy Interaction with CLAMP during Design Time

Image Added

Image Added

Policy Interaction with OOF

Image Added

Platform Maturity

...

List the API this project is expecting from other projects.
Prior to Release Planning review, Team Leads must agreed on the date by which the API will be fully defined. The API Delivery date must not be later than the release API Freeze date.

Prior to the delivery date, it is a good practice to organize an API review with the API consumers.

...

• Third Party Products Dependencies

...

• Testing and Integration Plans

Provide a description of the testing activities (unit test, functional test, automation,...) that will be performed by the team within the scope of this release.

...

• • JUnit tests: 50% code coverage is the goal for all repositories.
  • Functional tests: cover all possible Control Loop API calls. Simulating CLAMP and DCAE API calls
    • If resources become available, we will add more API calls such as delete, update.
    • Policy R2 Beijing CSIT Functional Test Cases
  • Integration Test Plans - In progress: Policy R2 Beijing - Integration Test Plans

"Confirm that resources have been allocated to perform such activities" - at this point I do not have enough resources to cover both making the changes for Platform Maturity and help with testing.

• Gaps

This section is used to document a limitation on a functionality or platform support. We are currently aware of this limitation and it will be delivered in a future Release.
List identified release gaps (if any), and its impact.

• Known Defects and Issues

Provide a link toward the list of all known project bugs.

...

• Resources

Fill out the Resources Committed to the Release centralized page.

• Release Milestone

The milestones are defined at the Release Level and all the supporting project agreed to comply with these dates.

...