Merge "GettingStarted: updated VNF Mangagement section"

14 files changed, 503 insertions, 73 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml b/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml
index 6115af0..d0e25b5 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml
@@ -199,13 +199,13 @@
       <title>PCI Passthrough Interface Type</title>
 
       <para>For PCI Passthrough the user does not have to configure a physical
-      interface, instead simply select the PCI address and connect it to
+      interface, instead simply select the PCI address and connect it to a
       virtual port at the VNF instantiation step.</para>
     </section>
   </section>
 
-  <section id="vnf_onboarding">
-    <title>VNF on-boarding</title>
+  <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
@@ -222,45 +222,468 @@
     appropriate, heal and upgrade it when necessary and tear it down at the
     right moment.</para>
 
-    <para><emphasis role="bold">How to on-board a VNF</emphasis></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>
 
-    <orderedlist>
+    <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>
+
+    <itemizedlist>
       <listitem>
-        <para>To on-board a VNF, select a target device on the map and click
-        the VNF button in the top toolbar:</para>
+        <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>
+
+      <listitem>
+        <para><literal>Instances</literal>: Choosing this option lets you
+        instantiate (or destroy) VNFs on a given uCPE host (the
+        <literal>target</literal>). As part of instantiation, the appropriate
+        UI, which includes the UI provided by the
+        <literal>VnfGuiProcessor</literal> described in Section 6.2 is
+        displayed to the user to supply instantiation parameters.</para>
+      </listitem>
+
+      <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>
+
+    <section id="onboarding_a_vnf">
+      <title>Onboarding a VNF</title>
+
+      <para>The VNF descriptor catalog table provides a button that allows you
+      to onboard a new (third-party) VNF bundle into the catalog.</para>
+
+      <figure>
+        <title>Onboard New VNF</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center"
+                       fileref="images/onboarding_a_new_vnf.png" scale="70" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <para>You can onboard using one of the following methods:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Onboard a VNF Package.</para>
+        </listitem>
+
+        <listitem>
+          <para>Directly onboard a VNF VM Image (such as a QCOW) using the
+          onboarding wizard.</para>
+        </listitem>
+      </itemizedlist>
+
+      <section id="onboarding_a_bundled_vnf">
+        <title>Onboarding a bundled VNF package</title>
+
+        <para><emphasis role="bold">How to onboard a VNF onto the uCPE
+        Manager</emphasis></para>
+
+        <orderedlist>
+          <listitem>
+            <para>Click the <literal>On-board</literal> button.</para>
+          </listitem>
+
+          <listitem>
+            <para>When prompted by the following UI, make sure the
+            <literal>VNF Package</literal> radio button is selected. </para>
+          </listitem>
+
+          <listitem>
+            <para> Click <literal>Choose File</literal> and choose the VNF
+            Package ZIP archive, e.g <literal>VProbe.zip</literal>, which
+            represents the VNF bundle. </para>
+          </listitem>
+
+          <listitem>
+            <para>Click <literal>Send</literal>.</para>
+          </listitem>
+        </orderedlist>
 
         <figure>
-          <title>Onboard New VNF</title>
+          <title>Onboarding a bundled VNF package</title>
 
           <mediaobject>
             <imageobject>
-              <imagedata align="center" fileref="images/vnf_onboard.png"
-                         scale="50" />
+              <imagedata align="center"
+                         fileref="images/onboard_a_vnf_send.png" scale="70" />
             </imageobject>
           </mediaobject>
         </figure>
-      </listitem>
 
-      <listitem>
-        <para>Click on the Descriptors -&gt; On-board -&gt; Browse options,
-        and select the VNF bundle file downloaded from the Enea portal (e.g.
-        ClavisterCosStream.zip), before pressing "Send".</para>
+        <para>This will cause the VNF Manager to do the following: Upload the
+        ZIP file and stage it in a temporary location. Unzip it and verify its
+        contents. Extract the various components and stash them in the
+        appropriate location(s) for use by the uCPE Manager, so that the VNF
+        can be treated by the uCPE Manager as a device. Then to add the VNF
+        descriptor to the VNF Descriptor Catalog.</para>
 
-        <para>Wait for the "Onboarding Status" popup to display the
-        confirmation message and select OK:</para>
+        <para>Once these operations are complete, you will be provided with a
+        success message.</para>
+      </section>
+
+      <section id="onboarding_a_bundled_vnf_wizard">
+        <title>Onboarding a VNF VM Image using the Onboarding Wizard</title>
+
+        <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>
 
         <figure>
