...
| Project Name | Enter the name of the project |
|---|---|
| Target Release Name | Casablanca |
| Project Lifecycle State | Incubation |
| Participating Company | AT&T, Ericsson, Amdocs (Confirming), Intel (Confirming), TechMahindra (Confirming) |
...
- Maintenance of current Platform MVP components
- 70% 50% code coverage (Java and Javascript)
- Reliability of S3P functionality
- Security Enhancements to further progress towards Silver badge
- internal communication encrypted
- role-based access control and authorization for all calls
- HPA Functional Requirement
- Creation of Application that integrates with SDC Service Distribution
- Must support current API and have hooks to support future Policy Lifecycle API
- Dockerized, HELM Chart, Health Check, CSIT, S3P, 70% code coverage
- Creation of Application that integrates with SDC Service Distribution
- Re-architecture of the Platform components for long term
- 70% code coverage - over new components
- S3P functionality for new components
- Ingest of Apex PDP engineCreation of Application that integrates with SDC Service Distribution
- Dockerized, HELM Chart, Health Check, CSIT, S3P, 70% code coverage
- PAP 2nd Generation
- Re-build of PAP ↔ PDP Policy Distribution API using Maven Nexus Repo.
- Re-build of PAP ↔ PDP Grouping
- Above 2 requirements will involve creation of PDP SDK (2nd Generation)
- Policy Lifecycle API
- Dockerized, HELM Chart, Health Check, CSIT, S3P, 70% code coverage
- XACML PDP 2nd Generation
- Configurability of XACML Combining Algorithms for root engine
- Open support for raw XACML policies
- Integration with PDP SDK (2nd Generation)
- Policy Engineer Development Environment
- Documentation
Use Cases
vFW/vLBvDNS/vCPE/VOLTE
HPA
Auto Scale Out- Test only support
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.
...
Jira Legacy server System Jira columns key,summary,type,created,updated,due,assignee,reporter,priority,status,resolution maximumIssues 20 jqlQuery project = POLICY and Type = Story and fixVersion = 'Casablanca Release' and Resolution = 'Unresolved' ORDER BY priority DESC, updated DESC serverId 4733707d-2057-3a0f-ae5e-4fd8aff50176
Longer term roadmap
Indicate at a high level the longer term roadmap. This is to put things into the big perspective.Casablanca will begin development of its new architecture as described in this wiki: The ONAP Policy Framework
Release Deliverables
Indicate the outcome (Executable, Source Code, Library, API description, Tool, Documentation, Release Note...) of this release.
| Deliverable Name | Deliverable Description | To fill out | To fill out|
|---|---|---|---|
| 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 | ||
| Existing 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. | ||
| Policy Lifecycle API (2nd Generation) | Description/Documentation | ||
| Policy SDC Distribution Integration | Executable | ||
| Policy PAP (2nd Generation) | Executable | ||
| Policy PDP SDK (2nd Generation) | Code Deliverable | ||
| Policy Apex PDP | Executable | ||
| Policy XACML PD (2nd Generation) | Executable |
Sub-Components
List all sub-components part of this release.
Activities related to sub-components must be in sync with the overall release.
...
| Area | Actual Level | Targeted Level for current Release | How, Evidences | Comments |
|---|---|---|---|---|
| Performance | 1 | 1 |
| |
| Stability | 1 | 1 |
| |
| Resiliency | 2 | 2 |
| |
| Security | 1 | 2 |
| |
| Scalability | 1 | 1 |
| |
| Manageability | 1 | 1 |
| |
| Usability | 1 | 1 |
|
...
| API Name | API Description | API Definition Date | API Delivery date | API Definition link (i.e.swagger) |
|---|---|---|---|---|
| To fill outCommon Actor API | High level description of the API | Date for which the API is reviewed and agreed | To fill out | Link toward the detailed API description |
| AAI | REST Web Service for AAI | Beijing | ||
| Control Loop Event Messages | Dmaap messages published by DCAE when a Control Loop Event occurs. | Beijing | n/a | n/a |
| APP-C | Dmaap message LCM API for Restart and ModifyConfig | Beijing | ||
| SO | API for auto scaling (for backwards compatibility until Common Actor API is established) | Beijing | ||
| DMAAP | API for publish/subscribe to DCAE Control Loop Events and APP-C API | Beijing |
API Outgoing Dependencies
...