1 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
7 .. * This Release Notes must be updated each time the team decides to Release new artifacts.
8 .. * The scope of these Release Notes are for ONAP POLICY. In other words, each ONAP component has its Release Notes.
9 .. * This Release Notes is cumulative, the most recently Released artifact is made visible in the top of
10 .. * this Release Notes.
11 .. * Except the date and the version number, all the other sections are optional but there must be at least
12 .. * one section describing the purpose of this new release.
13 .. * This note must be removed after content has been added.
16 .. ==========================
17 .. * * * CASABLANCA * * *
18 .. ==========================
23 :Release Date: 2018-11-15 (Casablanca Release)
27 The Casablanca release for POLICY delivered the following Epics. For a full list of stories and tasks delivered in the Casablanca release, refer to `JiraPolicyCasablanca`_ (Note: Jira details can also be viewed from this link).
29 * [POLICY-701] - This epic covers the work to integrate Policy into the SDC Service Distribution
30 - POLICY-723 Analyze and design the Policy SDC Distribution Application
31 - POLICY-922 Create application framework for Policy Service SDC Distribution
32 - POLICY-923 Create code to generate docker images for Policy SDC Service Distribution application
33 - POLICY-924 Create CSIT test framework for Policy SDC Service Distribution application
34 - POLICY-925 Create K8S Helm Charts for deployment via OOM project
35 - POLICY-926 Create code infrastructure for automatic policy forwarding
36 - POLICY-956 Implement IConfiguration interface to initiate Distribution Client
37 - POLICY-974 Implement INotificationCallback interface
38 - POLICY-1094 Refactor reception handler configuration parameter handling
40 * [POLICY-715] - This epic covers work to harden the policy platform
41 - POLICY-955 Incorporate changes to amsterdam rules template into casablanca rules template
43 * [POLICY-718] - This epic covers the work to perform release planning activities.
44 - POLICY-875 Update Beijing Branch and master branch for Casablanca versions
45 - POLICY-1040 Copy and clean up Beijing wiki's for Casablanca
47 * [POLICY-719] - This epic covers the work to build the Policy Lifecycle API
48 - POLICY-724 Gather requirements and design high-level software architecture
49 - POLICY-1056 Create Policy API Infrastructure
51 * [POLICY-726] - This epic covers the work to distribute policy from the PAP to the PDPs into the ONAP platform
52 - POLICY-874 Spike: Interface Stubbing for Architectual Enhancements
54 * [POLICY-772] - Enhance casablanca testing abilities between various environments
56 * [POLICY-803] - All the new repositories must be initialized and setup to work under policy/parent.
57 - POLICY-804 Setup policy/parent
58 - POLICY-805 Setup policy/models
59 - POLICY-806 Setup policy/api
60 - POLICY-807 Setup policy/apex-pdp
61 - POLICY-808 Setup ci-management verify/merge jobs
62 - POLICY-845 Setup policy/core
63 - POLICY-846 Setup policy/xacml-pdp
64 - POLICY-847 Setup policy/gui
65 - POLICY-848 Setup policy/pap
66 - POLICY-849 Setup policy/pdp
67 - POLICY-871 Setup policy/distribution
69 * [POLICY-809] - Maintain and implement performance
70 - POLICY-888 Performance PDP-D - Policy Decision/Enforcement
72 * [POLICY-814] - 72 hour stability testing (component and platform)
73 - POLICY-815 Stability PDP-X
75 * [POLICY-819] - Maintain and implement resiliency
76 * [POLICY-824] - maintain and implement security
77 - POLICY-781 PE Support for AAF Root Certificate in HTTPS communication.
78 - POLICY-905 Fix apex-engine License and Security issues
79 - POLICY-913 policy/engine CADI (AAF) Integration
80 - POLICY-914 policy/drools-pdp CADI (AAF) Integration
81 - POLICY-918 Policy Portal GUI - upgrade to latest Portal SDK to resolve security issues
82 - POLICY-942 BRMSGW: HTTPS support for DMaaP/UEB interfaces
83 - POLICY-946 Investigate what integration of CADI (AAF) integration into the ONAP Policy Platform components really means
84 - POLICY-982 Update security issues since portal SDK was upgraded
85 - POLICY-1030 Revisit CLM reports due to new software upgrade
86 - POLICY-1059 Address the security issues with Severe (and above) Level 4-6
88 * [POLICY-825] - Maintain and implement scability
89 * [POLICY-829] - Maintain and implement manageability
90 * [POLICY-839] - Maintain and implement usability
91 * [POLICY-840] - Flexible control loop coordination facility.
92 - POLICY-951 Code placement and development procedures
93 - POLICY-952 Analyze and design the control loop coordination facility
94 - POLICY-953 Configure whether a given control loop will be regulated by flexible control loop coordination.
95 - POLICY-975 Storage of abatement (and other) events in historical database
96 - POLICY-1109 Add demo code to template.demo
98 * [POLICY-841] - Covers the work required to support HPA
99 - POLICY-927 Develop the code that translates HPA requirements into OOF policies
100 - POLICY-989 HPA Use Case Modeling work to support optimization policies
102 * [POLICY-842] - This epic covers the work to support the Auto Scale Out functional requirements
103 - POLICY-962 Change SO Scale Out REST API call to new REST API version that support config parameters
104 - POLICY-963 Understand and Scope the Guard Policies for Scale Out
105 - POLICY-964 Modify drools-applications template to check is PROV_STATUS=Active before performing a Scale Out
106 - POLICY-968 Enforce guard policy for min/max instances of a VNF
107 - POLICY-1010 Enforce guard policy for waiting a period of time between Scale Outs
108 - POLICY-1011 Modify drools-applications template to make A&AI query to count number of instances of a VNF
109 - POLICY-1037 Use A&AI query for getting number of module instances to construct new module instance name
110 - POLICY-1038 Create new min/max guard policy template in policy engine
111 - POLICY-1039 Ensure Policy Integration Test wiki is up-to-date for new Scale Out APIs
113 * [POLICY-851] - This epic covers the work to bring in the Apex PDP code
114 - POLICY-855 Verify APEX-PDP setup in ONAP
115 - POLICY-856 Bring in the model code for APEX-PDP into ONAP
116 - POLICY-857 Bring in the context code for APEX-PDP into ONAP
117 - POLICY-858 Bring in the core code for APEX-PDP into ONAP
118 - POLICY-859 Bring in the server service code for APEX-PDP into ONAP
119 - POLICY-860 Bring in the authoring code for APEX-PDP into ONAP
120 - POLICY-861 Bring in the domain example code for APEX-PDP into ONAP
121 - POLICY-862 Bring in the plugin code for APEX-PDP into ONAP
122 - POLICY-863 Bring in the application code for APEX-PDP into ONAP
123 - POLICY-864 Bring in the client code for APEX-PDP into ONAP
124 - POLICY-865 Set up Integration Tests for APEX in ONAP
125 - POLICY-866 Set up ONAP Policy Framework compliant Docker build for APEX-PDP
126 - POLICY-867 Bring in APEX-PDP documents
127 - POLICY-954 APEX: Missing items and configuration problems
128 - POLICY-1099 Create CSIT test for policy APEX PDP
130 * [POLICY-876] - This epics covers the work to re-build how the PAP organizes the PDP's into groups.
131 * [POLICY-904] - This epic covers the features AT&T is submitting
132 - POLICY-900 TOSCA model enhancements
133 - POLICY-901 Guard policy UI enhancements
134 - POLICY-902 XACML platform enhancements
135 - POLICY-983 getConfig naming policy implementation
136 - POLICY-1042 Policy Dashboard Enhancment
138 * [POLICY-1081] - This epic covers the contribution for the 5G OOF PCI Optimization use case.
139 - POLICY-1079 Add support for VF Module Delete recipe
140 - POLICY-1086 Configuration/policies for OOF PCI use case
141 - POLICY-1089 Handle recommendation for PCI updates received from PCI-Handler MS
142 * [POLICY-1182] - Covers the work to support CCVPN use case
146 The following bug fixes have been deployed with this release:
148 * `[POLICY-909] <https://jira.onap.org/browse/POLICY-909>`_ - get_ZoneDictionaryDataByName class type error
149 * `[POLICY-1085] <https://jira.onap.org/browse/POLICY-1085>`_ - Stand-alone install will not run
150 * `[POLICY-1106] <https://jira.onap.org/browse/POLICY-1106>`_ - Checkstyle fixes appear to have broken persistence
151 * `[POLICY-1117] <https://jira.onap.org/browse/POLICY-1117>`_ - Fixed a bug on import function
152 * `[POLICY-1118] <https://jira.onap.org/browse/POLICY-1118>`_ - Microservice policies failing to display dynamic fields when selecting any model from GUI
153 * `[POLICY-1154] <https://jira.onap.org/browse/POLICY-1154>`_ - PE: CONSOLE not working with latest code changes
154 * `[POLICY-1155] <https://jira.onap.org/browse/POLICY-1155>`_ - PDP-D [APPS] : DRL Templates Compilation Errors
155 * `[POLICY-1158] <https://jira.onap.org/browse/POLICY-1158>`_ - meet ASDC_AUTHORIZATION_FAILED for client setting
156 * `[POLICY-1160] <https://jira.onap.org/browse/POLICY-1160>`_ - meet nullPointer exception based on the new schema of HPA capability requirement
157 * `[POLICY-1192] <https://jira.onap.org/browse/POLICY-1192>`_ - Update portal.properties in PE for AAF integration
158 * `[POLICY-1193] <https://jira.onap.org/browse/POLICY-1193>`_ - Policy: Heat Installation: policy host in certificate was generated incorrectly
159 * `[POLICY-1194] <https://jira.onap.org/browse/POLICY-1194>`_ - Policy: Heat installation: reconfigure URLs to point to a DNS hostname that matches the DMaaP certificate
160 * `[POLICY-1198] <https://jira.onap.org/browse/POLICY-1198>`_ - POLICY: OOM: PAP: cannot talk https directly to PDP-X pod bypassing service
161 * `[POLICY-1200] <https://jira.onap.org/browse/POLICY-1200>`_ - meet NullPointerException error since the PolicyScope should be set a default value
162 * `[POLICY-1201] <https://jira.onap.org/browse/POLICY-1201>`_ - Error while forwarding policy from policy-distribution to apex-pdp
163 * `[POLICY-1204] <https://jira.onap.org/browse/POLICY-1204>`_ - PAPLP: invalid schema database errors
168 POLICY code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The POLICY open Critical security vulnerabilities and their risk assessment have been documented as part of the `project (Casablanca Release) <https://wiki.onap.org/pages/viewpage.action?pageId=36964976>`_.
171 - `POLICY project page <https://wiki.onap.org/display/DW/Policy+Framework+Project>`_
173 - `Passing Badge information for POLICY <https://bestpractices.coreinfrastructure.org/en/projects/1614>`_
175 - `Project Vulnerability Review Table for POLICY (Casablanca Release) <https://wiki.onap.org/pages/viewpage.action?pageId=36964976>`_
179 The following known issues will be addressed in a future release:
180 * to be determined ...
185 .. =======================
186 .. * * * BEIJING * * *
187 .. =======================
192 :Release Date: 2018-06-07 (Beijing Release)
196 The Beijing release for POLICY delivered the following Epics. For a full list of stories and tasks delivered in the Beijing release, refer to `JiraPolicyBeijing`_.
198 * [POLICY-390] - This epic covers the work to harden the Policy platform software base (incl 50% JUnit coverage)
199 - POLICY-238 policy/drools-applications: clean up maven structure
200 - POLICY-336 Address Technical Debt
201 - POLICY-338 Address JUnit Code Coverage
202 - POLICY-377 Policy Create API should validate input matches DCAE microservice template
203 - POLICY-389 Cleanup Jenkin's CI/CD process's
204 - POLICY-449 Policy API + Console : Common Policy Validation
205 - POLICY-568 Integration with org.onap AAF project
206 - POLICY-610 Support vDNS scale out for multiple times in Beijing release
208 * [POLICY-391] - This epic covers the work to support Release Planning activities
209 - POLICY-552 ONAP Licensing Scan - Use Restrictions
211 * [POLICY-392] - Platform Maturity Requirements - Performance Level 1
212 - POLICY-529 Platform Maturity Performance - Drools PDP
213 - POLICY-567 Platform Maturity Performance - PDP-X
215 * [POLICY-394] - This epic covers the work required to support a Policy developer environment in which Policy Developers can create, update policy templates/rules separate from the policy Platform runtime platform.
216 - POLICY-488 pap should not add rules to official template provided in drools applications
218 * [POLICY-398] - This epic covers the body of work involved in supporting policy that is platform specific.
219 - POLICY-434 need PDP /getConfig to return an indicator of where to find the config data - in config.content versus config field
221 * [POLICY-399] - This epic covers the work required to policy enable Hardware Platform Enablement
222 - POLICY-622 Integrate OOF Policy Model into Policy Platform
224 * [POLICY-512] - This epic covers the work to support Platform Maturity Requirements - Stability Level 1
225 - POLICY-525 Platform Maturity Stability - Drools PDP
226 - POLICY-526 Platform Maturity Stability - XACML PDP
228 * [POLICY-513] - Platform Maturity Requirements - Resiliency Level 2
229 - POLICY-527 Platform Maturity Resiliency - Policy Engine GUI and PAP
230 - POLICY-528 Platform Maturity Resiliency - Drools PDP
231 - POLICY-569 Platform Maturity Resiliency - BRMS Gateway
232 - POLICY-585 Platform Maturity Resiliency - XACML PDP
233 - POLICY-586 Platform Maturity Resiliency - Planning
234 - POLICY-681 Regression Test Use Cases
236 * [POLICY-514] - This epic covers the work to support Platform Maturity Requirements - Security Level 1
237 - POLICY-523 Platform Maturity Security - CII Badging - Project Website
239 * [POLICY-515] - This epic covers the work to support Platform Maturity Requirements - Escalability Level 1
240 - POLICY-531 Platform Maturity Scalability - XACML PDP
241 - POLICY-532 Platform Maturity Scalability - Drools PDP
242 - POLICY-623 Docker image re-design
244 * [POLICY-516] - This epic covers the work to support Platform Maturity Requirements - Manageability Level 1
245 - POLICY-533 Platform Maturity Manageability L1 - Logging
246 - POLICY-534 Platform Maturity Manageability - Instantiation < 1 hour
248 * [POLICY-517] - This epic covers the work to support Platform Maturity Requirements - Usability Level 1
249 - POLICY-535 Platform Maturity Usability - User Guide
250 - POLICY-536 Platform Maturity Usability - Deployment Documentation
251 - POLICY-537 Platform Maturity Usability - API Documentation
253 * [POLICY-546] - R2 Beijing - Various enhancements requested by clients to the way we handle TOSCA models.
258 The following bug fixes have been deployed with this release:
260 * `[POLICY-484] <https://jira.onap.org/browse/POLICY-484>`_ - Extend election handler run window and clean up error messages
261 * `[POLICY-494] <https://jira.onap.org/browse/POLICY-494>`_ - POLICY EELF Audit.log not in ECOMP Standards Compliance
262 * `[POLICY-501] <https://jira.onap.org/browse/POLICY-501>`_ - Fix issues blocking election handler and add directed interface for opstate
263 * `[POLICY-509] <https://jira.onap.org/browse/POLICY-509>`_ - Add IntelliJ file to .gitingore
264 * `[POLICY-510] <https://jira.onap.org/browse/POLICY-510>`_ - Do not enforce hostname validation
265 * `[POLICY-518] <https://jira.onap.org/browse/POLICY-518>`_ - StateManagement creation of EntityManagers.
266 * `[POLICY-519] <https://jira.onap.org/browse/POLICY-519>`_ - Correctly initialize the value of allSeemsWell in DroolsPdpsElectionHandler
267 * `[POLICY-629] <https://jira.onap.org/browse/POLICY-629>`_ - Fixed a bug on editor screen
268 * `[POLICY-684] <https://jira.onap.org/browse/POLICY-684>`_ - Fix regex for brmsgw dependency handling
269 * `[POLICY-707] <https://jira.onap.org/browse/POLICY-707>`_ - ONAO-PAP-REST unit tests fail on first build on clean checkout
270 * `[POLICY-717] <https://jira.onap.org/browse/POLICY-717>`_ - Fix a bug in checking required fields if the object has include function
271 * `[POLICY-734] <https://jira.onap.org/browse/POLICY-734>`_ - Fix Fortify Header Manipulation Issue
272 * `[POLICY-743] <https://jira.onap.org/browse/POLICY-743>`_ - Fixed data name since its name was changed on server side
273 * `[POLICY-753] <https://jira.onap.org/browse/POLICY-753>`_ - Policy Health Check failed with multi-node cluster
274 * `[POLICY-765] <https://jira.onap.org/browse/POLICY-765>`_ - junit test for guard fails intermittently
279 POLICY code has been formally scanned during build time using NexusIQ and all Critical vulnerabilities have been addressed, items that remain open have been assessed for risk and determined to be false positive. The POLICY open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=25437092>`_.
282 - `POLICY project page <https://wiki.onap.org/display/DW/Policy+Framework+Project>`_
284 - `Passing Badge information for POLICY <https://bestpractices.coreinfrastructure.org/en/projects/1614>`_
286 - `Project Vulnerability Review Table for POLICY <https://wiki.onap.org/pages/viewpage.action?pageId=25437092>`_
290 The following known issues will be addressed in a future release:
292 * `[POLICY-522] <https://jira.onap.org/browse/POLICY-522>`_ - PAP REST APIs undesired HTTP response body for 500 responses
293 * `[POLICY-608] <https://jira.onap.org/browse/POLICY-608>`_ - xacml components : remove hardcoded secret key from source code
294 * `[POLICY-764] <https://jira.onap.org/browse/POLICY-764>`_ - Policy Engine PIP Configuration JUnit Test fails intermittently
295 * `[POLICY-776] <https://jira.onap.org/browse/POLICY-776>`_ - OOF Policy TOSCA models are not correctly rendered
296 * `[POLICY-799] <https://jira.onap.org/browse/POLICY-799>`_ - Policy API Validation Does Not Validate Required Parent Attributes in the Model
297 * `[POLICY-801] <https://jira.onap.org/browse/POLICY-801>`_ - fields mismatch for OOF flavorFeatures between implementation and wiki
298 * `[POLICY-869] <https://jira.onap.org/browse/POLICY-869>`_ - Control Loop Drools Rules should not have exceptions as well as die upon an exception
299 * `[POLICY-872] <https://jira.onap.org/browse/POLICY-872>`_ - investigate potential race conditions during rules version upgrades during call loads
307 :Release Date: 2018-01-18 (Amsterdam Maintenance Release)
311 The following fixes were deployed with the Amsterdam Maintenance Release:
313 * `[POLICY-486] <https://jira.onap.org/browse/POLICY-486>`_ - pdp-x api pushPolicy fails to push latest version
319 :Release Date: 2017-11-16 (Amsterdam Release)
323 The Amsterdam release continued evolving the design driven architecture of and functionality for POLICY. The following is a list of Epics delivered with the release. For a full list of stories and tasks delivered in the Amsterdam release, refer to `JiraPolicyAmsterdam`_.
325 * [POLICY-31] - Stabilization of Seed Code
326 - POLICY-25 Replace any remaining openecomp reference by onap
327 - POLICY-32 JUnit test code coverage
328 - POLICY-66 PDP-D Feature mechanism enhancements
329 - POLICY-67 Rainy Day Decision Policy
330 - POLICY-93 Notification API
331 - POLICY-158 policy/engine: SQL injection Mitigation
332 - POLICY-269 Policy API Support for Rainy Day Decision Policy and Dictionaries
334 * [POLICY-33] - This epic covers the body of work involved in deploying the Policy Platform components
335 - POLICY-40 MSB Integration
336 - POLICY-124 Integration with oparent
337 - POLICY-41 OOM Integration
338 - POLICY-119 PDP-D: noop sinks
340 * [POLICY-34] - This epic covers the work required to support a Policy developer environment in which Policy Developers can create, update policy templates/rules separate from the policy Platform runtime platform.
341 - POLICY-57 VF-C Actor code development
342 - POLICY-43 Amsterdam Use Case Template
343 - POLICY-173 Deployment of Operational Policies Documentation
345 * [POLICY-35] - This epic covers the body of work involved in supporting policy that is platform specific.
346 - POLICY-68 TOSCA Parsing for nested objects for Microservice Policies
348 * [POLICY-36] - This epic covers the work required to capture policy during VNF on-boarding.
350 * [POLICY-37] - This epic covers the work required to capture, update, extend Policy(s) during Service Design.
351 - POLICY-64 CLAMP Configuration and Operation Policies for vFW Use Case
352 - POLICY-65 CLAMP Configuration and Operation Policies for vDNS Use Case
353 - POLICY-48 CLAMP Configuration and Operation Policies for vCPE Use Case
354 - POLICY-63 CLAMP Configuration and Operation Policies for VOLTE Use Case
356 * [POLICY-38] - This epic covers the work required to support service distribution by SDC.
358 * [POLICY-39] - This epic covers the work required to support the Policy Platform during runtime.
359 - POLICY-61 vFW Use Case - Runtime
360 - POLICY-62 vDNS Use Case - Runtime
361 - POLICY-59 vCPE Use Case - Runtime
362 - POLICY-60 VOLTE Use Case - Runtime
363 - POLICY-51 Runtime Policy Update Support
364 - POLICY-328 vDNS Use Case - Runtime Testing
365 - POLICY-324 vFW Use Case - Runtime Testing
366 - POLICY-320 VOLTE Use Case - Runtime Testing
367 - POLICY-316 vCPE Use Case - Runtime Testing
369 * [POLICY-76] - This epic covers the body of work involved in supporting R1 Amsterdam Milestone Release Planning Milestone Tasks.
370 - POLICY-77 Functional Test case definition for Control Loops
371 - POLICY-387 Deliver the released policy artifacts
375 - This is technically the first release of POLICY, previous release was the seed code contribution. As such, the defects fixed in this release were raised during the course of the release. Anything not closed is captured below under Known Issues. For a list of defects fixed in the Amsterdam release, refer to `JiraPolicyAmsterdam`_.
379 - The operational policy template has been tested with the vFW, vCPE, vDNS and VOLTE use cases. Additional development may/may not be required for other scenarios.
381 - For vLBS Use Case, the following steps are required to setup the service instance:
382 - Create a Service Instance via VID.
383 - Create a VNF Instance via VID.
384 - 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.
385 - 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.
386 - Run heatbridge from the Robot VM using ``Vfmodule_`` … as stack name (it is the actual stack name in OpenStack)
387 - Populate AAI with a dummy VF module for vDNS scaling.
396 .. Links to jira release notes
398 .. _JiraPolicyCasablanca: https://jira.onap.org/secure/ReleaseNote.jspa?projectId=10106&version=10446
399 .. _JiraPolicyBeijing: https://jira.onap.org/secure/ReleaseNote.jspa?projectId=10106&version=10349
400 .. _JiraPolicyAmsterdam: https://jira.onap.org/secure/ReleaseNote.jspa?projectId=10106&version=10300
405 .. 10/08/2018 - Initial document for Casablanca release.
406 .. Per Jorge, POLICY-785 did not get done in Casablanca (removed).
407 .. 03/22/2018 - Initial document for Beijing release.
408 .. 01/15/2018 - Added change for version 1.1.3 to the Amsterdam branch. Also corrected prior version (1.2.0) to (1.1.1)
409 .. Also, Set up initial information for Beijing.
410 .. 05/29/2018 - Information for Beijing release.
411 .. Excluded POLICY-454 from bug list since it doesn't apply to Beijing per Jorge.
416 .. How to notes for SS
417 .. For initial document: list epic and user stories for each, list user stories with no epics.
418 .. For Bugs section, list bugs that are not tied to an epic. Remove all items with "Won't Do" resolution.
419 .. For Known issues, list bugs that are slotted for a future release.