GettingStarted: update VNF Management ch

- Merge "Onboarding and Instantiating a VNF" chapters from "VNF
  Onboarding Guide" and "Getting Started Guide".
- Remove all references to "Wizard"
- Remove all screenshots except “Figure 4.8 Onboard a VNF using the Wizard”

Change-Id: I0391abfa8254df9bed0ea3d1d7121a2bb1627a18
Signed-off-by: Sona Sarmadi <sona.sarmadi@enea.com>

1 files changed, 197 insertions, 520 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
index afb6ee3..935c9df 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
@@ -410,95 +410,121 @@
   <section id="vnf_management">
     <title>VNF Management</title>
 
-    <para>As the acting vnf manager, the uCPE Manager is responsible for
-    handling the life-cycles of VNFs that are instantiated and run on the
-    various uCPE devices. The vnf manager module is written so as to be able
-    to manage multiple VNF types. Along with it is provided a generic
-    infrastructure to allow the end-user to introduce new VNF types
-    dynamically into the system. This allows for third-party VNFs to be added
-    over time to an existing network infrastructure without having to perform
-    an expensive upgrade of the vnf manager itself.</para>
-
-    <para>The process of VNF Onboarding consists of providing the system with
-    sufficient information and resources related to the VNF such that it can
-    instantiate a flavour of the VNF on the uCPE device, configure and scale
-    it as appropriate, heal and upgrade it when necessary and tear it down at
-    the right moment.</para>
-
-    <para>The vnf manager subsystem in the uCPE Manager inserts a menu item in
-    the toolbar, called <literal>VNF</literal> as shown in the screen-shot
-    below.</para>
-
-    <figure>
-      <title>VNF Management</title>
-
-      <mediaobject>
-        <imageobject>
-          <imagedata align="center" fileref="images/vnf_management.png"
-                     scale="80" />
-        </imageobject>
-      </mediaobject>
-    </figure>
-
-    <para>Selecting this menu item gives you the following options:</para>
+    <para>The Enea uCPE Manager is responsible for
+    onboarding, configuring (e.g. CloudInit) and ensuring life cycle
+    management of VNFs that are instantiated and run on the various uCPE
+    devices.</para>
 
-    <itemizedlist>
-      <listitem>
-        <para><literal>Descriptors</literal>: Choosing this option lets you
-        manage the VNF Descriptors catalog. The vnf manager maintains a
-        catalog of all VNFs that can be instantiated and managed by the
-        system. Before you can use a new VNF, you need to onboard it into the
-        catalog.</para>
-      </listitem>
+    <section id="onboarding_a_vnf">
+      <title>Onboarding a VNF</title>
 
-      <listitem>
-        <para><literal>Instances</literal>: Choosing this option lets you
-        instantiate (or destroy) VNFs on a given uCPE device.</para>
-      </listitem>
+      <para>The onboarding of a VNF means adding it to the Enea uCPE Manager
+      VNF Catalog and preparing it for instantiation (deployment on connected
+      uCPE devices). This is accomplished using the Enea uCPE Manager
+      Onboarding graphical user interface.</para>
 
-      <listitem>
-        <para><literal>Events</literal>: Choosing this option displays all the
-        events that are related to VNF lifecycle management. Whenever a VNF
-        state changes (i.e. it is
-        created/destroyed/stopped/started/paused/resumed), a state change
-        event is generated in the uCPE Manager. The screen shown when this
-        option is chosen displays all events in the system, filtered to show
-        only VNF state change notifications.</para>
-      </listitem>
-    </itemizedlist>
+      <para>Typically, the Getting Started Guide of a VNF contains all necessary
+      information needed to onboard a VNF.</para>
 
-    <section id="onboarding_a_vnf">
-      <title>Onboarding a VNF (old)</title>
+      <section id="retrieve_art">
+        <title>Retrieving Artifacts</title>
 
-      <para>The VNF descriptor catalog table provides a button that allows you
-      to onboard a new (third-party) VNF into the catalog.</para>
+        <para>The user must first retrieve the necessary artifacts from the
+        VNF vendor:</para>
 
