Release Notes - Policy Framework - Version Amsterdam Release - HTML format

Epic

  • [POLICY-31] - Stabilization of Seed Code
  • [POLICY-33] - This epic covers the body of work involved in deploying the Policy Platform components
  • [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.
  • [POLICY-35] - This epic covers the body of work involved in supporting policy that is platform specific.
  • [POLICY-36] - This epic covers the work required to capture policy during VNF on-boarding.
  • [POLICY-37] - This epic covers the work required to capture, update, extend Policy(s) during Service Design.
  • [POLICY-38] - This epic covers the work required to support service distribution by SDC.
  • [POLICY-39] - This epic covers the work required to support the Policy Platform during runtime.
  • [POLICY-76] - This epic covers the body of work involved in supporting R1 Amsterdam Milestone Release Planning Milestone Tasks.

Story

  • [POLICY-25] - Replace any remaining openecomp reference by onap
  • [POLICY-32] - JUnit test code coverage
  • [POLICY-40] - MSB Integration
  • [POLICY-41] - OOM Integration
  • [POLICY-43] - Amsterdam Use Case Template
  • [POLICY-48] - CLAMP Configuration and Operation Policies for vCPE Use Case
  • [POLICY-51] - Runtime Policy Update Support
  • [POLICY-57] - VF-C Actor code development
  • [POLICY-59] - vCPE Use Case - Runtime
  • [POLICY-60] - VOLTE Use Case - Runtime
  • [POLICY-61] - vFW Use Case - Runtime
  • [POLICY-62] - vDNS Use Case - Runtime
  • [POLICY-63] - CLAMP Configuration and Operation Policies for VOLTE Use Case
  • [POLICY-64] - CLAMP Configuration and Operation Policies for vFW Use Case
  • [POLICY-65] - CLAMP Configuration and Operation Policies for vDNS Use Case
  • [POLICY-66] - PDP-D Feature mechanism enhancements
  • [POLICY-67] - Rainy Day Decision Policy
  • [POLICY-68] - TOSCA Parsing for nested objects for Microservice Policies
  • [POLICY-77] - Functional Test case definition for Control Loops
  • [POLICY-93] - Notification API
  • [POLICY-119] - PDP-D: noop sinks
  • [POLICY-121] - Update POM to inherit from oparent
  • [POLICY-124] - Integration with oparent
  • [POLICY-158] - policy/engine: SQL injection Mitigation
  • [POLICY-161] - Security Event Logging
  • [POLICY-173] - Deployment of Operational Policies Documentation
  • [POLICY-210] - Independent Versioning and Release Process
  • [POLICY-269] - Policy API Support for Rainy Day Decision Policy and Dictionaries
  • [POLICY-316] - vCPE Use Case - Runtime Testing
  • [POLICY-320] - VOLTE Use Case - Runtime Testing
  • [POLICY-324] - vFW Use Case - Runtime Testing
  • [POLICY-328] - vDNS Use Case - Runtime Testing
  • [POLICY-387] - Deliver the released policy artifacts

Task

  • [POLICY-3] - Add appropriate unit tests back into the distribution
  • [POLICY-6] - Updates to License and Trademark in the Policy Source Code
  • [POLICY-8] - Fix PDP-D Sonar Blocker Issues
  • [POLICY-9] - Remove warnings for type safety, unused imports, raw types
  • [POLICY-11] - Enhancements to extract fact information for a given Drools Application
  • [POLICY-17] - Removal of ECOMP-SDK-APP dbscripts
  • [POLICY-18] - Enhancement: Add additional feature hooks in Drools PDP
  • [POLICY-22] - drools-applications reorganization and template upgrade
  • [POLICY-26] - PDP-D Telemetry REST CLI
  • [POLICY-30] - PDP-D Logging Enhancements
  • [POLICY-53] - Update drools-application docker scripts to find reorganized pom changes
  • [POLICY-54] - POLICY-54 Add HTTP Proxy Support to docker image builds
  • [POLICY-55] - Ensure drools-application JUnit test works on ONAP JJB using in memory database
  • [POLICY-58] - Update Policy Engine dependencies and use case policies to support the latest drools-application code
  • [POLICY-70] - Add vagrant functionality to build/setup policy
  • [POLICY-78] - Update Drools version to 6.5.0.Final
  • [POLICY-80] - Policy Guard
  • [POLICY-87] - Implement Recommended Fix for Portal
  • [POLICY-88] - Delete the yaml sdk and sdc projects located in policy/engine
  • [POLICY-95] - Fix policy/commons sonar blocker issues with exception of integrity-monitor/audit
  • [POLICY-96] - Fix policy/common integrity-[monitor/audit] sonar blockers
  • [POLICY-97] - Fix policy/engine sonar blockers
  • [POLICY-98] - policy/commons critical sonar issues - NON integrity/monitor related
  • [POLICY-100] - fix policy/common critical sonar items - integrity monitor/audit related
  • [POLICY-105] - Common-Modules changes to RefreshStateAudit
  • [POLICY-111] - policy/drools-applications: sonar blockers
  • [POLICY-113] - policy/engine: sonar critical
  • [POLICY-114] - policy/drools-pdp: sonar critical
  • [POLICY-115] - policy/drools-application: sonar critical
  • [POLICY-116] - Remove MojoHaus Maven plug-in from pom file
  • [POLICY-117] - Resolve Policy Sonar Critical issues
  • [POLICY-122] - Policy GUI Fixes for Dictionary and Dashboard tabs
  • [POLICY-125] - Update Project FOSS Table
  • [POLICY-126] - Identify and outline the set of documentations to be delivered in this Release
  • [POLICY-133] - Addition of policy-persistence feature
  • [POLICY-154] - policy/engine finish eclipse warnings for unused imports/variables
  • [POLICY-155] - Addition of state-management feature
  • [POLICY-156] - Addition of active-standby-management feature
  • [POLICY-163] - Add 'install' and 'uninstall' option to DroolsPDP 'features' script
  • [POLICY-167] - Clean additional pom warnings policy/engine
  • [POLICY-168] - Clean pom warnings policy/drools-applications
  • [POLICY-171] - Update policy/docker README to reflect current project paths
  • [POLICY-176] - policy/drools-applications: convert System.out, System.err to use slf4j/logback
  • [POLICY-177] - test-transaction feature to check on the healthiness of policy controllers
  • [POLICY-178] - policy/common: convert integrity monitor to use slf4j/logback as in drools-pdp
  • [POLICY-180] - Upgrade policy/engine release build to use more memory
  • [POLICY-181] - Policy/common change jenkins job to not ignore JUnit tests for verify job.
  • [POLICY-193] - Created a new cleanup process
  • [POLICY-196] - Enhancement on MS JSON File
  • [POLICY-218] - LF Open Source License Issues
  • [POLICY-228] - Create common object to consolidate AAI response
  • [POLICY-231] - Remove Binary files from Policy Repo
  • [POLICY-237] - Address remaining sonar/critical for policy/common
  • [POLICY-239] - Address sonar major issues
  • [POLICY-247] - Modify docker push-policies to push the Amsterdam Template and latest policies
  • [POLICY-253] - Modify policy/engine pom.xml to remove sonar scan on 3rd party code.
  • [POLICY-261] - policy/drools-pdp last remaining sonar critical
  • [POLICY-266] - feature-state-management JUnit coverage
  • [POLICY-273] - Revert the SDK properties from onap to ecomp
  • [POLICY-274] - .gitignore policy/engine directories/files created after running mvn clean install or mvn test
  • [POLICY-297] - policy/drools-applications stage-site build is failing due to heap space
  • [POLICY-304] - Add ability for Docker scripts to NOT pre-load policies for testing
  • [POLICY-307] - Delete the pre-Amsterdam policy template etc.
  • [POLICY-312] - Change Policy CSIT Integration Tests to utilize the PRELOAD_POLICIES=false
  • [POLICY-335] - Add more documentation details
  • [POLICY-337] - Update CSIT Integration Tests with latest Config/Operational Policies
  • [POLICY-355] - Exclude dependencies for mysql and iText
  • [POLICY-372] - Update the DCAE TCA Model
  • [POLICY-453] - Upgrade .gitreview for Amsterdam Branch

Bug

  • [POLICY-12] - Clean up warnings in drools-pdp project
  • [POLICY-14] - Fix docker-compose to use onap/* instead of openecomp/*
  • [POLICY-15] - 1.1.0-SNAPSHOT bring up issues
  • [POLICY-16] - correct problems introduced by swagger addition to pdp-d
  • [POLICY-19] - PDP-X getConfig API Authentication error
  • [POLICY-20] - PDP-X getConfig - Configuration Policy not found
  • [POLICY-21] - PDP-D occasionally stuck during shutdown
  • [POLICY-23] - PDP-X getConfig issues
  • [POLICY-24] - PDP-X pushPolicy problems
  • [POLICY-27] - excessive long idle timeouts in DB introduced unnecessarily
  • [POLICY-29] - BRMS GW - client configuration
  • [POLICY-74] - policy-engine build failure
  • [POLICY-75] - KieScanner repeatedly updating Drools container
  • [POLICY-84] - Query Name validation before execution
  • [POLICY-91] - drools-applications - vFW/vDNS dependencies issues
  • [POLICY-92] - brmsgw - vFW/vDNS dependency rename issue
  • [POLICY-94] - Health check failure in R1.1.0 in DFW on Rackspace
  • [POLICY-134] - PolicyLogger.info(Object arg0) executes recursively causing stack overflow error.
  • [POLICY-144] - PAP: console: browser access: 500 code
  • [POLICY-145] - Healthcheck functionality not working
  • [POLICY-146] - brmsgw: vFW/vDNS rules jars not generated
  • [POLICY-165] - Support Backward compatibility for the Policy Interface
  • [POLICY-170] - policy build by vagrant fails
  • [POLICY-175] - 0% Code Coverage in some projects
  • [POLICY-192] - verify and/or merge job hang running JUnit test
  • [POLICY-194] - policy/drools-applications: fix template to enable JUnits
  • [POLICY-195] - policy/drools-pdp/session-persistence: remove new sonar blocker and criticals
  • [POLICY-197] - drools-applications: logger change breaks junit on drl template
  • [POLICY-199] - Policy UI page displays blank in ONAP
  • [POLICY-203] - Test case testGetPropertiesValue fails if we run test case or build code other than C:
  • [POLICY-205] - policy/engine: missing license files
  • [POLICY-206] - Missing license for drools-applications
  • [POLICY-211] - Policy Fails Robot Health Check
  • [POLICY-213] - remove sonar blocker/criticals introduced by feature-test-transaction
  • [POLICY-221] - Policy GUI Cosmetic Issues
  • [POLICY-223] - PDP Health Check Fail
  • [POLICY-229] - Policy healthcheck failure in RS ORD ONAP 1.1.0
  • [POLICY-234] - PDP-D: drools session remains hung on an update
  • [POLICY-275] - pdp-x: automated pushing of policies shows that some operations failed
  • [POLICY-276] - brmsgw: not generating amsterdam rules jar
  • [POLICY-278] - console: sql injection protection not working properly
  • [POLICY-295] - brmsgw: amsterdam controller rules generation cannot be built
  • [POLICY-296] - pdp-d guard db access causes control loop failures
  • [POLICY-298] - pdp-d: drl template drops messages in clean up rules
  • [POLICY-299] - Policy CSIT tests are running over 15 hours long
  • [POLICY-300] - Use correct format for messages from Policy to APPC_LCM_READ
  • [POLICY-301] - DB sessionpersistence.sessioninfo to mediumblob
  • [POLICY-302] - brmsgw: set up rules should not be generated
  • [POLICY-305] - Policy Guard Deny response
  • [POLICY-306] - vDNS yaml that is pushed should contain "SO" as actor not "MSO"
  • [POLICY-310] - Policy GUI Fixes
  • [POLICY-313] - Update MicroService vCPE Config Policy with new values
  • [POLICY-314] - pdp-d: better handling of unsuccessful AAI responses
  • [POLICY-315] - Change back docker compose version to 2 from 3
  • [POLICY-339] - pdp-d apps aai vdns : update aai interface from v8 to v11
  • [POLICY-340] - console: upgrade to latest portal sdk
  • [POLICY-341] - pdp-d apps vfw: subsequent onsets on same resource not discarded
  • [POLICY-342] - docker push-policies : config and operational policies must use the same control loop name
  • [POLICY-343] - console: displaying corporate logo
  • [POLICY-344] - Operations History Persistence Unit Not Found
  • [POLICY-345] - Operations History Table is not written to
  • [POLICY-350] - pdp-d apps drl: resiliency to exceptions and null values returned/thrown from java models
  • [POLICY-353] - Bug in UebTopicSinkFactory
  • [POLICY-354] - Update the latest Portal Properties
  • [POLICY-356] - pdp-d apps: print networked messages over http interface
  • [POLICY-357] - pdp-d db-migrator when ALL dbs flag is used upgrade not working properly
  • [POLICY-363] - docker pdp-d: set DCAE DMaaP Server default to vm1.mr.simpledemo.openecomp.org
  • [POLICY-364] - Policy template should not reject Event if A&AI lookup fails.
  • [POLICY-365] - MariaDB doesn't come up when an old volume is present
  • [POLICY-369] - Clean up of feature-state-management issues from testing
  • [POLICY-376] - pdp-d apps : control loop generation from archetype fails
  • [POLICY-385] - pdp-d apps : potential null pointer exceptions when logging http response to network log
  • [POLICY-386] - pdp-d: ensure pdp-d shuts down when underlying component is stuck in shutdown sequence
  • [POLICY-401] - Update SO url from v2 to v5
  • [POLICY-402] - pdp-d apps msb build issue when releasing
  • [POLICY-403] - Fixed a bug on view and editor screens
  • [POLICY-404] - pdp-d : clean up parent pom pre-release
  • [POLICY-405] - TOSCA model parser issue in Policy GUI
  • [POLICY-406] - policy/engine: snapshot external dependencies should be removed
  • [POLICY-407] - Rogue Abatement Processing
  • [POLICY-408] - VFC Manager not catching exception generated by NULL VFC URL
  • [POLICY-409] - Closed loop between DCAE and Policy still not working: vnf-name vs vnf-id
  • [POLICY-410] - pdp-d apps : aai rest response not expanded in network.log
  • [POLICY-411] - Resolve Policy Blocker Issues
  • [POLICY-412] - Remove the id value from MicroService Model in db script
  • [POLICY-433] - pdp-d apps : snapshot msb and core pdp-d dependencies shown in staging repo
  • [POLICY-437] - pdp-d apps : change mso url to not contain suffix HTTPS/1.1
  • [POLICY-438] - pdp-d apps vdns so: mismatch in post request
  • [POLICY-445] - Hardcode pattern match SO pre-load value into SO request for vDNS Use Case
  • [POLICY-446] - pdp-d apps : archetype tooling to default to 1.1.1
  • [POLICY-447] - Update SO to use is-base-vf-module=false
  • [POLICY-454] - brmsgw 1.1.2 policy rules generation in a 1.1.1 docker image
  • [POLICY-486] - pdp-x api pushPolicy fails to push latest version
  • [POLICY-487] - Race conditions leading to a blocked thread when disposing underlying kie sessions under transaction loads
  • [POLICY-496] - Docker Amsterdam release jobs have never succeeded

Sub-task

  • [POLICY-52] - policy/engine: JUnit test code coverage
  • [POLICY-71] - replace openecomp for policy-common
  • [POLICY-72] - replace openecomp for policy-drools-pdp
  • [POLICY-73] - replace openecomp for policy-engine
  • [POLICY-81] - policy/commons: verify warnings that show up in eclipse
  • [POLICY-82] - policy/engine: verify no warnings show up in eclipse window
  • [POLICY-83] - ensure policy/docker is able to run/create an image(s) using org.onap
  • [POLICY-85] - replace openecomp for policy-drools-applications
  • [POLICY-86] - replace openecomp for policy-docker
  • [POLICY-89] - Create Actor sub project in policy/drools-applications
  • [POLICY-90] - replace ECOMP to ONAP for policy-engine
  • [POLICY-101] - Use only one .drl in the Amsterdam template project
  • [POLICY-102] - vDNS Use Case - add in A&AI named query and call to SO for scale up
  • [POLICY-103] - Implement dynamic A&AI Functionality
  • [POLICY-104] - APP-C Restart API
  • [POLICY-106] - policy/drools-applications: verify no issues/warning are shown in eclipse
  • [POLICY-107] - policy/drools-pdp: not warnings in eclipse
  • [POLICY-108] - policy/common: JUnit test code coverage
  • [POLICY-109] - policy/drools-pdp: JUnit test code coverage
  • [POLICY-110] - policy/drools-applications: JUnit Test Coverage
  • [POLICY-120] - Request from MSB Team to fill out wiki
  • [POLICY-128] - Upload FOSSology for policy/common
  • [POLICY-129] - upload FOSSology for policy/engine
  • [POLICY-130] - Upload FOSSology for policy/drools-pdp
  • [POLICY-131] - Upload FOSSology for policy/drools-applications
  • [POLICY-132] - Generate FOSS report to upload into onap wiki
  • [POLICY-136] - Cleanup the Policy Architecture wiki
  • [POLICY-137] - Cleanup the Policy API wiki
  • [POLICY-139] - Create the parent pom.xml for the new repositories
  • [POLICY-140] - Add the ci-management Jenkins Jobs for the new repositories
  • [POLICY-142] - Create a simple Hello World functional test in integration project
  • [POLICY-143] - Create the Jenkin's Job in ci-management for the test to run automatically
  • [POLICY-149] - policy-common integration with oparent
  • [POLICY-150] - policy-drools-applications integration with oparent
  • [POLICY-151] - policy-drools-pdp integration with oparent
  • [POLICY-152] - policy-engine integration with oparent
  • [POLICY-153] - policy-docker integration with oparent
  • [POLICY-157] - Finalize the Functional Test Case definitions on the wiki
  • [POLICY-159] - policy-management, feature-eelf, feature-healthcheck sonar criticals
  • [POLICY-160] - policy-core sonar criticals
  • [POLICY-174] - fix critical sonar for ONAP-PAP-REST
  • [POLICY-182] - fix sonar critical for ONAP-PAP-REST
  • [POLICY-183] - fix critical sonar for ONAP-REST
  • [POLICY-184] - fix critical sonar for ONAP-XACML
  • [POLICY-185] - fix critical sonar for POLICY-SDK-APP
  • [POLICY-186] - fix critical sonar for PolicyEngineAPI
  • [POLICY-187] - fix critical sonar for PolicyEngineClient
  • [POLICY-188] - fix critical sonar for PolicyEngineUtils
  • [POLICY-189] - fix critical sonar for BRMSGateway
  • [POLICY-190] - Create documentation template in read the docs
  • [POLICY-198] - pdp-d: add junits for feature-test-transaction
  • [POLICY-200] - Create A&AI Simulator
  • [POLICY-201] - Create an SO simulator
  • [POLICY-202] - Create vFC Simulator
  • [POLICY-204] - Fix sonar critical for VFC Manager
  • [POLICY-212] - drools-application JUnit test for VFC
  • [POLICY-214] - pdp-d: add junits for policy-utils
  • [POLICY-216] - Clean unused imports and duplicate version warnings
  • [POLICY-217] - fix sonar blocker for ONAP-PAP-REST
  • [POLICY-219] - Change mysql connector to mariadb connector
  • [POLICY-220] - Change/Remove flexslider dependency
  • [POLICY-222] - Target Lock only works for Target Types of VM
  • [POLICY-224] - Sonar Major : Remove those useless parentheses from CheckPDP.java
  • [POLICY-225] - Upgrade pom.xml to oparent release version rather than snapshot
  • [POLICY-226] - Determine how to release Policy API for DCAE/CLAMP teams
  • [POLICY-227] - Add junit coverage for feature-healthcheck
  • [POLICY-230] - Sonar Major : Move the "" string literal on the left side of this string comparison.
  • [POLICY-232] - Determine if Guard Permits and Denies as Expected
  • [POLICY-233] - Sonar Major : Merge this if statement with the enclosing one
  • [POLICY-235] - Sonar Major : Introduce new variable instead of re-using the same.
  • [POLICY-236] - Add Junit tests to DroolsPDP policy-core
  • [POLICY-240] - Clear Eclipse warnings introduced
  • [POLICY-241] - Update API section of Read The Docs
  • [POLICY-242] - Create Release Notes
  • [POLICY-243] - Create Development Guides
  • [POLICY-244] - Convert Architecture to RST
  • [POLICY-248] - Sonar Major : Add override annotation above the method signature.
  • [POLICY-249] - Sonar Major : Move the String literal on left side of string comparison.
  • [POLICY-250] - Sonar Major:Remove those useless parentheses
  • [POLICY-251] - Remove non-functional policy csit health test
  • [POLICY-254] - vdns: use pdp-d environment settings to talk to so + aai
  • [POLICY-255] - guard: consultation and testing guard in pdp-d against pdp-x
  • [POLICY-256] - guard: add simulator for pdp-d junit usage
  • [POLICY-257] - pdp-d: aai scripts for onap environment
  • [POLICY-258] - pdp-d: pairwise testing with aai onap instance
  • [POLICY-259] - pdp-d: verification all use cases (non-junit) in standalone pdp-d environment
  • [POLICY-260] - guard: adapting xacml interface to pdp-x
  • [POLICY-262] - policy-management/org.onap.policy.drools.protocol.configuration junits
  • [POLICY-263] - brmsgw: support new amsterdam controller
  • [POLICY-264] - docker pe: modify push-policies.sh script to push new policies to PDP for automated startup as in R0
  • [POLICY-265] - pdpd: make amsterdam controller available at startup time
  • [POLICY-267] - Upgrade ci-management job for policy/drools-pdp
  • [POLICY-268] - SO Request Retries
  • [POLICY-270] - Add functionality to track operation attempts to VFC code
  • [POLICY-277] - Update Integration Docker Version for 1.1.0
  • [POLICY-279] - test AAI interaction in rackspace environment
  • [POLICY-280] - test PDP-X GUARD interaction in rackspace environment
  • [POLICY-281] - test complete flow in rackspace environment
  • [POLICY-282] - test AAI interaction in rackspace environment
  • [POLICY-283] - test PDP-X GUARD interaction in rackspace environment
  • [POLICY-284] - test complete flow in rackspace environment
  • [POLICY-285] - test AAI interaction in rackspace environment
  • [POLICY-286] - test PDP-X GUARD interaction in rackspace environment
  • [POLICY-287] - test complete flow in rackspace environment
  • [POLICY-288] - test AAI interaction in rackspace environment
  • [POLICY-289] - test PDP-X GUARD interaction in rackspace environment
  • [POLICY-290] - test complete flow in rackspace environment
  • [POLICY-291] - restructure use case junits to prevent frequent build failures due to race conditions
  • [POLICY-292] - clean up latest blocker/critical sonars (guard, msb, ..)
  • [POLICY-294] - create script to clean up GUARD history database
  • [POLICY-308] - Remove the deprecated pre-Amsterdam policy template code.
  • [POLICY-309] - Remove the pre-built policies and preloaded template from pre-Amsterdam release
  • [POLICY-318] - CLONE - test PDP-X GUARD interaction in rackspace environment
  • [POLICY-322] - CLONE - test PDP-X GUARD interaction in rackspace environment
  • [POLICY-323] - CLONE - test complete flow in rackspace environment
  • [POLICY-326] - CLONE - test PDP-X GUARD interaction in rackspace environment
  • [POLICY-327] - CLONE - test complete flow in rackspace environment
  • [POLICY-330] - CLONE - test PDP-X GUARD interaction in rackspace environment
  • [POLICY-331] - CLONE - test complete flow in rackspace environment
  • [POLICY-346] - Update archetype with fixed operational policies and abatement event
  • [POLICY-358] - Create Drools PDP Debugging Documentation
  • [POLICY-360] - Create Guard Policy Documentation
  • [POLICY-361] - Create Policy Engine PDP/PAP Debugging Documentation
  • [POLICY-362] - Create Policy Engine PAP/PDP/BRMSGateway Software Architecture Documentation
  • [POLICY-366] - Change A&AI query to use vnf-name instead of vnf-id
  • [POLICY-367] - Ensure target lock is for target VNF/VM instead of source VNF/VM
  • [POLICY-368] - For ABATED events, no A&AI lookup is necessary
  • [POLICY-371] - For subsequent onset events, no A&AI query is needed
  • [POLICY-373] - Update the push-policies.sh script based on the new model
  • [POLICY-374] - Update CSIT tests for new configuration policies
  • [POLICY-375] - Create a policy model from the TCA spec
  • [POLICY-378] - Create Amsterdam branch 1.1.0
  • [POLICY-379] - Create CI/CD jobs for release branch 1.1.0
  • [POLICY-380] - Email ONAP Helpdesk to release Java artifacts for 1.1.1
  • [POLICY-381] - Email ONAP Helpdesk to release Docker images for 1.1.1
  • [POLICY-383] - Notify CLAMP regarding released artifact version availability
  • [POLICY-384] - Update Integration Team Docker Manifest
  • [POLICY-388] - Create Final Documentation List of Tasks/Bugs/etc.
  • [POLICY-414] - Document Feature Test Transaction
  • [POLICY-415] - Document Feature EELF
  • [POLICY-416] - Document Feature Session Persistence
  • [POLICY-417] - Document Feature State Management
  • [POLICY-418] - Document Feature Active/Standby Management
  • [POLICY-419] - Document Feature Healthcheck
  • [POLICY-420] - Document PDP-D Software Architecture
  • [POLICY-421] - Document "Tutorial: Testing the vFW use case in a standalone PDP-D"
  • [POLICY-422] - Document "Tutorial: Testing the vDNS Use Case on standalone PDP-D"
  • [POLICY-423] - Document: "Tutorial: Testing the vCPE Use Case in a standalone PDP-D"
  • [POLICY-424] - Document: "Tutorial: Testing the VOLTE use case in a standalone PDP-D"
  • [POLICY-425] - Document "Verifying/Modifying AAI data"
  • [POLICY-426] - Document "Control Loop Simulation and Injection of Messages"
  • [POLICY-427] - Document "Using Guard in the PDP-D"
  • [POLICY-428] - Document: "Tutorial: Generating and Testing your own Control Loop Operational Policy in a standalone PDP-D"
  • [POLICY-429] - Document: "Modifying the Amsterdam Release Template"
  • [POLICY-430] - Document "Running PDP-D in Eclipse"
  • [POLICY-435] - Update Integration Team Java Manifest
  • [POLICY-436] - Update SNAPSHOT to next version 1.1.2
  • [POLICY-439] - Rename release notes so documentation can auto pick it up
  • [POLICY-441] - Update release process due to LF removing staging from global settings.xml file
  • [POLICY-450] - Update demo heat environment

Edit/Copy Release Notes

The text area below allows the project release notes to be edited and copied to another document.