...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | R1 Amsterdam |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Intel, Huawei, ZTE, Ericsson, IBM, BOCO, China Mobile, Orange,Reliance JIO |
Scope
What is this release trying to address?
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery status != Closed AND status != Done AND project != "Sandbox Project" AND project = POLICY and Type = EPIC and fixVersion = 'Amsterdam Release' ORDER BY priority DESC, updated DESC serverId 425b2b0a-557c-3c0c-b515-579789cceedb
...
Jira server ONAP JIRA columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project=Policy and issuetype in (story) and fixVersion = 'Amsterdam Release' serverId 425b2b0a-557c-3c0c-b515-579789cceedb
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.
- Fuller integration SDC during the design-time - this is not complete right now.
- Capturing policy during VNF on-boarding
- Extending policy during Service Design
- Integration with SO, SDNC, APP-C and VF-C during runtime instantiation, scaling, etc.
- These components should integrate with policy to enforce policy during runtime
- There are platform and overarching policies being created by operators of the platform that should be enforced.
- These components should not rely solely on the service specific policies declared during design time.
- ONAP Platform integration - the policy platform can be used for fine-grained authorization by the rest of the components such as AAF, MSB, OOM
- Fine-grained user management and platform component authorization (i.e. time of day, location, etc.)
- Distribution of PDPs across the network - in lieu of support future performance requirements
- PDP distribution needs to be enhanced to support multiple PDP's being located in edge, core, global datacenters.
- This should also support high availability and resiliency
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description |
|---|---|
| Policy Portal Dashboard | Executable |
| Policy PAP web application | Executable |
| API - internal to the Policy Platform. The Policy PDP engines use this API to synchronize policies being distributed. | |
| Policy Drools PDP | Executable |
| Policy XACML PDP | Executable |
| API - external to ONAP components. The API is used to CRUD Policies, Deploy Policies, and query for Policy Decisions. | |
| Policy BRMS Gateway | Executable |
| MariaDB | SQL database
|
| Nexus Repo | This repository is used by the Policy Drools PDP to retrieve distributed policies and their dependent jars. |
| VNF orchestration | *TBD the deliverables that are viable this release. |
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.
...
DMAAP - We are dependent on Dmaap for pub/sub infrastructure for Control Loop messages between the other ONAP components involved in Control Loop.
AAF - We are dependent on AAF for client libraries to support authentication of Dmaap Topics and ability to establish who can pub/sub topics for Control Loop.
SDC - We are dependent on being able to integrate with the SDC Distribution API in order to receive notification of service distribution. (Stretch)
...
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.
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.
Seed Code Architecture
Policy Seed Code Software Architecture
API Incoming Dependencies
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | |||
|---|---|---|---|---|---|---|---|
| AAI | REST Web Service for AAI | TBD | To fill out | Link toward the detailed API description | We are dependent on that team to provide us this. | ||
| Control Loop Event Messages | Dmaap messages published by DCAE when a Control Loop Event occurs. | We are dependent on that team to provide us this. | |||||
| APP-C | Dmaap message LCM API for auto healing/auto scaling/Restart/Reboot/ModifyConfig | We are dependent on that team to provide us this. | |||||
| VF-C | API for auto scaling/auto healing | We are dependent on that team to provide us this. | |||||
| SO | API for auto scaling | We are dependent on that team to provide us this. | |||||
| DMAAP | API for publish/subscribe to DCAE Control Loop Events and APP-C API | We are dependent on that team to provide us this. |
API Outgoing Dependencies
API this release is delivering to other releases.
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) | To fill out | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description
|---|---|---|---|---|---|---|---|---|
| Policy Client API | This API is used by other ONAP components to create, update and delete policy(s). | TBD | N/A | |||||
| Policy Query API | This API is used by other ONAP components responsible for enforcing policy during runtime. | TBD | N/A |
Third Party Products Dependencies
...
| Jira | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
...
| Risk identified | Mitigation Plan | Contingency Plan | |||
|---|---|---|---|---|---|
| Use Case clarity for control loop | At a minimum, we can deliver auto-healing control loop with dependencies on the API's to A&AI, APP-C, SO and VF-C. | auto-scaling can be pushed to the next release | To fill out | To fill out | To fill out |
Resources
Fill out and provide a link toward 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.
...
Each project must edit its table within the [[Free_and_Open_Source_Software#Project_Licenses| Master Project License Table]].
Board policy (including IPR)
Indicate if the release meets the Board policy.
...
available at Project FOSS.
Charter Compliance
The project team comply with the ONAP Charter.
Release Key Facts
Fill out and provide a link toward the centralized Release Artifacts.