-      <figure>
-        <title>Onboard New VNF</title>
+        <orderedlist>
+          <listitem>
+            <para>Download the VNF from the commercial vendor.</para>
+          </listitem>
 
-        <mediaobject>
-          <imageobject>
-            <imagedata align="center"
-                       fileref="images/onboarding_a_new_vnf.png" scale="70" />
-          </imageobject>
-        </mediaobject>
-      </figure>
+          <listitem>
+            <para>Procure any VNF-specific files from the VNF vendor, e.g. license file.</para>
 
-      <section id="onboarding_a_vnf_wizard">
-        <title>Onboarding a VNF VM Image using the Onboarding Wizard</title>
+            <note>
+              <para>There are no standard ways of managing VNF licenses,
+              therefore no general guidelines can be provided. One example of
+              license handling that can be employed in the uCPE Manager is the
+              adding of a license during the Cloud-Init setup.</para>
+            </note>
+          </listitem>
 
-        <para><emphasis role="bold">How to onboard a VNF into the uCPE Manager
-        using the Onboarding Wizard</emphasis></para>
+          <listitem>
+            <para>Get access to the VNF specific VNF Manager for day 1 and 2
+            configuration (in cloud or for local deployment).</para>
+          </listitem>
+
+          <listitem>
+            <para>Procure the Getting Started Guide from the VNF vendor,
+            preferably for KVM deployment for VNF specific configuration
+            information.</para>
+          </listitem>
+        </orderedlist>
+      </section>
+
+      <section id="onboard_prep">
+        <title>Preparation</title>
+
+        <para>Once all needed downloadables, documentation and more have been
+        attained, preparation for onboarding must be completed:</para>
 
         <orderedlist>
           <listitem>
-            <para>Make sure the uCPE device is added and placed on the map in
-            the uCPE Manager.</para>
+            <para>Determine the use-case and performance requirements of the
+            VNF you wish to deploy:</para>
+
+            <itemizedlist spacing="compact">
+              <listitem>
+                <para>This decides what resources the VNF is configured for,
+                along with networking and day zero configurations.</para>
+
+                <note><para>Generally, the Getting Started Guide for the VNF
+                provides guidelines for resource allocation, but since
+                performance is dependent on hardware capacity, the right
+                resource allocation for deployment is determined
+                  through benchmarking.</para></note>
+              </listitem>
+
+              <listitem>
+                <para>Determine the amount of hardware resources needed for
+                the VNF (RAM, CPUs and Disk size).</para>
+              </listitem>
+
+              <listitem>
+                <para>Determine how many Network Interfaces the VNF will
+                use.</para>
+              </listitem>
+            </itemizedlist>
+          </listitem>
+
+          <listitem>
+            <para>Determine the day zero configuration method from the VNF
+            Getting Started guidelines.</para>
+
+            <note>
+              <para>For many VNFs, day zero configuration can be skipped in
+              early onboarding efforts when automation is not of
+              importance.</para>
+            </note>
+          </listitem>
+
+          <listitem>
+            <para>Determine any requirements needed by the Cloud-Init file
+            structure and the content needed when this structure is
+            used.</para>
           </listitem>
+        </orderedlist>
+      </section>
 
+      <section id="onboard_in_ucpemg">
+        <title>Onboarding into the uCPE Manager</title>
+
+        <para><emphasis role="bold">How to onboard a VNF into the uCPE Manager
+        </emphasis></para>
+
+        <orderedlist>
           <listitem>
             <para>Select from the top toolbar <literal>VNF</literal> -&gt;
-            <literal>Descriptors.</literal></para>
+            <literal>Descriptors</literal></para>
           </listitem>
 
           <listitem>
@@ -506,24 +532,24 @@
           </listitem>
 
           <listitem>
