+Version: 2.1.23 (Frankfurt, 6.0.0)
+---------------------------------------------
+
+:Release Date: 2020-06-05
+
+**New Features**
+Certificate Management Protocol Version 2 (CMPv2) support was added to retrieve X.509 certificates from servers which supports CMPv2 over HTTP. SDNC as first ONAP component was integrated to enroll certificate from CMPv2 server to protect traffic between SDNC and Network Functions (xNFs).
+More details about CMPv2 support in ONAP can be found on a dedicated page.
+
+
+**Bug Fixes**
+ - `AAF-383 <https://jira.onap.org/browse/AAF-383>`_ AAF aaf-sms chart should use nodePortPrefix variable
+ - `AAF-783 <https://jira.onap.org/browse/AAF-783>`_ Consul container is outdated
+ - `AAF-784 <https://jira.onap.org/browse/AAF-784>`_ Vault container is outdated
+ - `AAF-1102 <https://jira.onap.org/browse/AAF-1102>`_ Pods still run as root
+
+**Known Issues - solve in Guilin**
+ - `AAF-1087 <https://jira.onap.org/browse/AAF-1087>`_ AAF init containers init with exit 0 even if failing
+
+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, 4.0.0-ONAP)
+---------------------------------------
+
+:Release Date: 2019-06-06
+
+**New Features**
+
+Note: In general, Infrastructure must be accomplished in the release PRIOR to general usage. This is the case for most of the features included here.
+
+ - AAF has built the required features to automatically generate all Certificates and Configurations real-time. This will be utilized by ONAP MSs in El Alto
+ - AAF has the ability to publish both Public and Internal Private K8s Service information (Locator)
+ - Greatly Reduced size of Docker Images
+ - Greatly enhanced startup procedures in K8s, to more cleanly start, with Certificate, Property Generation every time
+ - Ability to run internally as non-root (fully setup K8s in El Alto)
+ - Removal of unused classes in Batch
+ - Large improvement in Batch and methodology, to be used in El Alto
+
+**Bug Fixes**
+ - `AAF-797 <https://jira.onap.org/browse/AAF-797>`_ Update IP address for aaf-onap-test.osaaf.org
+ - `AAF-794 <https://jira.onap.org/browse/AAF-794>`_ Misleading error message in agent.sh
+ - `AAF-773 <https://jira.onap.org/browse/AAF-773>`_ aaf-cass timing issues
+ - `AAF-769 <https://jira.onap.org/browse/AAF-769>`_ AAF CSIT not working
+ - `AAF-727 <https://jira.onap.org/browse/AAF-727>`_ Cert Subject Check confused by Email
+ - `AAF-722 <https://jira.onap.org/browse/AAF-722>`_ aaf continues to be available to aai-resources even though aaf database appears to be down
+ - `AAF-720 <https://jira.onap.org/browse/AAF-720>`_ Docker Images not passing Signal -1
+ - `AAF-645 <https://jira.onap.org/browse/AAF-645>`_ Fix "Null" string for fetching path inside CADI API enforcement filter
+ - `AAF-522 <https://jira.onap.org/browse/AAF-522>`_ rsa 4096 signing fails with TPM
+ - `AAF-813 <https://jira.onap.org/browse/AAF-813>`_ Missing Role for dmaap-bc Identity
+ - `AAF-514 <https://jira.onap.org/browse/AAF-514>`_ TPM Plugin: Remove global structure used for storing session data
+ - `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