-          <title>VNF Manager</title>
+          <title>Onboard a VNF using the Wizard</title>
 
           <mediaobject>
             <imageobject>
-              <imagedata align="center" fileref="images/vnf_manager.png"
-                         scale="75" />
+              <imagedata align="center"
+                         fileref="images/onboard_a_vnf_image.png" scale="70" />
             </imageobject>
           </mediaobject>
         </figure>
-      </listitem>
-    </orderedlist>
+
+        <para><emphasis role="bold">Main fields</emphasis></para>
+
+        <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
+            QCOW image. Press <literal>Choose File</literal> and select the
+            image to be uploaded.</para>
+          </listitem>
+
+          <listitem>
+            <para><emphasis role="bold">Image Format</emphasis>. Select the
+            format which matches the image file.</para>
+          </listitem>
+
+          <listitem>
+            <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
+            in the GUI tables in the uCPE Manager.</para>
+          </listitem>
+
+          <listitem>
+            <para><emphasis role="bold">Version</emphasis>. This is the
+            version of the current VNF that you are hosting. It's used to
+            distinguish this VNF from other versions of the same type.</para>
+          </listitem>
+
+          <listitem>
+            <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
+            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
+            disk space to provide an instance of this VNF. To determine the
+            value for this field, consult the VNF vendor.</para>
+          </listitem>
+        </itemizedlist>
+
+        <para><emphasis role="bold">Interfaces Table</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>
+
+        <para><emphasis role="bold">Cloud-Init Tab</emphasis></para>
+
+        <para>You must provide Clout-Init configuration for the VNF. Click the
+        <literal>Clout Init</literal> tab.</para>
+
+        <figure>
+          <title>Cloud-Init Tab</title>
+
+          <mediaobject>
+            <imageobject>
+              <imagedata align="center" fileref="images/cloud_init_tab.png"
+                         scale="70" />
+            </imageobject>
+          </mediaobject>
+        </figure>
+
+       <para>Shown in the picture above are three fields that need to be populated:
+       Cloud-Init Datasource, Cloud-Init Disk Type and the Content Files Table.</para>
+
+       <para>To onboard the VNF you must specify the Cloud-Init datasource that the VNF
+       uses. You can get this information from the VNF Vendor. Choose one of the following
+       methods to specify the datasource:</para>
+
+        <itemizedlist>
+          <listitem>
+           <para><emphasis role="bold">ConfigDrive</emphasis>. This method allows you to provide
+           any number of content-data files containing Cloud-Init data.</para></listitem>
+           <listitem>
+  
+          <para><emphasis role="bold">NoCloud</emphasis>. This is a simpler method that uses only
+        one cloud init file (User-Data).</para></listitem>
+        </itemizedlist>
+
+        <para>The Cloud-Init Disk Type 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>
+
+        <para>The Content Files Table is used ONLY if you chose <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 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>
+
+        <para>Consult with the VNF vendor to determine what is required for the VNF you
+        are onboarding.</para>
+
+        <figure>
+          <title>Content Files Table example</title>
+
+          <mediaobject>
+            <imageobject>
+              <imagedata align="center"
+                         fileref="images/content_files_table.png" scale="70" />
+            </imageobject>
+          </mediaobject>
+        </figure>
+
+        <para><emphasis role="bold">Properties Tab</emphasis></para>
+
+        <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 libvert/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 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
+        memory pages the VNF uses (for DPDK). Needed for Clavister COS
+        Stream.</para>
+      </section>
+    </section>
+
+    <section id="instantiating_a_vnf">
+      <title>Instantiating a VNF</title>
+
+        <para>Once the VNF bundle has been onboarded, you can instantiate a
+        VNF on a specific uCPE host:</para>
+
+        <para>Launch the <literal>VNF instance</literal> table by choosing the
+        <literal>Instances</literal> option from the <literal>VNF</literal> menu.
+        This will display the table of VNF instances controlled by the VNF Manager.
+        Hit the <literal>Add</literal> button to create a new instance, as shown below:</para>
+
+      <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">VNF Type</emphasis>. The
+          <literal>VProbe</literal> VNF, in this case.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">VIM</emphasis>. This stands for <literal>
+         Virtual Infrastructure Manager</literal>, the target host on which to
+         instantiate a VNF, i.e. the target uCPE host that will run this VNF.</para>
+
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Name</emphasis>. The name of the
+          VNF.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">VNF Flavor</emphasis>. The flavor of VNF
+          (as specified in the descriptor) you would like to
+          instantiate.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Device Name</emphasis>. The name by
+          which the VNF will be known in the uCPE Manager, if the <literal>Manage
+          Device</literal> checkbox is checked. If unchecked, the VNF will not
+          be shown as a managed device in the uCPE Manager.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Instantiation Parameters</emphasis>.
+          This section contains all the parameters a user needs to supply when
+          instantiating a VNF of this type. The <literal>VProbe</literal> VNF
+          needs to specify network information (network name and IP address)
+          for two separate interfaces (enp0s9 and enp0s10 respectively). Every
+          VNF type will have a different UI section here. This section is
+          populated by the <literal>getInstanceGui()</literal> method in the
+          <literal>VnfGuiProcessorIf</literal>
+          interface, see Section 6.1 to understand exactly how the VProbe
+          method causes the above GUI section to be displayed.</para>
+        </listitem>
+
+        <listitem>
+          <para><emphasis role="bold">Auto-start</emphasis>. If checked, the
+          VNF will be stopped and started when unreachable. When the VIM
+          reports that it has lost connection to the VNF, the uCPE Manager will
+          ask the VIM 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 uCPE target specified above. The
+      following operations will now take place:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Check if the uCPE already has the VNF Flavor definition in its
+          flavor store; if not create a new Flavor definition on the
+          uCPE.</para>
+        </listitem>
+
+        <listitem>
+          <para>Check if the uCPE already has the VNF image in its image
+          store; if not, upload the image and create a new Image definition on
+          the uCPE.</para>
+        </listitem>
+
+        <listitem>
+          <para>Take in the user parameters and create the following:</para>
+
+          <itemizedlist>
+            <listitem>
+            <para><emphasis role="bold">Networking information.</emphasis>
+             Use the <literal>VnfGuiProcessorIf
+              </literal>class<literal> getConnectionInfo()</literal> method to
+              convert user parameters into networking information objects
+              (refer to Section 6.1 for the <literal>VProbe</literal>
+              VNF).</para>
+            </listitem>
+          </itemizedlist>
+
+          <itemizedlist>
+            <listitem>
+              <para><emphasis role="bold">Cloud-init.</emphasis>
+               Use generic VNF instance information in
+              conjunction with the networking information objects from
+              above and invoke the <literal>getCloudInitData()</literal> method on the
+              <literal>VnfProcessorIf</literal> class (refer to Section 6.2 for how this is done
+              for the <literal>VProbe</literal> VNF). The cloud-init data is
+              the script that will be executed by the VNF when it starts up
+              for the first time only. It is responsible for setting up the
+              initial system configuration to what is required by the VNF to
+              run correctly, setting up the network interfaces, static IP
+              addresses, etc.</para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>Make the uCPE create the VNF with the specified image,
+          flavor and cloud-init data via a NETCONF request and waits for it to
+          be created and started up.</para>
+        </listitem>
+
+        <listitem>
+          <para>If successful, optionally add the newly created VNF as a
+          device in the uCPE Manager.</para>
+        </listitem>
+      </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>
+    </section>
   </section>
 
   <section id="zero_touch_prov">