-            <para>When prompted by the following UI, make sure the <literal>VM
-            Image</literal> radio button is selected.</para>
+            <para>When prompted by the UI, make sure the <literal>VM
+            Image</literal> radio button at the top of the onboarding 
+              screen is selected, it will trigger a popup menu.</para>
           </listitem>
         </orderedlist>
 
-        <para>If you click the <literal>VM Image</literal> radio button at the
-        top of the onboarding screen, you will get a pop-up containing fields
-        which you can fill, suppling the necessary information about the VNF.
-        After providing the information and pressing the onboard button, the
-        uCPE Manager will create the VNF package and onboard it.</para>
+        <para>This menu contains data fields where both necessary and optional 
+          information about the VNF can be supplied. After doing so, press
+          the onboard button, the uCPE Manager will create the VNF package and onboard it.</para>
 
         <figure>
-          <title>Onboard a VNF using the Wizard</title>
+          <title>Onboard a VNF</title>
 
           <mediaobject>
             <imageobject>
               <imagedata align="center"
-                         fileref="images/onboard_a_vnf_image.png" scale="70" />
+                         contentwidth="600"
+                         fileref="images/onboard_a_vnf_image.png" />
             </imageobject>
           </mediaobject>
         </figure>
@@ -532,26 +558,26 @@
 
         <itemizedlist>
           <listitem>
-            <para><emphasis role="bold">VM Image File.</emphasis> This is the
-            Virtual Machine image file for the VNF itself. Typically, it is a
+            <para><emphasis role="bold">VM Image File</emphasis>. This is the
+            Virtual Machine image file for the VNF. Typically, it is a
             QCOW image. Press <literal>Choose File</literal> and select the
-            image to be uploaded.</para>
+            image you wish to upload.</para>
           </listitem>
 
           <listitem>
             <para><emphasis role="bold">Image Format</emphasis>. Select the
-            format which matches the image file.</para>
+            format which matches the image file format.</para>
           </listitem>
 
           <listitem>
-            <para><emphasis role="bold">VNF Type Name.</emphasis> This is the
+            <para><emphasis role="bold">VNF Type Name</emphasis>. This is the
             name that will be used to identify this VNF. It will be shown in
             the VNF tables.</para>
           </listitem>
 
           <listitem>
-            <para><emphasis role="bold">Description.</emphasis> This field
-            contains any description you want to provide. It is only displayed
+            <para><emphasis role="bold">Description</emphasis>. This field
+            contains any description provided and is only displayed
             in the GUI tables in the uCPE Manager.</para>
           </listitem>
 
@@ -562,21 +588,21 @@
           </listitem>
 
           <listitem>
-            <para><emphasis role="bold">Memory in MB.</emphasis> This is the
+            <para><emphasis role="bold">Memory in MB</emphasis>. This is the
             amount of memory (in megabytes) that will be provided to this type
             of VNF when it is instantiated. To determine the value for this
             field, consult the VNF vendor.</para>
           </listitem>
 
           <listitem>
-            <para><emphasis role="bold">Num of CPUs.</emphasis> The number of
+            <para><emphasis role="bold">Num of CPUs</emphasis>. The number of
             CPUs that will be dedicated to an instance of this VNF when
             created. To determine the value for this field, consult the VNF
             vendor.</para>
           </listitem>
 
           <listitem>
-            <para><emphasis role="bold">Storage in GB.</emphasis> How much
+            <para><emphasis role="bold">Storage in GB</emphasis>. How much
             disk space to provide an instance of this VNF. To determine the
             value for this field, consult the VNF vendor.</para>
           </listitem>
@@ -584,56 +610,31 @@
 
         <para><emphasis role="bold">Interfaces Tab</emphasis></para>
 
-        <figure>
-          <title>Interfaces Table</title>
-
-          <mediaobject>
-            <imageobject>
-              <imagedata align="center" fileref="images/interfaces_table.png"
-                         scale="70" />
-            </imageobject>
-          </mediaobject>
-        </figure>
-
         <para>Click on the <literal>Interfaces</literal> tab to show the
         Interfaces table.</para>
 
         <para>This table will contain the interfaces required by this VNF to
         be configured, when creating an instance. Consult the VNF vendor to
         determine which and how many are required. Each interface requires a
