Update release-notes

[aaf/authz.git] / docs / sections / release-notes.rst

diff --git a/docs/sections/release-notes.rst b/docs/sections/release-notes.rst
index 4e6fcbd..edbfa8d 100644 (file)
--- a/docs/sections/release-notes.rst
+++ b/docs/sections/release-notes.rst
@@ -1,12 +1,37 @@
 .. This work is licensed under a Creative Commons Attribution 4.0 International License.
 .. http://creativecommons.org/licenses/by/4.0
 .. Copyright © 2017 AT&T Intellectual Property. All rights reserved.
-
+.. _release_notes:
 
 Release Notes
-=============
+==============
+
+Version: 2.1.15 (El Alto, 5.0.1)
+---------------------------------------------
+
+:Release Date: 2019-08-12
+
+**New Features**
+El Alto is a consolidation release.  New Features are not Added.  
+However, for El Alto, ONAP is propagating the AAF Auto-Configuration and Certificate Generation feature from Dublin, see below
+
+An important change, however, is that the AAF Locator requires internal K8s Apps to use 
+       internal-to-K8s Service URL tags as (example) "onap.org.osaaf.aaf.service:2.1" 
+        external-to-K8s Service URL tags as (example) "org.osaaf.aaf.service.2.1"
+
+        IF you are using previous configurations, you may need to clear the existing directory
+       
+       - Login to your Init Container
+       - cd /opt/app/osaaf/local
+        - CAREFULLY rm *.*, and have it regenerate 
+
+**Bug Fixes**
+       - `AAF-859 <https://jira.onap.org/browse/AAF-859>`_ Images hardcoded in AAF helm deployment yamls
+
+**Known Issues - solve in Frankfurt**
+        - `AAF-962 <https://jira.onap.org/browse/AAF-962>`_ AAF Certs could not generate...
 
-Version: 2.1.13 (Dublin, 3.1.0-ONAP)
+Version: 2.1.13 (Dublin, 4.0.0-ONAP)
 ---------------------------------------
 
 :Release Date: 2019-06-06
@@ -38,6 +63,15 @@ Note: In general, Infrastructure must be accomplished in the release PRIOR to ge
        - `AAF-785 <https://jira.onap.org/browse/AAF-785>`_ non STAGING version on master
        - `AAF-822 <https://jira.onap.org/browse/AAF-822>`_ Startup issues with K8S, Certs
 
+**Usage Notes**
+       - AAF Core and SMS elements have consistently started from scratch. The one case where this didn't happen for SMS, 
+               it was found that incompatible data was left in volume.  Removal of old data for SMS (See SMS notes) should resolve
+        - On the same instance, one AAF Core component had a similar scenario.  A simple bounce of aaf-locator resolved.
+       - Existing Cassandra
+               - For each release, AAF maintains the authz/auth/auth-cass/cass_init/init.cql which is used to setup Keyspaces from scratch
+               - Any changes are also done in small CQL files, you MIGHT need authz/auth/auth-cass/cass_init/init2_10.cql for Dublin
+
+
 Version: 2.1.8 (Casablanca, 3.0.0-ONAP, Casablanca Maintenance Release)
 --------------------------------------------------------------------------
 
@@ -83,11 +117,6 @@ Note: AAF did not create new artifacts for Casablanca Maintenance Release.
 
  - AAF 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 AAF open Critical security vulnerabilities and their risk assessment have been documented as part of the `project <https://wiki.onap.org/pages/viewpage.action?pageId=43386201>`_.
 
-**Quick Links:**
-       - `AAF project page <https://wiki.onap.org/display/DW/Application+Authorization+Framework+Project>`_
-       - `CII Best Practices Silver Badge information for AAF <https://bestpractices.coreinfrastructure.org/en/projects/2303?criteria_level=1>`_
-       - `CII Best Practices Passing Badge information for AAF <https://bestpractices.coreinfrastructure.org/en/projects/2303?criteria_level=0>`_
-       - `Project Vulnerability Review Table for AAF <https://wiki.onap.org/pages/viewpage.action?pageId=43386201>`_
 
 **Upgrade Notes**
   NA
@@ -125,8 +154,13 @@ Version: 2.1.1 (Beijing, 2.0.0-ONAP)
      - Cassandra Instance in Kubernetes ONAP Test environment is a single instance.  REAL deployments should follow global, multi-datacenter deployment strategies per Cassandra recommendations.
 
 
-**Quick Links:**
+================
+Quick Links
+================
        - `AAF project page <https://wiki.onap.org/display/DW/Application+Authorization+Framework+Project>`_
+       - `CII Best Practices Silver Badge information for AAF <https://bestpractices.coreinfrastructure.org/en/projects/2303?criteria_level=1>`_
        - `CII Best Practices Passing Badge information for AAF <https://bestpractices.coreinfrastructure.org/en/projects/2303?criteria_level=0>`_
-       - `Project Vulnerability Review Table for AAF <https://wiki.onap.org/pages/viewpage.action?pageId=43385140>`_
+       - `Project Vulnerability Review Table for AAF <https://wiki.onap.org/pages/viewpage.action?pageId=43386201>`_
+
+