-Release Data
-============
-
-+--------------------------------------+--------------------------------------+
-| **Policy Project** | |
-| | |
-+--------------------------------------+--------------------------------------+
-| **Docker images** | - policy-api 2.2.3 (tbd) |
-| | - policy-pap 2.2.2 (tbd) |
-| | - policy-drools-pdp 1.6.3 (tbd) |
-| | - policy-xacml-pdp 2.2.1 (tbd) |
-| | - policy-apex-pdp 2.3.1 (tbd) |
-| | - policy-distribution 2.3.1 (tbd) |
-| | - policy-pe 1.6.3 (tbd) |
-| | |
-+--------------------------------------+--------------------------------------+
-| **Release designation** | 6.0.0 frankfurt |
-| | |
-+--------------------------------------+--------------------------------------+
-| **Release date** | 2020-06-04 (tbd) |
-| | |
-+--------------------------------------+--------------------------------------+
+**Security Notes**
+
+*Fixed Security Issues*
+
+
+ * `[POLICY-2678] <https://jira.onap.org/browse/POLICY-2678>`_ - policy/engine tomcat upgrade for CVE-2020-11996
+Artifacts released:
+
+.. csv-table::
+ :header: "Repository", "Java Artifact", "Docker Image (if applicable)"
+ :widths: 15,10,10
+
+ "policy/parent", "3.1.3", ""
+ "policy/common", "1.6.5", ""
+ "policy/models", "2.2.6", ""
+ "policy/api", "2.2.4", "onap/policy-api:2.2.4"
+ "policy/pap", "2.2.3", "onap/policy-pap:2.2.3"
+ "policy/drools-pdp", "1.6.3", "onap/policy-drools:1.6.3"
+ "policy/apex-pdp", "2.3.2", "onap/policy-apex-pdp:2.3.2"
+ "policy/xacml-pdp", "2.2.2", "onap/policy-xacml-pdp:2.2.2"
+ "policy/drools-applications", "1.6.4", "onap/policy-pdpd-cl:1.6.4"
+ "policy/engine", "1.6.4", "onap/policy-pe:1.6.4"
+ "policy/distribution", "2.3.2", "onap/policy-distribution:2.3.2"
+ "policy/docker", "2.0.1", "onap/policy-jdk-alpine:2.0.1, onap/policy-jre-alpine:2.0.1, onap/policy-jdk-debian:2.0.1, onap/policy-jre-debian:2.0.1"
+
+Summary
+=======
+
+New features include policy update notifications, native policy support, streamlined health check for the Policy Administration Point (PAP),
+configurable pre-loading/pre-deployment of policies, new APIs (e.g. to create one or more Policies with a single call), new experimental PDP monitoring GUI, and enhancements to all three PDPs: XACML, Drools, APEX.
+
-* Support for offline mode.
- - The OOM deployment now supports offline mode for PDP-D by default.
-
-* Parameterize mvn repo urls and proxy settings
- - This allows the users to build the docker images for drools-pdp and drools-application using their own CI pipelines if needed.
-
-* TOSCA Policy Type design for operational policy supported by Drools so that policy is compliant with TOSCA policies
-* pip updated to pip3 in docker.
-* Extend PDP-D capabilities so that it can instantiate new drools controller instances for executing native Drools policies deployed from PAP.
-* Updated drools to use the redesigned Actors in policy/models.
-* Server Pool feature for supporting multiple active Drools PDP hosts.
-* server-pool is a resilient implementation that supports redundancy within and across data centers involving multiple PDP-Drools. Implementation involves hashing of which PDP-Drools owns which transaction and routing transactions to the appropriate PDP-Drools. By implementing as a feature, any deployment can choose to use or not use server-pool for its redundancy needs.
+* Support for PDP-D in offline mode to support locked deployments. This is the default ONAP installation.
+* Parameterize maven repository URLs for easier CI/CD integration.
+* Support for Tosca Compliant Operational Policies.
+* Support for TOSCA Compliant Native Policies that allows creation and deployment of new drools-applications.
+* Validation of Operational and Native Policies against their policy type.
+* Support for a generic Drools-PDP docker image to host any type of application.
+* Experimental Server Pool feature that supports multiple active Drools PDP hosts.
-* Support for offline mode.
-* Rate limiting DCAE flooding of ONSETs
- - Policy will get flooded with potentially hundreds of ONSETs at once being picked up from DMaaP. Processing of multiple ONSETs (potentially hundreds in a batch read) of the same underlying unique network alarm severely impacts performance.
-
-* Design Operational Policy Type for Drools
- - Design and preload the drools operational policy type.
- - Backwards compatible support for tosca operational policies in usecases.
- - Tosca compliant vCPE, vFirewall, vDNS
-
-* PDP-D support for native Drools policy execution
- - Topics are decoupled from controllers. Native policies require topics configured at installation. Topics can also be overridden or new ones added when being placed in the mounted config directory.
-
-* Update Drools to use new actors.
- - Add frankfurt rules for Actor redesign
- - Usecases controller disabled (to be removed shortly after Frankfurt release) and the Frankfurt controller will be used.
-
-* Delete template.demo sub-module and amsterdam controllers
-* Removed vLB from drools-apps.
-* Replace URL with host/port/contextURI in the controlloop properties.
- - Corresponding changes in base.conf file in OOM which is mounted.
+* Removal of DCAE ONSET alarm duplicates (with different request IDs).
+* Support of a new controller (frankfurt) that supports the ONAP use cases under the new actor architecture.
+* Deprecated the "usecases" controller supporting the use cases under the legacy actor architecture.
+* Deleted the unsupported "amsterdam" controller related projects.
+Version: 5.0.2
+--------------
+
+:Release Date: 2020-08-24 (El Alto Maintenance Release #1)
+
+**New Features**
+
+Artifacts released:
+
+.. csv-table::
+ :header: "Repository", "Java Artifact", "Docker Image (if applicable)"
+ :widths: 15,10,10
+
+ "policy/api", "2.1.3", "onap/policy-api:2.1.3"
+ "policy/pap", "2.1.3", "onap/policy-pap:2.1.3"
+ "policy/drools-pdp", "1.5.3", "onap/policy-drools:1.5.3"
+ "policy/apex-pdp", "2.2.3", "onap/policy-apex-pdp:2.2.3"
+ "policy/xacml-pdp", "2.1.3", "onap/policy-xacml-pdp:2.1.3"
+ "policy/drools-applications", "1.5.4", "onap/policy-pdpd-cl:1.5.4"
+ "policy/engine", "1.5.3", "onap/policy-pe:1.5.3"
+ "policy/distribution", "2.2.2", "onap/policy-distribution:2.2.2"
+ "policy/docker", "1.4.0", "onap/policy-common-alpine:1.4.0, onap/policy/base-alpine:1.4.0"
+
+
+**Bug Fixes**
+
+
+ * `[PORTAL-760] <https://jira.onap.org/browse/PORTAL-760>`_ - Access to Policy portal is impossible
+ * `[POLICY-2107] <https://jira.onap.org/browse/POLICY-2107>`_ - policy/distribution license issue in resource needs to be removed
+ * `[POLICY-2169] <https://jira.onap.org/browse/POLICY-2169>`_ - SDC client interface change caused compile error in policy distribution
+ * `[POLICY-2171] <https://jira.onap.org/browse/POLICY-2171>`_ - Upgrade elalto branch models and drools-applications
+ * `[POLICY-1509] <https://jira.onap.org/browse/POLICY-1509>`_ - Investigate Apex org.python.jython-standalone.2.7.1
+ * `[POLICY-2062] <https://jira.onap.org/browse/POLICY-2062>`_ - APEX PDP logs > 4G filled local storage
+
+
+**Security Notes**
+
+*Fixed Security Issues*
+
+
+ * `[POLICY-2475] <https://jira.onap.org/browse/POLICY-2475>`_ - Update El Alto component certificates
+
- - POLICY-969 Docker improvement in policy framwork modules
- - POLICY-1074 Fix checkstyle warnings in every repository
- - POLICY-1121 RPM build for Apex
- - POLICY-1223 CII Silver Badging Requirements
- - POLICY-1600 Clean up hash code equality checks, cloning and copying in policy-models
- - POLICY-1646 Replace uses of getCanonicalName() with getName()
- - POLICY-1652 Move PapRestServer to policy/common
- - POLICY-1732 Enable maven-checkstyle-plugin in apex-pdp
- - POLICY-1737 Upgrade oParent 2.0.0 - change daily jobs to staging jobs
- - POLICY-1742 Make HTTP return code handling configurable in APEX
- - POLICY-1743 Make URL configurable in REST Requestor and REST Client
- - POLICY-1744 Remove topic.properties and incorporate into overall properties
- - POLICY-1770 PAP REST API for PDPGroup Healthcheck
- - POLICY-1771 Boost policy/api JUnit code coverage
- - POLICY-1772 Boost policy/xacml-pdp JUnit code coverage
- - POLICY-1773 Enhance the policy/xacml-pdp S3P Stability and Performance tests
- - POLICY-1784 Better Handling of "version" field value with clients
- - POLICY-1785 Deploy same policy with a new version simply adds to the list
- - POLICY-1786 Create a simple way to populate the guard database for testing
- - POLICY-1791 Address Sonar issues in new policy repos
- - POLICY-1795 PAP: bounced apex and xacml pdps show deleted instance in pdp status through APIs.
- - POLICY-1800 API|PAP components use different version formats
- - POLICY-1805 Build up stability test for api component to follow S3P requirements
- - POLICY-1806 Build up S3P performance test for api component
- - POLICY-1847 Add control loop coordination as a preloaded policy type
- - POLICY-1871 Change policy/distribution to support ToscaPolicyType & ToscaPolicy
- - POLICY-1881 Upgrade policy/distribution to latest SDC artifacts
- - POLICY-1885 Apex-pdp: Extend CLIEditor to generate policy in ToscaServiceTemplate format
- - POLICY-1898 Move apex-pdp & distribution documents to policy/parent
- - POLICY-1942 Boost policy/apex-pdp JUnit code coverage
- - POLICY-1953 Create addTopic taking BusTopicParams instead of Properties in policy/endpoints
+ - POLICY-969 Docker improvement in policy framwork modules
+ - POLICY-1074 Fix checkstyle warnings in every repository
+ - POLICY-1121 RPM build for Apex
+ - POLICY-1223 CII Silver Badging Requirements
+ - POLICY-1600 Clean up hash code equality checks, cloning and copying in policy-models
+ - POLICY-1646 Replace uses of getCanonicalName() with getName()
+ - POLICY-1652 Move PapRestServer to policy/common
+ - POLICY-1732 Enable maven-checkstyle-plugin in apex-pdp
+ - POLICY-1737 Upgrade oParent 2.0.0 - change daily jobs to staging jobs
+ - POLICY-1742 Make HTTP return code handling configurable in APEX
+ - POLICY-1743 Make URL configurable in REST Requestor and REST Client
+ - POLICY-1744 Remove topic.properties and incorporate into overall properties
+ - POLICY-1770 PAP REST API for PDPGroup Healthcheck
+ - POLICY-1771 Boost policy/api JUnit code coverage
+ - POLICY-1772 Boost policy/xacml-pdp JUnit code coverage
+ - POLICY-1773 Enhance the policy/xacml-pdp S3P Stability and Performance tests
+ - POLICY-1784 Better Handling of "version" field value with clients
+ - POLICY-1785 Deploy same policy with a new version simply adds to the list
+ - POLICY-1786 Create a simple way to populate the guard database for testing
+ - POLICY-1791 Address Sonar issues in new policy repos
+ - POLICY-1795 PAP: bounced apex and xacml pdps show deleted instance in pdp status through APIs.
+ - POLICY-1800 API|PAP components use different version formats
+ - POLICY-1805 Build up stability test for api component to follow S3P requirements
+ - POLICY-1806 Build up S3P performance test for api component
+ - POLICY-1847 Add control loop coordination as a preloaded policy type
+ - POLICY-1871 Change policy/distribution to support ToscaPolicyType & ToscaPolicy
+ - POLICY-1881 Upgrade policy/distribution to latest SDC artifacts
+ - POLICY-1885 Apex-pdp: Extend CLIEditor to generate policy in ToscaServiceTemplate format
+ - POLICY-1898 Move apex-pdp & distribution documents to policy/parent
+ - POLICY-1942 Boost policy/apex-pdp JUnit code coverage
+ - POLICY-1953 Create addTopic taking BusTopicParams instead of Properties in policy/endpoints
- - POLICY-1270 Policy Lifecycle API RESTful HealthCheck/Statistics Main Entry Point
- - POLICY-1271 PAP RESTful HealthCheck/Statistics Main Entry Point
- - POLICY-1272 Create the S3P JMeter tests for API, PAP, XACML (2nd Gen)
- - POLICY-1273 Policy Type Application Design Requirements
- - POLICY-1436 XACML PDP RESTful HealthCheck/Statistics Main Entry Point
- - POLICY-1440 XACML PDP RESTful Decision API Main Entry Point
- - POLICY-1441 Policy Lifecycle API RESTful Create/Read Main Entry Point for Policy Types
- - POLICY-1442 Policy Lifecycle API RESTful Create/Read Main Entry Point for Concrete Policies
- - POLICY-1443 PAP Dmaap PDP Register/UnRegister Main Entry Point
- - POLICY-1444 PAP Dmaap Policy Deploy/Undeploy Policies Main Entry Point
- - POLICY-1445 XACML PDP upgrade to xacml 2.0.0
- - POLICY-1446 Policy Lifecycle API RESTful Delete Main Entry Point for Policy Types
- - POLICY-1447 Policy Lifecycle API RESTful Delete Main Entry Point for Concrete Policies
- - POLICY-1449 XACML PDP Dmaap Register/UnRegister Functionality
- - POLICY-1451 XACML PDP Dmaap Deploy/UnDeploy Functionality
- - POLICY-1452 Apex PDP Dmaap Register/UnRegister Functionality
- - POLICY-1453 Apex PDP Dmaap Deploy/UnDeploy Functionality
- - POLICY-1454 Drools PDP Dmaap Register/UnRegister Functionality
- - POLICY-1455 Drools PDP Dmaap Deploy/UnDeploy Functionality
- - POLICY-1456 Policy Architecture and Roadmap Documentation
- - POLICY-1458 Create S3P JMeter Tests for Policy API
- - POLICY-1460 Create S3P JMeter Tests for PAP
- - POLICY-1461 Create S3P JMeter Tests for Policy XACML Engine (2nd Generation)
- - POLICY-1462 Create S3P JMeter Tests for Policy SDC Distribution
- - POLICY-1471 Policy Application Designer - Develop Guard and Control Loop Coordination Policy Type application
- - POLICY-1474 Modifications of Control Loop Operational Policy to support new Policy Lifecycle API
- - POLICY-1515 Prototype Policy Lifecycle API Swagger Entry Points
- - POLICY-1516 Prototype the Policy Decision API
- - POLICY-1541 PAP REST API for PDPGroup Query, Statistics & Delete
- - POLICY-1542 PAP REST API for PDPGroup Deployment, State Management & Health Check
+ - POLICY-1270 Policy Lifecycle API RESTful HealthCheck/Statistics Main Entry Point
+ - POLICY-1271 PAP RESTful HealthCheck/Statistics Main Entry Point
+ - POLICY-1272 Create the S3P JMeter tests for API, PAP, XACML (2nd Gen)
+ - POLICY-1273 Policy Type Application Design Requirements
+ - POLICY-1436 XACML PDP RESTful HealthCheck/Statistics Main Entry Point
+ - POLICY-1440 XACML PDP RESTful Decision API Main Entry Point
+ - POLICY-1441 Policy Lifecycle API RESTful Create/Read Main Entry Point for Policy Types
+ - POLICY-1442 Policy Lifecycle API RESTful Create/Read Main Entry Point for Concrete Policies
+ - POLICY-1443 PAP Dmaap PDP Register/UnRegister Main Entry Point
+ - POLICY-1444 PAP Dmaap Policy Deploy/Undeploy Policies Main Entry Point
+ - POLICY-1445 XACML PDP upgrade to xacml 2.0.0
+ - POLICY-1446 Policy Lifecycle API RESTful Delete Main Entry Point for Policy Types
+ - POLICY-1447 Policy Lifecycle API RESTful Delete Main Entry Point for Concrete Policies
+ - POLICY-1449 XACML PDP Dmaap Register/UnRegister Functionality
+ - POLICY-1451 XACML PDP Dmaap Deploy/UnDeploy Functionality
+ - POLICY-1452 Apex PDP Dmaap Register/UnRegister Functionality
+ - POLICY-1453 Apex PDP Dmaap Deploy/UnDeploy Functionality
+ - POLICY-1454 Drools PDP Dmaap Register/UnRegister Functionality
+ - POLICY-1455 Drools PDP Dmaap Deploy/UnDeploy Functionality
+ - POLICY-1456 Policy Architecture and Roadmap Documentation
+ - POLICY-1458 Create S3P JMeter Tests for Policy API
+ - POLICY-1460 Create S3P JMeter Tests for PAP
+ - POLICY-1461 Create S3P JMeter Tests for Policy XACML Engine (2nd Generation)
+ - POLICY-1462 Create S3P JMeter Tests for Policy SDC Distribution
+ - POLICY-1471 Policy Application Designer - Develop Guard and Control Loop Coordination Policy Type application
+ - POLICY-1474 Modifications of Control Loop Operational Policy to support new Policy Lifecycle API
+ - POLICY-1515 Prototype Policy Lifecycle API Swagger Entry Points
+ - POLICY-1516 Prototype the Policy Decision API
+ - POLICY-1541 PAP REST API for PDPGroup Query, Statistics & Delete
+ - POLICY-1542 PAP REST API for PDPGroup Deployment, State Management & Health Check
- - POLICY-1410 List Policy API
- - POLICY-1413 Dashboard enhancements
- - POLICY-1414 Push Policy and DeletePolicy API enhancement
- - POLICY-1416 Model enhancements to support CLAMP
- - POLICY-1417 Resiliency improvements
- - POLICY-1418 PDP APIs - make ClientAuth optional
- - POLICY-1419 Better multi-role support
- - POLICY-1420 Model enhancement to support embedded JSON
- - POLICY-1421 New audit data for push/delete
- - POLICY-1422 Enhanced encryption
- - POLICY-1423 Save original model file
- - POLICY-1427 Controller Logging Feature
- - POLICY-1489 PDP-D: Nested JSON Event Filtering support with JsonPath
- - POLICY-1499 Mdc Filter Feature
+ - POLICY-1410 List Policy API
+ - POLICY-1413 Dashboard enhancements
+ - POLICY-1414 Push Policy and DeletePolicy API enhancement
+ - POLICY-1416 Model enhancements to support CLAMP
+ - POLICY-1417 Resiliency improvements
+ - POLICY-1418 PDP APIs - make ClientAuth optional
+ - POLICY-1419 Better multi-role support
+ - POLICY-1420 Model enhancement to support embedded JSON
+ - POLICY-1421 New audit data for push/delete
+ - POLICY-1422 Enhanced encryption
+ - POLICY-1423 Save original model file
+ - POLICY-1427 Controller Logging Feature
+ - POLICY-1489 PDP-D: Nested JSON Event Filtering support with JsonPath
+ - POLICY-1499 Mdc Filter Feature
- - POLICY-1159 Move expectException to policy-common/utils-test
- - POLICY-1176 Work on technical debt introduced by CLC POC
- - POLICY-1266 A&AI Modularity
- - POLICY-1274 further improvement in PSSD S3P test
- - POLICY-1401 Build onap.policies.Monitoring TOSCA Policy Template
- - POLICY-1465 Support configurable Heap Memory Settings for JVM processes
+ - POLICY-1159 Move expectException to policy-common/utils-test
+ - POLICY-1176 Work on technical debt introduced by CLC POC
+ - POLICY-1266 A&AI Modularity
+ - POLICY-1274 further improvement in PSSD S3P test
+ - POLICY-1401 Build onap.policies.Monitoring TOSCA Policy Template
+ - POLICY-1465 Support configurable Heap Memory Settings for JVM processes
- - POLICY-238 policy/drools-applications: clean up maven structure
- - POLICY-336 Address Technical Debt
- - POLICY-338 Address JUnit Code Coverage
- - POLICY-377 Policy Create API should validate input matches DCAE microservice template
- - POLICY-389 Cleanup Jenkin's CI/CD process's
- - POLICY-449 Policy API + Console : Common Policy Validation
- - POLICY-568 Integration with org.onap AAF project
- - POLICY-610 Support vDNS scale out for multiple times in Beijing release
+ - POLICY-238 policy/drools-applications: clean up maven structure
+ - POLICY-336 Address Technical Debt
+ - POLICY-338 Address JUnit Code Coverage
+ - POLICY-377 Policy Create API should validate input matches DCAE microservice template
+ - POLICY-389 Cleanup Jenkin's CI/CD process's
+ - POLICY-449 Policy API + Console : Common Policy Validation
+ - POLICY-568 Integration with org.onap AAF project
+ - POLICY-610 Support vDNS scale out for multiple times in Beijing release
- - POLICY-527 Platform Maturity Resiliency - Policy Engine GUI and PAP
- - POLICY-528 Platform Maturity Resiliency - Drools PDP
- - POLICY-569 Platform Maturity Resiliency - BRMS Gateway
- - POLICY-585 Platform Maturity Resiliency - XACML PDP
- - POLICY-586 Platform Maturity Resiliency - Planning
- - POLICY-681 Regression Test Use Cases
+ - POLICY-527 Platform Maturity Resiliency - Policy Engine GUI and PAP
+ - POLICY-528 Platform Maturity Resiliency - Drools PDP
+ - POLICY-569 Platform Maturity Resiliency - BRMS Gateway
+ - POLICY-585 Platform Maturity Resiliency - XACML PDP
+ - POLICY-586 Platform Maturity Resiliency - Planning
+ - POLICY-681 Regression Test Use Cases
- Create a VNF Instance via VID.
- Preload SDNC with topology data used for the actual VNF instantiation (both base and DNS scaling modules). NOTE: you may want to set "vlb_name_0" in the base VF module data to something unique. This is the vLB server name that DCAE will pass to Policy during closed loop. If the same name is used multiple times, the Policy name-query to AAI will show multiple entries, one for each occurrence of that vLB VM name in the OpenStack zone. Note that this is not a limitation, typically server names in a domain are supposed to be unique.
- Instantiate the base VF module (vLB, vPacketGen, and one vDNS) via VID. NOTE: The name of the VF module MUST start with ``Vfmodule_``. The same name MUST appear in the SDNC preload of the base VF module topology. We'll relax this naming requirement for Beijing Release.
- Create a VNF Instance via VID.
- Preload SDNC with topology data used for the actual VNF instantiation (both base and DNS scaling modules). NOTE: you may want to set "vlb_name_0" in the base VF module data to something unique. This is the vLB server name that DCAE will pass to Policy during closed loop. If the same name is used multiple times, the Policy name-query to AAI will show multiple entries, one for each occurrence of that vLB VM name in the OpenStack zone. Note that this is not a limitation, typically server names in a domain are supposed to be unique.
- Instantiate the base VF module (vLB, vPacketGen, and one vDNS) via VID. NOTE: The name of the VF module MUST start with ``Vfmodule_``. The same name MUST appear in the SDNC preload of the base VF module topology. We'll relax this naming requirement for Beijing Release.
-.. For initial document: list epic and user stories for each, list user stories with no epics.
-.. For Bugs section, list bugs where Affected Version is a prior release (Casablanca, Beijing etc), Fixed Version is the current release (Dublin), Resolution is done.
-.. For Known issues, list bugs that are slotted for a future release.
+.. For initial document: list epic and user stories for each, list user stories with no epics.
+.. For Bugs section, list bugs where Affected Version is a prior release (Casablanca, Beijing etc), Fixed Version is the current release (Dublin), Resolution is done.
+.. For Known issues, list bugs that are slotted for a future release.