-        name, and optionally a description, used by the uCPE Manager
-        only.</para>
+        name, and optionally a description, used only by the uCPE Manager.</para>
 
         <para><emphasis role="bold">Cloud Init Tab</emphasis></para>
 
         <para>Click the <literal>Clout Init</literal> tab to provide the
-        Clout-Init configuration.</para>
-
-        <figure>
-          <title>Cloud-Init Tab</title>
-
-          <mediaobject>
-            <imageobject>
-              <imagedata align="center" fileref="images/cloud_init_tab.png"
-                         scale="70" />
-            </imageobject>
-          </mediaobject>
-        </figure>
-
-        <para>As shown in the picture above, there are three fields that need
-        to be populated:</para>
+        Clout-Init configuration. There are three fields that need to be 
+          populated:</para>
 
         <orderedlist>
           <listitem>
             <para><emphasis role="bold">Cloud-Init
             Datasource</emphasis></para>
 
-            <para>To onboard the VNF you must specify the<literal> Cloud-Init
-            Datasource</literal> that the VNF uses. You can get this
-            information from the VNF Vendor. Choose one of the following
+            <para>To onboard a VNF you must specify the <literal>Cloud-Init
+            Datasource</literal> that the VNF uses. This
+            information is procured from the VNF Vendor. Choose one of the following
             methods to specify the datasource:</para>
 
-            <itemizedlist>
+            <itemizedlist spacing="compact">
               <listitem>
                 <para><emphasis role="bold">None</emphasis>. If there is no
                 datasource.</para>
@@ -662,7 +663,7 @@
           <listitem>
             <para><emphasis role="bold">Cloud-Init Disk Type</emphasis></para>
 
-            <para>The <literal>Cloud-Init Disk Type </literal>field must be
+            <para>The <literal>Cloud-Init Disk Type</literal> field must be
             set to either <literal>Disk</literal>, or
             <literal>CD-ROM</literal>, depending on what the VNF requires. You
             can get this information from the VNF Vendor.</para>
@@ -675,24 +676,13 @@
             you choose <literal>ConfigDrive</literal> as the Cloud-Init
             Datasource. For each content file added, you must provide a
             <literal>Path</literal>. When a user uses the uCPE Manager to
-            create an instance of one of these VNFs, they will be prompted to
+            create an instance for multiple VNFs, they will be prompted to
             provide a data file for each entry in this table. Each type of VNF
             will require different cloud-init files, e.g.: a license
             file.</para>
           </listitem>
         </orderedlist>
 
-        <figure>
-          <title>Content Files Table example</title>
-
-          <mediaobject>
-            <imageobject>
-              <imagedata align="center"
-                         fileref="images/content_files_table.png" scale="70" />
-            </imageobject>
-          </mediaobject>
-        </figure>
-
         <para>Consult with the VNF vendor to determine what is required for
         the VNF you are onboarding.</para>
 
@@ -700,23 +690,11 @@
 
         <para>In this table, you can enter values for properties that will be
         used during instantiation of the VNF. The values will augment the
-        default values in the Domain.XML file used by libvirt/virsh (running
-        in NFV Access) when creating an instance of the VNF. These property
-        names are well known to the uCPE NFV Access software, and more will be
-        added in future versions. You will need to consult with the VNF Vendor
+          default values in the <filename>Domain.XML</filename> file used 
+          by <literal>libvirt/virsh</literal> (running in NFV Access) when 
+          creating an instance of the VNF. Consult with the VNF Vendor
         or ENEA support for values needed by specific VNFs.</para>
 
-        <figure>
-          <title>Properties Tab</title>
-
-          <mediaobject>
-            <imageobject>
-              <imagedata align="center" fileref="images/properties_tab.png"
-                         scale="70" />
-            </imageobject>
-          </mediaobject>
-        </figure>
-
         <para><emphasis role="bold">Property Values</emphasis></para>
 
         <para><literal>numHugePages</literal> defines the number of huge
