Versions Compared

Version Old Version 2 New Version Current
Changes made by

James Hahn

James Hahn

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Project NameEnter the name of the project
Target Release NameIstanbul
Project Lifecycle StateMature
Participating Company AT&T, Ericsson, Bell Canada

Scope

Planned Updates

  • Make policy-clamp official
  • Make TOSCA Control Loop official
  • Multi-cluster support
  • Only send policy deltas to PDPs
  • Allow rules to specify EventManagerService
  • DB Enhancements
  • Unify the representation of control loops in CLAMP
  • Update control loop TOSCA to support design-time and runtime roles
  • APEX-PDP enhancements
    • SSL support in Kafka IO plugin
    • Send notifications to DMaaP/Kafka
    • Context album improvements
    • Mount truststore via helm charts
  • Add more flexible time and dayOfWeek capabilities in xacml-pdp
  • Store audit details of policy deploy/undeploy in PAP
  • Enhance consolidated health check to include dependencies (e.g., DMaaP connectivity)
  • Usual sonar/code coverage improvements
  • Archive policy-engine repo and change its status to “unmaintained”

Requirements

Please see the release requirements planned as identified in Policy Istanbul-R9 Architecture Review

Minimum Viable Product

The following application components are the MVP from this release.

  • Policy Lifecycle API component
  • Policy Administration Point component
  • PDP-A - Apex PDP Engine
  • PDP-D - Drools PDP Engine
  • PDP-X - XACML PDP Engine
  • Policy Distribution Component

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
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = POLICY AND fixVersion = "Istanbul Release" and resolution != "Won't Do" and issuetype in (epic)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

Jira Legacy
serverSystem Jira
columnskey,summary,type,created,updated,due,assignee,reporter,priority,status,resolution
maximumIssues20
jqlQueryproject = POLICY AND fixVersion = "Istanbul Release" and resolution != "Won't Do" and issuetype in (story)
serverId4733707d-2057-3a0f-ae5e-4fd8aff50176

...

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.

Link toward the detailed API description
API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill out
AAFAuthentication

We are not expecting any upgrades for any of our requirements.

M3
DmaapMessage Router

We are not expecting any upgrades for any of our requirements.

M3
SDCService Distribution

We are not expecting any upgrades for any of our requirements.

DMaaP

M3
AAI

Schema for custom query calls

We are not expecting any upgrades for any of our requirements.

REST

M3
SOVF Module Create

We are not expecting any upgrades for any of our requirements.

REST

M3
SDNRSDN-R component interface

We are not expecting any upgrades for any of our requirements.

Dmaap - No direct link to any libraries

M3
SDNCSDN-C component interface

We are not expecting any upgrades for any of our requirements.

Dmaap - No direct link to any libraries

M3
VFCVFC component interface

We are not expecting any upgrades for any of our requirements.

REST

M3
CDSCDS component Interface

Upgrading to new CDS jars

M3

  • API Outgoing Dependencies

...

API NameAPI DescriptionAPI Definition DateAPI Delivery dateAPI Definition link (i.e.swagger)
To fill outHigh level description of the APIDate for which the API is reviewed and agreedTo fill outLink toward the detailed API description

  • Third Party Products Dependencies

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.

  • 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.

Describe the plan to integrate and test the release deliverables within the overall ONAP system.
Confirm that resources have been allocated to perform such activities.

...

Policy Lifecycle APICRUD for Policy Types and PoliciesM3M3https://docs.onap.org/projects/onap-policy-parent/en/latest/api/api.html
PAP API

PDP Group API and Deploy/Undeploy of Policies

Health Check

Policy Deployment Status

PDP-Policy Deployment Status

M3M3https://docs.onap.org/projects/onap-policy-parent/en/latest/pap/pap.html
Decision APIClient API for ONAP components to ask for Decision as to which policy they should enforce for a set of given attributes.M3M3https://docs.onap.org/projects/onap-policy-parent/en/latest/xacml/decision-api.html

  • Third Party Products Dependencies



DescriptionVersion
MariaDBThe MariaDB is the repository that holds all the policies, templates, PDP group, and deployment information.

10.5.8

OpenJDKOpenJDK for Alpine from integration images (integration/docker/onap-java11 repository)
openjdk11:jre-11.0.11_9-alpine


  • Testing and Integration Plans

The testing and integration activities are described in the following page: Policy R9 Istanbul CSIT/External Lab Functional Test Cases

  • Gaps

No gaps identified.

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.

Gaps identifiedImpact
To fill outTo fill out

  • Known Defects and Issues

Please refer to Frankfurt Defect StatusThere are no major known defects or issues.


  • Risks

List the risks identified for this release along with the plan to prevent the risk to occur (mitigation) and the plan of action in the case the risk would materialized (contingency).

Please update any risk on the centralized wiki page - Frankfurt Risks

  • Resources

Fill out the Resources Committed to the Release centralized page.There are no known risks.


  • Resources

Please refer to the INFO.yaml for each policy repo:

https://git.onap.org/policy/apex-pdp/tree/INFO.yaml

https://git.onap.org/policy/api/tree/INFO.yaml

https://git.onap.org/policy/clamp/tree/INFO.yaml

https://git.onap.org/policy/common/tree/INFO.yaml

https://git.onap.org/policy/distribution/tree/INFO.yaml

https://git.onap.org/policy/docker/tree/INFO.yaml

https://git.onap.org/policy/drools-applications/tree/INFO.yaml

https://git.onap.org/policy/drools-pdp/tree/INFO.yaml

https://git.onap.org/policy/gui/tree/INFO.yaml

https://git.onap.org/policy/models/tree/INFO.yaml

https://git.onap.org/policy/parent/tree/INFO.yaml

https://git.onap.org/policy/pap/tree/INFO.yaml

https://git.onap.org/policy/xacml-pdp/tree/INFO.yaml


  • Release Milestone

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


  • Team Internal Milestone

This section is optional and may be used to document internal milestones within a project team or multiple project teams. For instance, in the case the team has made agreement with other team to deliver some artifacts on a certain date that are not in the release milestone, it is erecommended to provide these agreements and dates in this section.

It is not expected to have a detailed project plan.

...


  • Documentation, Training

Please update the following centralized wiki: Frankfurt Documentation

That includes

  • Team contributions to the specific document related to he project (Config guide, installation guide...).
  • Team contributions to the overall Release Documentation and training asset
  • High level list of documentation, training and tutorials necessary to understand the release capabilities, configuration and operation.
  • Documentation includes items such as:
    • Installation instructions
    • Configuration instructions
    • Developer guide
    • End User guide
    • Admin guide
    • ...

...

titleNote

...

Minor updates are expected as documented in the Istanbul Documentation

Other Information

  • Vendor Neutral

If this project is coming from an existing proprietary codebase, ensure that all proprietary trademarks, logos, product names, etc. have been removed. All ONAP deliverables must comply with this rule and be agnostic of any proprietary symbols.N/A

  • Free and Open Source Software

...