@@ -273,13 +696,13 @@
     without additional manual intervention by an operator.</para>
 
     <para>A variety of operations can occur as part of ZTP such as initial
-    device setup, configuration of managed objects, etc. The goal is to set
-    up a device to the maximum possible extent without forcing an operator
-    to be physically present (initially) to manage the device.</para>
+    device setup, configuration of managed objects, etc. The goal is to set up
+    a device to the maximum possible extent without forcing an operator to be
+    physically present (initially) to manage the device.</para>
 
     <para>In order to create a static configuration supporting ZTP, the uCPE
-    Manager user needs to identify the <literal>Device ID</literal> of the machine running NFV
-    Access.</para>
+    Manager user needs to identify the <literal>Device ID</literal> of the
+    machine running NFV Access.</para>
 
     <para>During the automatic installation process when the
     <literal>Automatic install</literal> step is reached, enter the option
@@ -288,7 +711,7 @@
     linkend="install_ena_stick" />, step 7 for how to set the uCPE Manager IP
     address at boot time. The Device ID will be listed in the installer under
     the <literal>Customize kernel parameters</literal> menu.</para>
-     
+
     <para>With the address parameter set, run
     <literal>list_deviceID.sh</literal> after NFV Access is installed and
     booted, to get the device ID of the target.</para>
@@ -309,9 +732,9 @@
     <section id="adding_a_device">
       <title>Adding a Device</title>
 