@@ -724,203 +702,16 @@
       </section>
     </section>
 
-    <section id="onboarding_a_vnf2">
-      <title>Onboarding a VNF (copied from VNF Onboarding Guide)</title>
-
-      <para>The onboarding of a VNF means adding it to the Enea uCPE Manager
-      VNF Catalog and preparing it for instantiation (deployment on connected
-      uCPE devices). This is accomplished using the Enea uCPE Manager
-      Onboarding Wizard, a graphical user interface specifically designed to
-      make VNF onboarding simple and fast.</para>
-
-      <para>Typically, the VNF's Getting Started Guide contains all necessary
-      information needed to onboard a VNF using the Onboarding Wizard. This
-      present guide however, provides a number of examples of how to onboard
-      specific commercial VNFs.</para>
-
-      <para>The following sections detail the basic steps needed to
-      successfully onboard a VNF in the Enea uCPE Manager.</para>
-
-      <section id="retrieve_art">
-        <title>Retrieving Artifacts</title>
-
-        <para>The user must first retrieve the necessary artifacts from the
-        VNF vendor:</para>
-
-        <orderedlist>
-          <listitem>
-            <para>Download the VNF from the commercial vendor.</para>
-          </listitem>
-
-          <listitem>
-            <para>Get any VNF specific license from the VNF vendor.</para>
-
-            <note>
-              <para>There are no standard ways of managing VNF licenses,
-              therefore no general guidelines can be provided. One example of
-              license handling that can be employed in the uCPE Manager is the
-              adding of a license during the Cloud-Init setup. The ConfigDrive
-              value is provided in the Fortios specific guidelines.</para>
-            </note>
-          </listitem>
-
-          <listitem>
-            <para>Get access to the VNF specific VNF Manager for day 1 and 2
-            configuration (in cloud or for local deployment).</para>
-          </listitem>
-
-          <listitem>
-            <para>Procure the Getting Started Guide from the VNF vendor,
-            preferably for KVM deployment for VNF specific configuration
-            information.</para>
-          </listitem>
-        </orderedlist>
-      </section>
-
-      <section id="onboard_prep">
-        <title>Preparation</title>
-
-        <para>Once all needed downloadables, documentation and more have been
-        attained, preparation for onboarding must be completed:</para>
-
-        <orderedlist>
-          <listitem>
-            <para>Determine the use-case and performance requirements of the
-            VNF you wish to deploy.</para>
-
-            <itemizedlist>
-              <listitem>
-                <para>This decides what resources the VNF is configured for,
-                along with networking and day zero configurations.</para>
-
-                <para>Generally, the Getting Started Guide for the VNF
-                provides guidelines for resource allocation, but since
-                performance is dependent on hardware capacity, the right
-                resource allocation for deployment is typically determined
-                through benchmarking.</para>
-              </listitem>
-
-              <listitem>
-                <para>Determine the amount of hardware resources needed for
-                the VNF (RAM, CPUs and Disk size).</para>
-              </listitem>
-
-              <listitem>
-                <para>Determine how many Network Interfaces the VNF shall
-                use.</para>
-              </listitem>
-            </itemizedlist>
-          </listitem>
-
-          <listitem>
-            <para>Determine the day zero configuration method from the VNF
-            Getting Started guidelines.</para>
-
-            <note>
-              <para>For many VNFs, day zero configuration can be skipped in
-              early onboarding efforts when automation is not of
-              importance.</para>
-            </note>
-          </listitem>
-
-          <listitem>
-            <para>Determine any requirements needed by the Cloud-Init file
-            structure and the content needed for the VNF when Cloud-Init is
-            used.</para>
-          </listitem>
-        </orderedlist>
-      </section>
-
-      <section id="onboarding2">
-        <title>Onboarding the VNF</title>
-
-        <orderedlist>
-          <listitem>
-            <para>Enter the Enea uCPE Manager and choose VNF-&gt;Descriptors
-            in the GUI.</para>
-          </listitem>
-
-          <listitem>
-            <para>Click <literal>Onboard</literal> to start the onboarding
-            procedure.</para>
-          </listitem>
-
-          <listitem>
-            <para>Fill in all mandatory fields in the popup menu: Name, Image,
-            RAM, CPUs, Disk.</para>
-          </listitem>
-
-          <listitem>
-            <para>Define the VNF's Network Interfaces and give them
-            descriptive names.</para>
-          </listitem>
-
-          <listitem>
-            <para>Configure the Cloud-Init settings, starting with the
-            Datasource:</para>
-
-            <itemizedlist spacing="compact">
-              <listitem>
-                <para>Choose <literal>None</literal> if Cloud-Init is not
-                used.</para>
-              </listitem>
-
-              <listitem>
-                <para>Choose <literal>ConfigDrive</literal>,
-                <literal>NoCloud</literal> or <literal>ISO</literal> depending
-                on the VNF specific Cloud-Init implementation.</para>
-              </listitem>
-
-              <listitem>
-                <para>Choose the Cloud-Init mount method based on the VNF
-                specific Cloud-Init implementation.</para>
-              </listitem>
-
-              <listitem>
-                <para>Configure any VNF specific Cloud-Init files according to
-                VNF specific documentation.</para>
-              </listitem>
-            </itemizedlist>
-          </listitem>
-
-          <listitem>
-            <para>Additional Properties (in the Properties Tab) are typically
-            not needed and can be ignored.</para>
-          </listitem>
-
-          <listitem>
-            <para>Click <literal>Onboard</literal> to add the VNF to the Enea
-            uCPE Manager VNF Catalog.</para>
-          </listitem>
-        </orderedlist>
-
-        <para>When the onboarding is complete, the VNF will appear in the VNF
-        Catalog and can be used for deploying services on the uCPE
-        devices.</para>
-      </section>
-    </section>
-
     <section id="instantiating_a_vnf">
