5 files changed, 156 insertions, 17 deletions

diff --git a/doc/book-enea-edge-getting-started/doc/installation_guide.xml b/doc/book-enea-edge-getting-started/doc/installation_guide.xml
index 50a90b0..2805d4f 100644
--- a/doc/book-enea-edge-getting-started/doc/installation_guide.xml
+++ b/doc/book-enea-edge-getting-started/doc/installation_guide.xml
@@ -22,7 +22,7 @@
         </note>
 
         <para>The following will detail CPU, RAM and storage requirements for
-        the Enea Edge Management.</para>
+        the Enea Edge Management Application.</para>
 
         <itemizedlist>
           <listitem>
@@ -81,7 +81,7 @@
         </itemizedlist>
 
         <para>The purpose of the CentOS 7 server is to host the Enea Edge
-        Management. Network access between the CentOS 7 server and the uCPE
+        Management Application. Network access between the CentOS 7 server and the uCPE
         devices is required. The Enea Edge Management and the uCPE devices
         will be connected on separate subnets to avoid inconsistencies.</para>
       </listitem>
@@ -1134,10 +1134,11 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
   <section id="ucpe_monitor">
     <title>uCPE Device Monitorization and Control</title>
 
-    <para>Once the uCPE device is connected to the Enea Edge Management, it is
-    ready for central management. Two important functions available in the
-    Enea Edge Management GUI are alarm checking and resource
-    allocation.</para>
+    <para>Once the uCPE device is connected to the Enea Edge Management 
+      application, it is ready for central management. Two important functions 
+      available in the Enea uCPE Management GUI are alarm checking and resource 
+      allocation. Additionally, the device can be rebooted, the factory settings 
+      can be restored or simply the vCPE service can be restarted.</para>
 
     <section id="check_alarms">
       <title>Checking Alarms</title>
@@ -1167,6 +1168,41 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
       uCPE device once instantiated.</para>
     </section>
 
+    <section id="basic_oper_device">
+      <title>Basic operations for uCPE device Managememt</title>
+
+      <para>When the uCPE device is connected to the Enea Edge Management application, it can
+      be rebooted, the factory settings can be restored or simply the vCPE
+      service can be restarted.</para>
+
+      <para>Select the uCPE device and go to the <emphasis
+      role="bold">Operations</emphasis> menu, where the following options are available:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><emphasis role="bold">Reboot</emphasis>. Reboots the device. Settings will be preserved.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Factory reset</emphasis>. Resets the device to its 
+          default factory settings. All current configuration settings are lost. All 
+          running VNFs are destroyed. Any installed custom scripts will be removed and 
+          they will need to be reinstalled.</para>
+
+          <para>Only the vCPE service will be restarted, the device will not
+          be rebooted. No reboot is needed.</para>
+
+          <para>Once the vCPE service restart completes, appropriate day-0
+          provisioning will take place.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Restart Vcpe</emphasis>. Restarts the
+          vCPE service on the device. The device will not be rebooted.</para>
+        </listitem>
+      </itemizedlist>
+    </section>
+
     <section id="access_device_cli">
       <title>Accessing the uCPE device CLI</title>
 
diff --git a/doc/book-enea-edge-getting-started/doc/introduction.xml b/doc/book-enea-edge-getting-started/doc/introduction.xml
index 8186ff1..5786883 100644
--- a/doc/book-enea-edge-getting-started/doc/introduction.xml
+++ b/doc/book-enea-edge-getting-started/doc/introduction.xml
@@ -257,6 +257,12 @@
 
               <entry>Virtual Network Function.</entry>
             </row>
+
+            <row>
+              <entry>vCPE</entry>
+
+              <entry>Virtual Customer Premises Equipment.</entry>
+            </row>
           </tbody>
         </tgroup>
       </table>
diff --git a/doc/book-enea-edge-getting-started/doc/net_config_options.xml b/doc/book-enea-edge-getting-started/doc/net_config_options.xml
index dae5b36..344b79b 100644
--- a/doc/book-enea-edge-getting-started/doc/net_config_options.xml
+++ b/doc/book-enea-edge-getting-started/doc/net_config_options.xml
@@ -722,7 +722,8 @@
     <section id="remove_scripts">
       <title>Removing Scripts</title>
 
-      <para>Follow the instruction below to remove scripts:</para>
+      <para>Follow the instruction below to remove scripts from the Enea Edge
+      Management application:</para>
 
       <orderedlist>
         <listitem>
@@ -744,7 +745,7 @@
       <title>Configuring Script Location</title>
 
       <para>The location where the scripts are staged in the Enea Edge
-      Management can be chanaged as described below:</para>
+      Management application can be changed as described below:</para>
 
       <orderedlist>
         <listitem>
@@ -814,9 +815,32 @@
         </listitem>
       </orderedlist>
     </section>
+
+    <section id="remove_script_device">
+      <title>Removing Scripts from a uCPE Device</title>
+
+      <para>Follow the instructions below to remove scripts from a uCPE
+      Device:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Access the <emphasis role="bold">Operations</emphasis> menu
+          and select <emphasis role="bold">Delete Custom
+          Script</emphasis>.</para>
+        </listitem>
+
+        <listitem>
+          <para>In the <emphasis role="bold">Delete Custom Script</emphasis>
+          pop up, set the name and the type of the script that should be
+          deleted and press <emphasis role="bold">Execute</emphasis>. If the
+          <emphasis role="bold">Script Type</emphasis> remains unset, the
+          script will be deleted regardless of its type.</para>
+        </listitem>
+      </orderedlist>
+    </section>
   </section>
 