-      <para>The uCPE Manager must be configured to bring the target device under
-      management. This is done by using the <literal>Devices -&gt; Manage
-      -&gt; Add</literal> menu:</para>
+      <para>The uCPE Manager must be configured to bring the target device
+      under management. This is done by using the <literal>Devices -&gt;
+      Manage -&gt; Add</literal> menu:</para>
 
       <figure>
         <title>Adding a Device</title>
@@ -328,62 +751,67 @@
 
       <itemizedlist>
         <listitem>
-          <para>Type. The type of device to be added, i.e <literal>Enea universal uCPE
-          </literal>.</para>
+          <para>Type. The type of device to be added, i.e <literal>Enea
+          universal uCPE </literal>.</para>
         </listitem>
       </itemizedlist>
 
       <itemizedlist>
         <listitem>
-          <para>Name. The name by which the device is referred to in the uCPE Manager.</para>
+          <para>Name. The name by which the device is referred to in the uCPE
+          Manager.</para>
         </listitem>
       </itemizedlist>
 
       <itemizedlist>
         <listitem>
-          <para>IP Address. IP address of the device. If a device is installed under a
-          local/private network and not directly visible to the uCPE Manager machine, the
-          Gateway IP of the private network must be used.</para>
+          <para>IP Address. IP address of the device. If a device is installed
+          under a local/private network and not directly visible to the uCPE
+          Manager machine, the Gateway IP of the private network must be
+          used.</para>
         </listitem>
       </itemizedlist>
 
       <itemizedlist>
         <listitem>
-          <para>SSH Port. The NETCONF Port used for communications. This is a relevant
-          parameter if the standard NETCONF SSH (i.e. not Call-Home) is being used. Default
-          is set to 22.</para>
+          <para>SSH Port. The NETCONF Port used for communications. This is a
+          relevant parameter if the standard NETCONF SSH (i.e. not Call-Home)
+          is being used. Default is set to 22.</para>
         </listitem>
       </itemizedlist>
 
       <itemizedlist>
         <listitem>
-          <para>SSH User Name. The user name for SSH connectivity. Default user is
-           <literal>root</literal>.</para>
+          <para>SSH User Name. The user name for SSH connectivity. Default
+          user is <literal>root</literal>.</para>
         </listitem>
       </itemizedlist>
 
       <itemizedlist>
         <listitem>
-          <para>SSH Password/Private Key/Passphrase. The Authentication Credentials, use
-          one of the aforementioned as appropriate. Default password is empty.</para>
+          <para>SSH Password/Private Key/Passphrase. The Authentication
+          Credentials, use one of the aforementioned as appropriate. Default
+          password is empty.</para>
         </listitem>
       </itemizedlist>
 
       <itemizedlist>
         <listitem>
-          <para>Device Calls Home. This checkbox indicates the direction of device
-           communications. When cleared, the uCPE Manager will initiate a connection to
-           the device. When checked, the device will initiate a connection by opening a
-           socket to the uCPE Manager for NETCONF traffic (over SSH), while the uCPE
-           Manager waits for device connection.</para>
+          <para>Device Calls Home. This checkbox indicates the direction of
+          device communications. When cleared, the uCPE Manager will initiate
+          a connection to the device. When checked, the device will initiate a
+          connection by opening a socket to the uCPE Manager for NETCONF
+          traffic (over SSH), while the uCPE Manager waits for device
+          connection.</para>
         </listitem>
       </itemizedlist>
 
       <itemizedlist>
         <listitem>
-          <para>Device ID. The unique instance ID of the device. This is what links a
-          device to its day-0 configuration (stored in the offline configuration system).
-          It is a required field if you want to perform Zero-Touch Provisioning.</para>
+          <para>Device ID. The unique instance ID of the device. This is what
+          links a device to its day-0 configuration (stored in the offline
+          configuration system). It is a required field if you want to perform
+          Zero-Touch Provisioning.</para>
         </listitem>
       </itemizedlist>
     </section>
@@ -413,19 +841,21 @@
       </figure>
 
       <para>Specify the exact value of the <literal>Device ID</literal> in the