-      <title>Instantiating a VNF (old)</title>
+      <title>Instantiating a VNF</title>
 
-      <para>Once the VNF has been onboarded, you can instantiate a VNF on a
-      specific uCPE device.</para>
-
-      <para><emphasis role="bold">How to instantiate a VNF using the
-      Wizard</emphasis></para>
+      <para>When a VNF is onboarded and available in the VNF catalog, it can
+      be instantiated on connected uCPE devices. The configurations 
+        provided when the VNF is onboarded, serve as a template for instantiation. 
+        Follow the instructions below to instantiate a VNF:</para>
 
       <orderedlist>
         <listitem>
-          <para>Make sure the uCPE device is added and placed on the map in
-          the uCPE Manager.</para>
-        </listitem>
-
-        <listitem>
-          <para>Make sure the VNF has been onboarded into the uCPE
-          Manager.</para>
-        </listitem>
-
-        <listitem>
           <para>Select from the top toolbar <literal>VNF</literal> -&gt;
           <literal>Instances</literal></para>
         </listitem>
@@ -930,205 +721,91 @@
         </listitem>
 
         <listitem>
-          <para>When prompted by the following UI, fill the required
-          fields.</para>
+          <para>Fill out the following mandatory fields:</para>
+
+          <itemizedlist spacing="compact">
+            <listitem>
+              <para>Name (a descriptive name).</para>
+            </listitem>
+
+            <listitem>
+              <para>Device (the uCPE device to instantiate the VNF on).</para>
+            </listitem>
+
+            <listitem>
+              <para>Networking Configuration:</para>
+
+              <itemizedlist spacing="compact">
+                <listitem>
+                  <para>Connect each configured NIC with a bridge, SR-IOV or
+                  PCI Passthrough.</para>
+                </listitem>
+
+                <listitem>
+                  <para>Set up each NIC with a driver method (DPDK or
+                  e1000).</para>
+                </listitem>
+              </itemizedlist>
+
+              <note>
+                <para>All configured NICs must be set up before instantiating
+                a VNF. Failure to do so will end in a failed
+                instantiation.</para>
+              </note>
+            </listitem>
+          </itemizedlist>
         </listitem>
