Updated the EE Automation UG Chapter 4 to reflect name change.

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

1 files changed, 28 insertions, 27 deletions

diff --git a/doc/book-enea-edge-automation-user-guide/doc/automation_framework_test_harness.xml b/doc/book-enea-edge-automation-user-guide/doc/automation_framework_test_harness.xml
index f710ccb..bdc3343 100644
--- a/doc/book-enea-edge-automation-user-guide/doc/automation_framework_test_harness.xml
+++ b/doc/book-enea-edge-automation-user-guide/doc/automation_framework_test_harness.xml
@@ -192,9 +192,9 @@
           <filename>OfflineConfigHandler.py</filename> script, where the
           <literal>OfflineConfigHandler</literal> class is defined. Inside
           this class, the methods for offline configuration functionality are
-          implemented: <literal>addOfflineConfig</literal>,
-          <literal>removeOfflineConfig</literal>,
-          <literal>uploaOfflineConfig</literal> and so on.</para>
+          implemented: <literal>addOfflineConfigStore</literal>,
+          <literal>deleteOfflineConfigStore</literal>,
+          <literal>uploadConfigToDevice</literal> and so on.</para>
         </listitem>
       </itemizedlist>
     </section>
@@ -430,17 +430,17 @@
           <listitem>
             <para>Run <filename>generate_device_config.py</filename>:</para>
 
-            <programlisting>testHarness-venv)&gt; python generate_device_config.py
+            <programlisting>python generate_device_config.py
 Device name: test
 Device ID: test_id
 Device groupings tags [ ]: test_id
-uCPE Device version [2.4.0]: 2.4.0
+uCPE Device version [2.5.0]: 2.5.0
 Device IP address [No]: 10.0.0.1
 Call home [false]:
-Mgmt network interface [No]: eth0
-WAN network interface [No]: eth1
-LAN network interface [No]: eth2
-WAP network interface [No]: wlan0
+Mgmt network interface - it must not be the management interface [No]: eth0
+WAN network interface - it must not be the management interface [No]: eth1
+LAN network interface - it must not be the management interface [No]: eth2
+WAP network interface - it must not be the management interface [No]: wlan0
 
 The following JSON config file was successfully created (uCPE Device config file):
 test.json
@@ -464,7 +464,7 @@ store.json</programlisting>
     "deviceId": "test_id",
     "deviceGroupingTags": "test_id",
     "name": "test",
-    "version": "2.4.0",
+    "version": "2.5.0",
     "callHome": "false",
     "address": "10.0.0.1",
     "certificate": null,
@@ -503,8 +503,8 @@ store.json</programlisting>
         executed in a non-interactive way using the
         <command>--non-interactive</command> option, as follows:</para>
 
-        <programlisting>testHarness-venv)&gt;python generate_device_config.py --non-interactive --device_name=test
-  --device_id=test_id --device_grouping_tags=test_id --version 2.4.0
+        <programlisting>python generate_device_config.py --non-interactive --device_name=test
+  --device_id=test_id --device_grouping_tags=test_id --version 2.5.0
   --device_ip_addr=10.0.0.1 --call_home=false --mgmt_nic=eth0 --wan_nic=eth1
   --lan_nic=eth2 --wap_nic=wlan0</programlisting>
 
@@ -529,7 +529,7 @@ store.json</programlisting>
             <para>Run
             <filename>generate_nics_config_files.py</filename>:</para>
 
-            <programlisting>(testHarness-venv)&gt; python generate_nics_config_files.py
+            <programlisting>python generate_nics_config_files.py
 Device name: test
 Check 'test' directory for JSON configuration files</programlisting>
           </listitem>
@@ -606,7 +606,7 @@ Check 'test' directory for JSON configuration files</programlisting>
         <para>The <filename>generate_nics_config_files.py</filename> script
         can be executed in a non-interactive way, as follows:</para>
 
-        <programlisting>(testHarness-venv)&gt; python generate_nics_config_files.py  --device_name=test
+        <programlisting>python generate_nics_config_files.py  --device_name=test
 Check 'test' directory for JSON configuration files</programlisting>
 
         <para>The values from the JSON files depend on the input
@@ -624,7 +624,7 @@ Check 'test' directory for JSON configuration files</programlisting>
             <para>Run
             <filename>generate_bridges_config_files.py</filename>:</para>
 
-            <programlisting>(testHarness-venv)&gt; python generate_bridges_config_files.py
+            <programlisting>python generate_bridges_config_files.py
 Device name: test
 Check 'test' directory for JSON configuration files</programlisting>
           </listitem>
@@ -720,7 +720,7 @@ Check 'test' directory for JSON configuration files</programlisting>
         <para>The <filename>generate_bridges_config_files.py</filename> script
         can be executed in a non-interactive way, as follows:</para>
 
-        <programlisting>(testHarness-venv)&gt; python generate_bridges_config_files.py --device-name=test
+        <programlisting>python generate_bridges_config_files.py --device-name=test
 Check 'test' directory for JSON configuration files</programlisting>
 
         <para>The values from the JSON files depend on the input
@@ -799,13 +799,14 @@ Check 'test' directory for JSON configuration files</programlisting>
       directory inherit this class, and call its methods.</para>
 
       <note>
-        <para>The <literal>uCPEMgrHTTPClient</literal> class is a wrapper of
-        the <literal>ManagementClient</literal> class. All the methods defined
-        in the <literal>ManagementClient</literal> class can be used when the
-        <literal>uCPEMgrHTTPClient</literal> object is instantiated. The
-        <literal>uCPEMgrHTTPClient</literal> object is deprecated and will be
-        removed starting with the next major release. It is recommended to use
-        the <literal>ManagementClient</literal> class instead.</para>
+        <para>The <literal>uCPEMgrHTTPClientRestAPIv2</literal> class is a
+        wrapper of the <literal>ManagementClient</literal> class. All the
+        methods defined in the <literal>ManagementClient</literal> class can
+        be used when the <literal>uCPEMgrHTTPClientRestAPIv2</literal> object
+        is instantiated. The <literal>uCPEMgrHTTPClientRestAPIv2</literal>
+        object is deprecated and will be removed starting with the next major
+        release. It is recommended to use the
+        <literal>ManagementClient</literal> class instead.</para>
       </note>
 
       <para><emphasis role="bold">Examples</emphasis>:</para>
@@ -882,9 +883,9 @@ Options:
 
       <itemizedlist>
         <listitem>
-          <para>Run the Python API using only the values of the parameters 
-            without specifying the parameters' names. All parameters will 
-            be given and the value will be the position of each parameter.</para>
+          <para>Run the Python API using only the values of the parameters
+          without specifying the parameters' names. All parameters will be
+          given and the value will be the position of each parameter.</para>
         </listitem>
 
         <listitem>
@@ -1155,7 +1156,7 @@ uploadImage &lt;imagePath&gt; &lt;type&gt;</programlisting>
         <para><emphasis role="bold">Example:</emphasis></para>
 
         <programlisting>python automation_framework/DeviceUpgradeHandler.py -m uploadImage 
-/tmp/enea-nfv-access-xeon-d.tar.gz xeon-d</programlisting>
+/tmp/enea-edge-runtime-xeon-d.tar.gz xeon-d</programlisting>
 
         <para>All the other methods run in a similar way.</para>
       </section>