From 4be647d4375f5f49f5f4d3b415abb986fe6dc35b Mon Sep 17 00:00:00 2001 From: Marco Platania Date: Fri, 15 Feb 2019 14:37:22 -0500 Subject: Update release notes for vFW and vLB use cases Change-Id: I15e07efad73c5301f285685a003a1b979bc41173 Issue-ID: INT-748 Signed-off-by: Marco Platania --- docs/docs_scaleout.rst | 60 +++++++++++++------------------------------------- docs/docs_vfw.rst | 16 +++++++++++++- docs/docs_vlb.rst | 20 ++++++++++++++--- 3 files changed, 47 insertions(+), 49 deletions(-) diff --git a/docs/docs_scaleout.rst b/docs/docs_scaleout.rst index 86bbc93ef..6fe44e16f 100644 --- a/docs/docs_scaleout.rst +++ b/docs/docs_scaleout.rst @@ -164,7 +164,19 @@ Casablanca Scale Out completed all tests as found here: https://wiki.onap.org/pa Known Issues and Resolutions ~~~~~~~~~~~~~~~~~~~~~~~~~~~~ -1) When running closed loop-enabled scale out, the closed loop designed in CLAMP conflicts with the default closed loop defined for the old vLB/vDNS use case +1) SO fails service distribution + +Resolution: Update SO database as below + +- Connect to the SO database POD +- Login to mysql: mysql -uroot -ppassword +- Select database: use catalogdb: +- Update tables: + - ALTER TABLE vnf_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000); + - ALTER TABLE network_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000); + - ALTER TABLE allotted_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000); + +2) When running closed loop-enabled scale out, the closed loop designed in CLAMP conflicts with the default closed loop defined for the old vLB/vDNS use case Resolution: Change TCA configuration for the old vLB/vDNS use case @@ -173,7 +185,7 @@ Resolution: Change TCA configuration for the old vLB/vDNS use case - Change "subscriberConsumerGroup" in the TCA configuration to something different, for example "OpenDCAE-c13" instead of the default value "OpenDCAE-c12" - Click "UPDATE" to upload the new TCA configuration -2) When running closed loop-enabled scale out, the permitAll guard policy conflicts with the scale out guard policy +3) When running closed loop-enabled scale out, the permitAll guard policy conflicts with the scale out guard policy Resolution: Undeploy the permitAll guard policy @@ -182,46 +194,4 @@ Resolution: Undeploy the permitAll guard policy - Click "Policy" → "Push" on the left panel - Click the pencil symbol next to "default" in the PDP Groups table - Select "Decision_AllPermitGuard" -- Click "Remove" - -3) When using SDNC, the JSON template for DMaaP messages has a wrong "input" field - -Resolution: Replace the "input" field in the JSON template with "output" - -- Connect to the SDNC container from the Rancher VM in the Kubernetes cluster, for example - -:: - - kubectl exec -it -n onap dev-sdnc-sdnc-0 bash - -- Install your favorite text editor, for example - -:: - - apt-get update; apt-get install vim -y - -- Open /opt/onap/sdnc/restapi/templates/lcm-dmaap-publish-template.json and replace "input" with "output" in the JSON object body -- Save the changes -- If SDNC is deployed in cluster mode (3 SDNC replicas, dev-sdnc-sdnc-0, dev-sdnc-sdnc-1, dev-sdnc-sdnc-2), apply the same change to all the replicas in the cluster. - -4) When using SDNC, the JSON template for DMaaP messages has an extra newline at the end of the file - -Resolution: Delete the extra newline - -- Connect to the SDNC container from the Rancher VM in the Kubernetes cluster, for example - -:: - - kubectl exec -it -n onap dev-sdnc-sdnc-0 bash - -- Install your favorite text editor, for example - -:: - - apt-get update; apt-get install vim -y - -- Open /opt/onap/sdnc/restapi/templates/lcm-dmaap-publish-template.json and execute the following operations - - :set binary - - :set noeol -- Save the changes -- If SDNC is deployed in cluster mode (3 SDNC replicas, dev-sdnc-sdnc-0, dev-sdnc-sdnc-1, dev-sdnc-sdnc-2), apply the same change to all the replicas in the cluster. \ No newline at end of file +- Click "Remove" \ No newline at end of file diff --git a/docs/docs_vfw.rst b/docs/docs_vfw.rst index a722c67d5..9c5abc6e8 100644 --- a/docs/docs_vfw.rst +++ b/docs/docs_vfw.rst @@ -79,4 +79,18 @@ Although videos are still valid, users are encouraged to use the Heat templates Known issues and resolution ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -The packet generator may become unresponsive to external inputs like changing the number of active streams. To solve the problem, reboot the packet generator VM. \ No newline at end of file +1) SO fails service distribution + +Resolution: Update SO database as below + +- Connect to the SO database POD +- Login to mysql: mysql -uroot -ppassword +- Select database: use catalogdb: +- Update tables: + - ALTER TABLE vnf_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000); + - ALTER TABLE network_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000); + - ALTER TABLE allotted_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000); + +2) The packet generator may become unresponsive to external inputs like changing the number of active streams + +Resolution: Reboot the packet generator VM. \ No newline at end of file diff --git a/docs/docs_vlb.rst b/docs/docs_vlb.rst index ded308f05..463461a4b 100644 --- a/docs/docs_vlb.rst +++ b/docs/docs_vlb.rst @@ -94,12 +94,26 @@ Although videos are still valid, users are encouraged to use the Heat templates Known issues and resolution ~~~~~~~~~~~~~~~~~~~~~~~~~~~ -1) The packet generator may become unresponsive and stop generating traffic. To solve the problem, reboot the packet generator. +1) SO fails service distribution -2) The base and scaling VF module names need to follow a specific naming convention: +Resolution: Update SO database as below + +- Connect to the SO database POD +- Login to mysql: mysql -uroot -ppassword +- Select database: use catalogdb: +- Update tables: + - ALTER TABLE vnf_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000); + - ALTER TABLE network_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000); + - ALTER TABLE allotted_resource_customization MODIFY IF EXISTS RESOURCE_INPUT varchar(20000); + +2) The packet generator may become unresponsive to external inputs like changing the number of active streams + +Resolution: Reboot the packet generator VM. + +3) The base and scaling VF module names need to follow a specific naming convention: a) The base VF module name must be "Vfmodule\_xyz" b) The SDNC preload for the scaling VF module must set the VF module name to "vDNS\_xyz", where "xyz" is the same as the base module. This is required because during closed loop Policy looks for "Vfmodule\_" and replaces it with "vDNS\_" -3) Only one scaling operation is supported. \ No newline at end of file +4) Only one scaling operation is supported. \ No newline at end of file -- cgit 1.2.3-korg