-      </orderedlist>
-
-      <figure>
-        <title>Instantiating a VNF</title>
 
-        <mediaobject>
-          <imageobject>
-            <imagedata align="center" fileref="images/instantiate_a_vnf.png"
-                       scale="70" />
-          </imageobject>
-        </mediaobject>
-      </figure>
-
-      <para>There are a number of parameters to be supplied before the VNF can
-      be instantiated:</para>
-
-      <itemizedlist>
         <listitem>
-          <para><emphasis role="bold">Name</emphasis>. The name of the
-          VNF.</para>
+          <para>Add VNF-specific configuration data by uploading a Cloud-Init file
+          (when the Cloud-Init is used).</para>
         </listitem>
 
         <listitem>
-          <para><emphasis role="bold">VNF Type</emphasis>. The name of the
-          onboarded VNF. In this case <literal>VProbe</literal> VNF.</para>
+          <para>Add any VNF-specific files (e.g license files).</para>
         </listitem>
 
         <listitem>
-          <para><emphasis role="bold">Flavour</emphasis>. The flavour of VNF
-          (as specified in the descriptor) you would like to
-          instantiate.</para>
+          <para>Hit the <literal>Create</literal> button to deploy the
+          VNF and run it on the specified uCPE device.</para>
         </listitem>
-
-        <listitem>
-          <para><emphasis role="bold">Device</emphasis>. The uCPE device on
-          which to instantiate a VNF, i.e. the uCPE device that will run this
-          VNF.</para>
-        </listitem>
-
-        <listitem>
-          <para><emphasis role="bold">Auto-start</emphasis>. If checked, the
-          VNF will be stopped and started when unreachable. When the device
-          reports that it has lost connection to the VNF, the uCPE Manager
-          will ask the device to terminate the VM and then start it up again.
-          If unchecked, only a <literal>Disconnected</literal> notification
-          will appear in the uCPE Manager.</para>
-        </listitem>
-      </itemizedlist>
-
-      <para>Hitting the <literal>Create</literal> button will cause the VNF to
-      be instantiated and run on the specified uCPE device.</para>
+      </orderedlist>
 
       <para>Selecting the<literal> VNF -&gt; Events</literal> menu will show
-      that the VNF was created and a connection was established:</para>
-
-      <figure>
-        <title>VNF Events menu</title>
-
-        <mediaobject>
-          <imageobject>
-            <imagedata align="center" fileref="images/instantiate_a_vnf4.png"
-                       scale="70" />
-          </imageobject>
-        </mediaobject>
-      </figure>
+      that the VNF was created and a connection was established.</para>
     </section>
 
-    <section id="instantiating_a_vnf2">
-      <title>Instantiating a VNF (copied from VNF Onboarding Guide)</title>
+    <section id="enter_console">
+      <title>Entering the VNF Console</title>
 
-      <para>When a VNF is onboarded and available in the VNF catalog, it can
-      be instantiated (deployed) on connected uCPE devices. The instantiation
-      wizard uses the configurations provided when the VNF is onboarded, as a
-      template for instantiation. Before the instantiation, however, the uCPE
-      device needs to be prepared:</para>
+      <para>Once the VNF is deployed, the VNF console can be entered using SSH
+      and virsh commands. The VNF Console is a typical starting point for
+      determining a successful deployment and configuring a VNF beyond Day
+      Zero.</para>
 
       <orderedlist>
         <listitem>
-          <para>Physical NICs used with the VNF directly (through SR-IOV or
-          PCI Passthrough) or indirectly (through bridges) need to be
-          configured (Device-&gt;Configuration-&gt;OpenVSwitch-&gt;Host
-          Interfaces).</para>
-
-          <note>
-            <para>Before configuring any physical NICs determine which is used
-            for managing the uCPE device. Altering the configuration of a NIC
-            may cause connectivity issues.</para>
-          </note>
+          <para>SSH to the uCPE device from the Enea uCPE Manager (<literal>Device-&gt;SSH</literal>) 
+            with default user and password: <literal>root</literal>.</para>
         </listitem>
 
         <listitem>
