Update Release Notes and Guides

Updated APPC Release Notes and API and Client Library Guides

IssueId: APPC-101
Change-Id: I950eb93b337504b8ef1686ca06ecd2f77c74f245
Signed-off-by: Scott Seabolt <js9808@att.com>

diff --git a/docs/APPC Client Library Guide/APPC Client Library Guide.rst b/docs/APPC Client Library Guide/APPC Client Library Guide.rst
index 32a757a..f596bcd 100644 (file)
--- a/docs/APPC Client Library Guide/APPC Client Library Guide.rst
+++ b/docs/APPC Client Library Guide/APPC Client Library Guide.rst
@@ -88,8 +88,8 @@ Jar Files
 
 The Java application that runs the APPC client kit uses the following jar files:
 
-    -  com.att.appc.client.client-kit
-    -  com.att.appc.client.client-lib
+    -  org.openecomp.appc.client:client-kit
+    -  org.openecomp.appc.client:client-lib
 
 The client library JAR files are located in the repository under ``com\\att\\appc\\client``.
 

diff --git a/docs/APPC LCM API Guide/APPC LCM API Guide.rst b/docs/APPC LCM API Guide/APPC LCM API Guide.rst
index 916dd59..ada587a 100644 (file)
--- a/docs/APPC LCM API Guide/APPC LCM API Guide.rst
+++ b/docs/APPC LCM API Guide/APPC LCM API Guide.rst
@@ -114,6 +114,10 @@ Table 1 Request / Response Message Fields
 | correlation- id      | Correlation ID used for associating responses in APPC Client Library. Built as: <request-id>-<sub-request-id>  |     Yes             |
 +----------------------+----------------------------------------------------------------------------------------------------------------+---------------------+
 | rpc-name             | The target Remote Processing Call (RPC) name which should match the LCM command name. For example: configure   |     Yes             |
+|                      |                                                                                                                |                     |
+|                      | The convention for RPC names and the target URL is that multi-word command names should have a dash between    |                     |
+|                      | words, e.g.,                                                                                                   |                     |
+|                      | /restconf/operations/appc-provider-lcm:config-modify                                                           |                     |
 +----------------------+----------------------------------------------------------------------------------------------------------------+---------------------+
 | type                 | Message type: request, response or error                                                                       |     Yes             |
 +----------------------+----------------------------------------------------------------------------------------------------------------+---------------------+
@@ -1039,7 +1043,7 @@ Migrate suspends the guest virtual machine, and moves an image of the guest virt
 
 The migrate action will leave the VM in the same Openstack state the VM had been in prior to the migrate action. If a VM was stopped before migration, a separate VM-level restart command would be needed to restart the VM after migration.
 
-A successful Migrate action returns a success response and the new node identity in the response payload block.
+A successful Migrate action returns a success response.
 
 A failed Migrate action returns a failure and the failure messages in the response payload block.
 

diff --git a/docs/release-notes.rst b/docs/release-notes.rst
index 66d3eb8..85ab577 100644 (file)
--- a/docs/release-notes.rst
+++ b/docs/release-notes.rst
@@ -63,6 +63,12 @@ Other key features added in this release include:
        
 **Known Issues**
 
+       - `APPC-316 <https://jira.onap.org/browse/APPC-316>`_ - Null payload issue for Stop Application; Stop action will not work with a null payload. Ensure when testing Stop action that payload is included. 
+       
+       - `APPC-315 <https://jira.onap.org/browse/APPC-315>`_ - appc-request-handler is giving error java.lang.NoClassDefFoundError - This error results in vnf state and lock not being released. The workaround is to manually remove the entries from the VNF_LOCK_MANAGEMENT and VNF_STATE_MANAGEMENT tables.
+          - ``DELETE FROM VNF_LOCK_MANAGEMENT where RESOURCE_ID="vnf-id"``
+          - ``DELETE FROM VNF_STATE_MANAGEMENT where VNF_ID="vnf-id"``
+
        - `APPC-312 <https://jira.onap.org/browse/APPC-312>`_ - APPC request is going to wrong request handler and rejecting request. Configure request failing with following error: ``REJECTED Action Configure is not supported on VM level``.
        
        - `APPC-311 <https://jira.onap.org/browse/APPC-311>`_ - The APPC LCM Provider Healthcheck, which does a healthceck on a VNF, is failing. No known workaround at this time. 
@@ -77,7 +83,7 @@ Other key features added in this release include:
         
        - `APPC-154 <https://jira.onap.org/browse/APPC-154>`_ - Logging issue - Request REST API of APPC has RequestID (MDC) in Body or Payload section instead of Header.
        
-               
+       
 **Security Issues**
        - Communication over DMaaP currently does not use secure topics in this release.
        - AAF is deactivated by default in this release and was not validated or committed as part of the Amsterdam Release.
@@ -101,3 +107,4 @@ Other key features added in this release include:
 ===========
 
 End of Release Notes
+