-  <section  id="wireless_access_point">
+  <section id="wireless_access_point">
     <title>Wireless Access Point</title>
 
     <para>The Wireless AP Screen from the Enea Edge Management Configuration
diff --git a/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml b/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
index 14ac049..9680a0c 100644
--- a/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
+++ b/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
@@ -245,7 +245,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
         <emphasis role="bold">System</emphasis>, <emphasis
         role="bold">Configuration</emphasis>, <emphasis role="bold">Web
         Access</emphasis> and checking the <emphasis role="bold">Enable
-        HTTP</emphasis> box, or installing it manually.</para>
+        HTTP</emphasis> box, or install Edge Enea 2.4.0 on the device manually.</para>
       </note>
     </section>
 
@@ -576,13 +576,37 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
         upgrade image can be chosen from the <emphasis role="bold">Image
         Files</emphasis> tab by selecting the image file from the list and
         clicking the <emphasis role="bold">Install on Device</emphasis>
-        button.</para>
+        button. The Image files that appear in the <emphasis role="bold">Image
+        Library</emphasis> tab can be uploaded to the Enea Edge Management Application
+        by following the steps listed in <link linkend="image_lib">Image Library</link>.</para>
 
         <para>Once an image is installed on the uCPE device, the image will be
         available on the uCPE device and be visible in the <emphasis
-        role="bold">Releases</emphasis> tab. It can then be selected from the
-        list and the upgrade started by clicking the <emphasis
-        role="bold">Upgrade</emphasis> button.</para>
+        role="bold">Releases</emphasis> tab. There are two ways to make it
+        active, choose one or the other:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Select it from the list and then start the upgrade by
+            clicking the <emphasis role="bold">Upgrade</emphasis> button.</para>
+          </listitem>
+
+          <listitem>
+            <para>Select <emphasis role="bold">Operations</emphasis>, then 
+            <emphasis role="bold">Upgrade</emphasis>, enter the
+            <literal>Release Name</literal> and press <emphasis
+            role="bold">Execute</emphasis>. Filling in the <literal>Restore Archive</literal> 
+            text field is optional and should be left unset if the 
+              <literal>NFVi Snapshot</literal> feature is disabled.</para>
+          </listitem>
+        </itemizedlist>
+
+        <para>If an installed image is no longer needed, it can be removed
+        from the device by selecting <emphasis
+        role="bold">Operations</emphasis> and <emphasis role="bold">Remove
+        Release</emphasis>. In the <emphasis role="bold">Remove
+        Release</emphasis> window, provide the <literal>Release Name</literal>
+        and press <emphasis role="bold">Execute</emphasis>.</para>
       </section>
     </section>
   </section>
diff --git a/doc/book-enea-edge-getting-started/doc/vnf_mg.xml b/doc/book-enea-edge-getting-started/doc/vnf_mg.xml
index bd2fb0b..e3fcde2 100644
--- a/doc/book-enea-edge-getting-started/doc/vnf_mg.xml
+++ b/doc/book-enea-edge-getting-started/doc/vnf_mg.xml
@@ -407,9 +407,58 @@
       </listitem>
     </orderedlist>
 
-    <para>Selecting the <emphasis role="bold">VNF</emphasis> menu then
-    choosing <emphasis role="bold">Events</emphasis> will show that the VNF
-    was created and a connection was established.</para>
+    <para>Selecting the <emphasis role="bold">VNF</emphasis> menu then choosing <emphasis role="bold">Events</emphasis> 
+        will show that the VNF was created and a connection was established.</para>
+  </section>
+
+  <section id="vm_operations">
+    <title>VNF Instance Operations</title>
+
+    <para>Various operations can be done to a VNF instance. It can be paused,
+    resumed, stopped, started or deleted.</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Select from the top toolbar <emphasis role="bold">VNF</emphasis>
+        and choose <emphasis role="bold">Instances</emphasis>.</para>
+      </listitem>
+
+      <listitem>
+        <para>Select an instance that needs to be modified.</para>
+      </listitem>
+
+      <listitem>
+        <para>Depending on the desired action, click the <emphasis
+        role="bold">Delete/ Force Delete / Start / Stop / Pause /
+        Resume</emphasis> button respectively.</para>
+      </listitem>
+    </orderedlist>
+
+    <para>Alternatively, these same operations can be performed by:</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Selecting <emphasis role="bold">Operations</emphasis>.</para>
+      </listitem>
+
+      <listitem>
+        <para>Depending on the desired action, choosing <emphasis
+        role="bold">Destroy / Start / Stop / Pause / Resume
+        VM</emphasis> respectively.</para>
+      </listitem>
+
+      <listitem>
+        <para>The <literal>Id</literal> of the VM that should be modified can
+        be found by selecting <emphasis role="bold">Configuration</emphasis>, then
+        <emphasis role="bold">Virtual Machines</emphasis>, and then accessing the <emphasis
+        role="bold">VMs</emphasis> tab.</para>
+      </listitem>
+
+      <listitem>
+        <para>Provide the <literal>Id</literal> of the VM that should be
+        modified and press <emphasis role="bold">Execute</emphasis>.</para>
+      </listitem>
+    </orderedlist>
   </section>
 
   <section id="enter_console">