Update vCPE use case doc for R3.0.2

Change-Id: If2f62f01bea269d83392d768d48a3672bdf13ab7
Issue-ID: INT-1022
Signed-off-by: Yang Xu <yang.xu3@huawei.com>

1 files changed, 29 insertions, 5 deletions

diff --git a/docs/docs_vCPE.rst b/docs/docs_vCPE.rst
index 5bdaa3fd6..5dcf1fdd9 100644
--- a/docs/docs_vCPE.rst
+++ b/docs/docs_vCPE.rst
@@ -23,13 +23,28 @@ Most part of the use case has been automated by vcpe scripts. For the details on
 
 Test Status
 ~~~~~~~~~~~~~~~~~~~~~
-The use case had been tested for Casablanca Maintenance release, the regression test is reported on https://wiki.onap.org/display/DW/Casablanca+Maintenance+Release+Integration+Testing+Status 
+The use case had been tested for Casablanca Maintenance release 3.0.1, the regression test is reported on https://wiki.onap.org/display/DW/Casablanca+Maintenance+Release+Integration+Testing+Status 
 The use case had been tested for Casablanca release, the test report can be found on https://wiki.onap.org/display/DW/vCPE+-+Test+Status
 
-Known Issues and Workaround for Casablanca Maintenance Release
-~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
-1) vCPE infra service model distribution will fail due to a bug in SO, see the JIRA on https://jira.onap.org/browse/SO-1400, and follow the instruction on the comment section to expand database table size
- 
+Known Issues and Workaround for Casablanca Maintenance Releases 3.0.1 and 3.0.2
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+1) vCPE infra service model distribution will fail due to a bug in SO, see the JIRA on https://jira.onap.org/browse/SO-1400. Follow the instructions below to expand database table field size
+
+   a) Connect to SO mariadb POD from rancher node
+   
+   b) Login to mysql: mysql -uroot -ppassword
+   
+   c) Select database: use catalogdb;
+   
+   d) Update tables:
+
+::
+
+  mysql>ALTER TABLE vnf_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000);
+  mysql>ALTER TABLE network_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000);
+  mysql>ALTER TABLE allotted_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000);
+
 2) Firewalls are installed on BRG and vBNG. In order to allow SDNC to send BRG configuration message through vBNG, SDNC host VM IP address is preloaded on BRG and vBNG, and provisioned into the firewalls. If SDNC changes its host VM, SDNC host VM IP changes and we need to manually update the IP in /opt/config/sdnc_ip.txt. Then run:
 
 ::
@@ -39,6 +54,15 @@ Known Issues and Workaround for Casablanca Maintenance Release
   root>/opt/bind_nic.sh
   root>/opt/set_nat.sh
 
+3) Neutron HEAT template in database is invalid, see https://jira.onap.org/browse/SO-1609. The workaround is to download neutron.sh from the JIRA attachment and run neutron.sh on SO mariadb pod to update database table
+
+4) vGMUX doesn't send VES event in the right format. You need to follow vCPE tutorial to update libevel.so, then you may also need to restart vGMUX after running ldconfig command
+
+5) No ONSET event received by Policy. Check if TCA app is loaded from CDAT portal http://{{oom_cluster_node_ip}}:32010, click on top right corner drop down box to see if TCA app is listed. If TCA is not loaed, delete pod dcae-tca-analytics to let it restart
+
+6) The very first RESTART DMaaP event is not received by APPC. It is because the first RESTART message only creates the topic. You just need to wait a few minutes for the subsequent event to be triggered to see the closed loop action by APPC.
+
+
 Known Issues and Workaround for Casablanca Release
 ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 1) Firewalls are installed on BRG and vBNG. In order to allow SDNC to send BRG configuration message through vBNG, SDNC host VM IP address is preloaded on BRG and vBNG, and provisioned into the firewalls. If SDNC changes its host VM, SDNC host VM IP changes and we need to manually update the IP in /opt/config/sdnc_ip.txt. Then run: