Adding a note concerning timing between VNF Lifecycle

Operations.

Change-Id: Ie24d68289d33822b1d899018d41262bb79d7a829
Signed-off-by: mrpa <miruna.paun@enea.com>

1 files changed, 12 insertions, 3 deletions

diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
index 2a4cc8a..5088e9c 100644
--- a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
@@ -13,8 +13,8 @@
     adding uCPE device(s), receiving uCPE events' reports, removing a uCPE
     device, waiting for a uCPE device to connect to the uCPE Manager, as well
     as scripts for adding and removing an offline configuration store. This
-    folder also contains scripts for uploading and removing an NFVA image into 
-      the uCPE Manager, and for installing and activating a NFVA image on a uCPE
+    folder also contains scripts for uploading and removing an NFVA image into
+    the uCPE Manager, and for installing and activating a NFVA image on a uCPE
     Device.</para>
 
     <para>The <literal>/customScripts</literal> folder contains Python scripts
@@ -55,7 +55,7 @@
 
     <para>The <literal>/unittestSuite/vnf_config</literal> directory contains
     symlinks for the Fortigate license file and for the
-    <literal>/vnf_config/fortigateImage</literal> folder. </para>
+    <literal>/vnf_config/fortigateImage</literal> folder.</para>
 
     <para>The <literal>/vnf</literal> folder contains Python scripts for
     onboarding and offboarding a VNF image, instantiating a VNF, controlling a
@@ -1629,6 +1629,15 @@ License("vnf_config/fortigateImage/fortigateLicense.lic")
       <para>How to Control a VNF instance from the Enea uCPE Manager is
       detailed below.</para>
 
+      <note>
+        <para>If a sequence of commands aiming to change the state of the VNF
+        (start/stop/suspend/shutdown) is issued rapidly, certain VNFs might become
+        unresponsive. Depending on the actual VNF, the time required between
+        life-cycle operations may vary from several seconds to half a minute
+        or even more. If a VNF becomes unresponsive, the only possible action
+        is to "Force Delete" the instance from the uCPE Manager.</para>
+      </note>
+
       <section id="script_opts_control">
         <title>Script Options</title>