-      required field. This will tag the device needed for the initial configuration
-      provided by the offline configuration store. Choose <literal>Merge</literal> as
-      the Default Upload Method if you do not want any boot configuration set on the
-      device, to be wiped out. Selecting <literal>Replace</literal> will set the
-      entire device configuration to match values in the offline configuration.</para>
-
-      <para>After creating the Offline Config Store, access the device through <literal>
-      Applications -> offline config -> Config App</literal> and provision it with the
-      required initial configuration. This operation mirrors what happens during regular
-      offline configuration.</para>
-
-      <para>Now that the store has been provisioned successfully, it is ready to send
-      this configuration to the device when it first comes online.</para>
+      required field. This will tag the device needed for the initial
+      configuration provided by the offline configuration store. Choose
+      <literal>Merge</literal> as the Default Upload Method if you do not want
+      any boot configuration set on the device, to be wiped out. Selecting
+      <literal>Replace</literal> will set the entire device configuration to
+      match values in the offline configuration.</para>
+
+      <para>After creating the Offline Config Store, access the device through
+      <literal> Applications -&gt; offline config -&gt; Config App</literal>
+      and provision it with the required initial configuration. This operation
+      mirrors what happens during regular offline configuration.</para>
+
+      <para>Now that the store has been provisioned successfully, it is ready
+      to send this configuration to the device when it first comes
+      online.</para>
     </section>
 
     <section id="initial_communications">
@@ -436,17 +866,17 @@
 
       <orderedlist>
         <listitem>
-          <para>If Call-Home is not enabled/supported, the uCPE Manager creates a SSH
-          session to the device over the port configured through the <literal>Add Device
-          </literal> process (default 830). It then initiates NETCONF communications over
-          this session.</para>
+          <para>If Call-Home is not enabled/supported, the uCPE Manager
+          creates a SSH session to the device over the port configured through
+          the <literal>Add Device </literal> process (default 830). It then
+          initiates NETCONF communications over this session.</para>
         </listitem>
 
         <listitem>
-          <para>If the device uses Call-Home, it creates a socket connection to port 4334
-          on the management system which runs the uCPE Manager. The uCPE Manager then
-          creates a SSH session over this socket and initiates NETCONF communications as
-          a client.</para>
+          <para>If the device uses Call-Home, it creates a socket connection
+          to port 4334 on the management system which runs the uCPE Manager.
+          The uCPE Manager then creates a SSH session over this socket and
+          initiates NETCONF communications as a client.</para>
         </listitem>
       </orderedlist>
 
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/cloud_init_tab.png b/doc/book-enea-nfv-access-getting-started/doc/images/cloud_init_tab.png
new file mode 100755
index 0000000..df964a8
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/cloud_init_tab.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/content_files_table.png b/doc/book-enea-nfv-access-getting-started/doc/images/content_files_table.png
new file mode 100755
index 0000000..b5f3466
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/content_files_table.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/instantiate_a_vnf.png b/doc/book-enea-nfv-access-getting-started/doc/images/instantiate_a_vnf.png
new file mode 100755
index 0000000..41165e4
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/instantiate_a_vnf.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/instantiate_a_vnf4.png b/doc/book-enea-nfv-access-getting-started/doc/images/instantiate_a_vnf4.png
new file mode 100755
index 0000000..ec82bbc
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/instantiate_a_vnf4.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/interfaces_table.png b/doc/book-enea-nfv-access-getting-started/doc/images/interfaces_table.png
new file mode 100755
index 0000000..51eef4e
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/interfaces_table.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png b/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png
new file mode 100755
index 0000000..8df385e
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_image.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_send.png b/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_send.png
new file mode 100755
index 0000000..b49f293
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/onboard_a_vnf_send.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/onboarding_a_new_vnf.png b/doc/book-enea-nfv-access-getting-started/doc/images/onboarding_a_new_vnf.png
new file mode 100755
index 0000000..0f3033f
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/onboarding_a_new_vnf.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/onboarding_vnf.png b/doc/book-enea-nfv-access-getting-started/doc/images/onboarding_vnf.png
deleted file mode 100755
index 72b59bc..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/images/onboarding_vnf.png
+++ /dev/null
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/properties_tab.png b/doc/book-enea-nfv-access-getting-started/doc/images/properties_tab.png
new file mode 100755
index 0000000..55de421
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/properties_tab.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/vnf_management.png b/doc/book-enea-nfv-access-getting-started/doc/images/vnf_management.png
new file mode 100755
index 0000000..c08ded0
--- /dev/null
+++ b/doc/book-enea-nfv-access-getting-started/doc/images/vnf_management.png
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/vnf_manager.png b/doc/book-enea-nfv-access-getting-started/doc/images/vnf_manager.png
deleted file mode 100755
index 8adb954..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/images/vnf_manager.png
+++ /dev/null
diff --git a/doc/book-enea-nfv-access-getting-started/doc/images/vnf_onboard.png b/doc/book-enea-nfv-access-getting-started/doc/images/vnf_onboard.png
deleted file mode 100755
index 72b59bc..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/images/vnf_onboard.png
+++ /dev/null