-          <para>Add any needed bridges, connecting them to the physical NICs
-          previously configured or making them integration bridges (without
-          physical NIC) for service chaining.</para>
+          <para>In SSH:</para>
+
+          <orderedlist spacing="compact">
+            <listitem>
+              <para>Use the <command>virsh list</command> command to list all
+              running VNFs and to determine the VNF's instance number.</para>
+            </listitem>
+
+            <listitem>
+              <para>Use the <command>virsh console &lt;instance
+              number&gt;</command> command to enter the VNF-specific
+              console.</para>
+            </listitem>
+          </orderedlist>
         </listitem>
       </orderedlist>
-
-      <para>Once the physical NICs and bridges are configured, the VNF can be
-      instantiated using the Instantiation Wizard.</para>
-
-      <section id="using_wiz2">
-        <title>Using the Instantiation Wizard</title>
-
-        <orderedlist>
-          <listitem>
-            <para>Enter the Instantiation Wizard by accessing
-            VNF-&gt;Instances and hitting <literal>Add</literal>.</para>
-          </listitem>
-
-          <listitem>
-            <para>Fill out the following mandatory fields:</para>
-
-            <itemizedlist spacing="compact">
-              <listitem>
-                <para>Name (a descriptive name).</para>
-              </listitem>
-
-              <listitem>
-                <para>Device (the uCPE device to instantiate the VNF
-                on).</para>
-              </listitem>
-
-              <listitem>
-                <para>Networking Configuration:</para>
-
-                <itemizedlist spacing="compact">
-                  <listitem>
-                    <para>Connect each configured NIC with a bridge, SR-IOV or
-                    PCI Passthrough.</para>
-                  </listitem>
-
-                  <listitem>
-                    <para>Set up each NIC with a driver method (DPDK or
-                    e1000).</para>
-                  </listitem>
-                </itemizedlist>
-
-                <note>
-                  <para>All configured NICs must be set up before
-                  instantiating a VNF. Failure to do so will end in a failed
-                  instantiation.</para>
-                </note>
-              </listitem>
-            </itemizedlist>
-          </listitem>
-
-          <listitem>
-            <para>Add VNF specific configuration by uploading a Cloud-Init
-            file (when the Cloud-Init is used).</para>
-          </listitem>
-
-          <listitem>
-            <para>Add any VNF specific files (e.g license files).</para>
-          </listitem>
-
-          <listitem>
-            <para>Hit the <literal>Create</literal> button to deploy the
-            VNF.</para>
-          </listitem>
-        </orderedlist>
-      </section>
-
-      <section id="enter_console">
-        <title>Entering the VNF Console</title>
-
-        <para>Once the VNF is deployed, the VNF console can be entered using
-        SSH and virsh commands. The VNF Console is a typical starting point
-        for determining a successful deployment and configuring a VNF beyond
-        Day Zero.</para>
-
-        <orderedlist spacing="compact">
-          <listitem>
-            <para>SSH to the uCPE device from the Enea uCPE Manager
-            (Device-&gt;SSH) with default user and password:
-            <literal>root</literal>.</para>
-          </listitem>
-
-          <listitem>
-            <para>In SSH:</para>
-
-            <orderedlist>
-              <listitem>
-                <para>Use the <command>virsh list</command> command to list
-                all running VNFs and to determine the VNF's instance
-                number.</para>
-              </listitem>
-
-              <listitem>
-                <para>Use the <command>virsh console &lt;instance
-                number&gt;</command> command to enter the VNF specific
-                console.</para>
-              </listitem>
-            </orderedlist>
-          </listitem>
-        </orderedlist>
-      </section>
     </section>
   </section>
 </chapter>