Add deprecations to release notes

Updated release notes to indicate deprecation of SDNC portal and VNF-API

Change-Id: I7ba72bbfb225256b8ee060d52857e680a016920a
Issue-ID: SDNC-1231
Issue-ID: SDNC-1232
Signed-off-by: Dan Timoney <dtimoney@att.com>
Former-commit-id: 523bb0f096646ff70b8f9e94ac63828fe2fc3052

diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index 6f1bbc4..d317546 100644 (file)
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -21,6 +21,7 @@ The Frankfurt release of SDNC introduces new functionality to support PNFs (Phys
 for Netconf/TLS to support CMPv2, and adds support for the Multi Domain Optical Network Service use case.
 
 
+
 Release Data
 ============
 
@@ -61,6 +62,24 @@ The full list of `bugs fixed in the SDNC Frankfurt release <https://jira.onap.or
 
 The full list of `known issues in SDNC <https://jira.onap.org/issues/?filter=11119>`_ is maintained on the `ONAP Jira`_.
 
+
+Deprecated Features
+-------------------
+
+** SDNC portal **
+
+The SDNC portal is considered deprecated in the Frankfurt release, due
+to resource contraints.  This functionality is delivered dormant
+in Frankfurt (i.e. it is disabled in the Frankfurt helm charts) and we
+plan to remove the code entirely in the Guilin release.
+
+** VNF-API **
+
+The functionality provided by the VNF-API is now provided as part
+of the GENERIC-RESOURCE-API.  Therefore, the VNF-API is deprecated
+in Frankfurt and will be removed in Guilin.
+
+
 Deliverables
 ------------
 
@@ -153,10 +172,14 @@ There is currently one known SDNC security issue, related to the SDNC portal
 
 * `OJSI-91 <https://jira.onap.org/browse/OJSI-91>`_ : SDNC exposes unprotected API for user creation
 
-The current implementation of the SDNC portal has a self-subscription model - so anyone can create an account by going to
-the setup link.  This is not appropriate for production deployment and will be fixed in a future release.  
-The SDNC portal is disabled in the Frankfurt helm charts and we recommend that it NOT be enabled in a production
-deployment until this issue is corrected.
+The current implementation of the SDNC portal - which was intended purely
+as a test tool - has a self-subscription model - so anyone can create an
+account by going to the setup link.  This is not appropriate for production
+deployment and we strongly recommend that the SDNC portal NOT be used in
+production.
+
+The SDNC portal is disabled in the Frankfurt helm charts and will be removed
+entirely in the Guilin release.