1 files changed, 416 insertions, 315 deletions

diff --git a/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml b/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml
index 0e539de..8fe5e89 100644
--- a/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml
+++ b/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml
@@ -4,72 +4,47 @@
 <chapter id="install_instructions">
   <title>Installation Instructions</title>
 
-  <para>ENEA NFV Core 1.0 leverages the work in the OPNFV Project, delivering
+  <para>Enea NFV Core 1.0 leverages the work in the OPNFV Project, delivering
   selected Installer DVD images together with instructions on how to setup the
-  Installers and deploy OPNFV releases on a Pharos compliant test lab. These
-  images can be accessed on the OPNFV Downloads page.</para>
+  Installers and deploy OPNFV releases on a Pharos compliant test lab.</para>
 
-  <para>ENEA NFV Core uses the Fuel@OPNFV Installer as a deployment facility,
+  <para>Enea NFV Core uses the Fuel@OPNFV Installer as a deployment facility,
   hereafter referred to as <emphasis role="bold">Fuel</emphasis>. Fuel is an
   automated deployment tool capable of automatically provisioning and
-  deploying OpenStack on a cluster of servers. ENEA NFV Core 1.0 is based on
-  the OPNFV release <emphasis role="bold">Danube</emphasis>, which is also
-  available for aarch64 servers through the OPNFV Armband project that is
-  driven by ENEA, which also uses the Fuel Installer. The Armband project is
-  out of the scope of this document but there are information available online
-  on the OPNFV wiki. The OPNFV download page provides general instructions for
-  building and installing the Fuel Installer iso and also on how to deploy
-  OPNFV Danube using Fuel on a Pharos compliant test lab . Through the
-  remainder of this document there will be references to this Installation
-  Guide, sometimes referred simply as &rdquor;the guide&rdquo; or &rdquor;the
-  installation guide&rdquo; or the &rdquor;Fuel Installation Guide&rdquo;. The
-  next sections of this chapter will explain in detail the procedure for
-  configuring and installing the Fuel Master followed by configuration and
-  deployment of the ENEA NFV Core 1.0 on the test lab.</para>
+  deploying OpenStack on a cluster of servers.</para>
 
-  <note>
-    <para>Covering chapters 1-6 of the Fuel Installation Guide is not
-    mandatory but useful for better understanding the hardware requirements
-    and how the deployment process works. Also note that since and ISO is
-    provided, it is not necessary to build an ISO image from scratch.</para>
-  </note>
+  <para>Enea NFV Core 1.0 is based on the OPNFV <emphasis role="bold">Danube
+  </emphasis>release, available for aarch64 servers through the OPNFV Armband
+  project that is driven by Enea, which also uses the Fuel Installer. The
+  Armband project is out of the scope of this document but information is
+  available online on the OPNFV wiki.</para>
+
+  <para>The OPNFV download page provides general instructions for building and
+  installing the Fuel Installer .iso and also on how to deploy OPNFV Danube
+  using Fuel on a Pharos compliant test lab.</para>
 
   <note>
-    <para>the following sections will refer to a specific sub-chapter in the
-    installation guide, which is indicated at the end of the title in round
-    parenthesis. Chapter of the installation guide which are not mentioned can
-    be safely skipped.</para>
+    <para>Covering chapters 1-6 of the Fuel Installation Guide is useful for
+    better understanding the hardware requirements and how the deployment
+    process works. Since an ISO image is provided however, it is not necessary
+    to build one from scratch.</para>
   </note>
 
-  <para>Before starting the installation of this release of ENFV Core, certain
-  preparations must be done to ensure optimal performance.</para>
+  <para>Before starting the installation of this release of Enea NFV Core,
+  certain preparations must be done to ensure optimal performance.</para>
 
   <section id="retrieve-ISO-image">
-    <title>Retrieving the ISO image</title>
+    <title>The ISO image</title>
 
-    <para>First, the Fuel deployment ISO image needs to be retrieved. The .iso
-    image download link for this release can be found in <ulink
-    url="https://www.opnfv.org/software/download">OPNFV documentation and
-    software downloads </ulink></para>
-
-    <remark>Update this url link as appropriate</remark>
-
-    <para>This refers to chapter 3.1 in the installation guide. In this case
-    the ENEA provided ISO image is to be used, which should have been made
-    available.</para>
+    <para>ENEA provides the ISO image that is to be used, removing the need
+    for any downloads or building from the ground up.</para>
   </section>
 
   <section id="other-preparations">
     <title>Other Preparations</title>
 
-    <para>Chapter 3.3 of the installation guide provides link to further
-    documentation which is useful but not mandatory.</para>
-
-    <para>Next, familiarize yourself with Fuel by reading the following
-    documents:</para>
-
-    <remark>Should any of these 4 documents be included/referenced as part of
-    our guide or should we include something else ?</remark>
+    <para>Reading the following documents aides in familiarizing yourself with
+    Fuel:</para>
 
     <itemizedlist>
       <listitem>
@@ -98,7 +73,7 @@
     </itemizedlist>
 
     <para>Prior to installation, a number of deployment specific parameters
-    must be collected, such as:</para>
+    must be collected:</para>
 
     <remark>Change the following parameters as appropriate</remark>
 
@@ -138,7 +113,7 @@
         links above.</para>
 
         <para>This information will be needed for the configuration procedures
-        provided in this document.</para>
+        that follow.</para>
       </listitem>
     </itemizedlist>
   </section>
@@ -147,7 +122,7 @@
     <title>Hardware Requirements</title>
 
     <para>The following minimum hardware requirements must be met for the
-    installation of ENFV Core using Fuel, to be successful:</para>
+    installation of Enea NFV Core using Fuel, to be successful:</para>
 
     <informaltable>
       <tgroup cols="2">
@@ -163,84 +138,67 @@
           <row>
             <entry align="left">Nr. of nodes</entry>
 
-            <entry>Minimum 6 (3 for non-redundant deployment):<itemizedlist>
+            <entry>6 physical nodes:<itemizedlist>
                 <listitem>
-                  <para>1 Fuel deployment master (may be virtualized)</para>
+                  <para>1 x Fuel deployment master (which was virtualized),
+                  x86 based</para>
                 </listitem>
 
                 <listitem>
-                  <para>3 Controllers (1 co-located mongo/ceilometer role, 2
-                  Ceph-OSD roles)</para>
+                  <para>3x Cavium ThunderX 1U 48 cores <ulink
+                  url="https://www.avantek.co.uk/arm-server-r120-t30/">R120-T30</ulink>
+                  as Controller nodes (for an HA configuration: 1 collocated
+                  mongo/ceilometer role, 1 Ceph-OSD role, 1 Vitrage Controller
+                  role)</para>
                 </listitem>
 
                 <listitem>
-                  <para>1 Compute (1 co-located Ceph-OSD role)</para>
+                  <para>2x Cavium ThunderX 2U 96 cores <ulink
+                  url="https://www.avantek.co.uk/arm-server-r270-t60/">R270-T60</ulink>
+                  as Compute nodes (with collocated Ceph-OSD roles)</para>
                 </listitem>
               </itemizedlist></entry>
           </row>
 
           <row>
-            <entry>CPU</entry>
-
-            <entry>Minimum 1 socket x86_AMD64 with Virtualization
-            support</entry>
-          </row>
-
-          <row>
             <entry>RAM</entry>
 
-            <entry>Minimum 16GB/server (depending on VNF work load)</entry>
+            <entry>128 GB on the Controller nodes, 256 GB on the Compute
+            nodes</entry>
           </row>
 
           <row>
             <entry>Disk</entry>
 
-            <entry>Minimum 256GB 10kRPM spinning disks</entry>
+            <entry>1 x 120GB SSD and 1 x 2TB SATA 5400 rpm</entry>
           </row>
 
           <row>
             <entry>Networks</entry>
 
-            <entry><itemizedlist>
-                <listitem>
-                  <para>4 Tagged VLANs (PUBLIC, MGMT, STORAGE, PRIVATE)</para>
-                </listitem>
-
-                <listitem>
-                  <para>1 Un-Tagged VLAN for PXE Boot - ADMIN Network</para>
-                </listitem>
-              </itemizedlist><para>Note: These can be allocated to a single
-            NIC - or spread out over multiple NICs as supported by your
-            hardware.</para></entry>
+            <entry><para>Apart from the integrated NICs, one Intel &reg;
+            82574L PCIe card was also installed, to be used by Fuel Admin on
+            each server.</para></entry>
           </row>
         </tbody>
       </tgroup>
     </informaltable>
-
-    <para>6 physical nodes 1 x Fuel deployment master (which was virtualized),
-    x86 based 3 x Cavium ThunderX 1U 48 cores R120-T30
-    (https://www.avantek.co.uk/arm-server-r120-t30/) as Controller nodes (for
-    an HA configuration, 1 collocated mongo/ceilometer role, 1 Ceph-OSD role,
-    1 Vitrage Controller role) 2 x Cavium ThunderX 2U 96 cores R270-T60
-    (https://www.avantek.co.uk/arm-server-r270-t60/) as Compute nodes (with
-    collocated Ceph-OSD roles) RAM &ndash; 128 GB on the Controller nodes, 256
-    GB on the Compute nodes Disk &ndash; 1 x 120GB SSD and 1 x 2TB SATA 5400
-    rpm Networks &ndash; Appart from the integrated NICs also installed was
-    one Intel &reg; 82574L PCIe card used for Fuel Admin on each server</para>
   </section>
 
   <section id="install_fuel_master">
-    <title>Install Fuel Master</title>
+    <title>Installing Fuel Master</title>
+
+    <para>This section describes the installation of the Enea NFV Core
+    installation server (Fuel Master) as well as the deployment of the full
+    ENFV Core reference platform stack across a server cluster.</para>
 
-    <para>This section describes the installation of the ENFV Core
-    installation server (Fuel master) as well as the deployment of the full
-    ENFV Core reference platform stack across a server cluster. It is
-    recommended to install the Fuel Master on a VM using virt-manager with a
-    minimum of 8GB of RAM, 4 CPUs and at least 100GB disk.</para>
+    <para>It is recommended to install the Fuel Master on a VM using
+    virt-manager, with a minimum of 8GB of RAM, 4 CPUs and at least 100GB
+    disk.</para>
 
     <orderedlist>
       <listitem>
-        <para>Mount the ENEA NFV Core 1.0 ISO file/media as a boot device to
+        <para>Mount the Enea NFV Core 1.0 ISO file/media as a boot device to
         the Fuel Master VM.</para>
       </listitem>
 
@@ -253,8 +211,8 @@
           </listitem>
 
           <listitem>
-            <para>Select <literal>Fuel Install (Static IP)</literal> (See
-            figure below)</para>
+            <para>Select <literal>Fuel Install (Static IP)</literal> as shown
+            in the figure below.</para>
           </listitem>
 
           <listitem>
@@ -278,20 +236,19 @@
 
       <listitem>
         <para>In the <literal>Fuel User</literal> section, confirm/change the
-        default password (see figure below).</para>
+        default password</para>
 
         <itemizedlist>
           <listitem>
-            <para>Enter &rdquor;admin&rdquo; in the Fuel password input</para>
+            <para>Enter "admin" in the Fuel password input</para>
           </listitem>
 
           <listitem>
-            <para>Enter &rdquor;admin&rdquo; in the Confirm password
-            input</para>
+            <para>Enter "admin" in the Confirm password input</para>
           </listitem>
 
           <listitem>
-            <para>Select &rdquor;Check&rdquo; and press [Enter]</para>
+            <para>Select "Check" and press [Enter]</para>
           </listitem>
         </itemizedlist>
 
@@ -304,17 +261,16 @@
       </listitem>
 
       <listitem>
-        <para>In the &rdquor;Network Setup&rdquo; section, configure
-        DHCP/Static IP information for your FUEL node.</para>
-
-        <para>E.g.: ETH0 is 10.20.0.2/24 for FUEL booting and ETH1 is DHCP in
-        your corporate/lab network (see figure below) .</para>
+        <para>In the <literal>Network Setup</literal> section, configure
+        DHCP/Static IP information for your FUEL node. E.g.: ETH0 is
+        10.20.0.2/24 for FUEL booting and ETH1 is DHCP in your corporate/lab
+        network, as shown below.</para>
 
         <itemizedlist>
           <listitem>
-            <para>Configure eth1 here, it should be the interface to the
-            outside world. In this example ETH1 is configured with
-            10.0.6.10/24 and the default gateway is 10.0.6.254</para>
+            <para>Configure ETH1, the interface to the outside world. In this
+            example ETH1 is configured with 10.0.6.10/24 and the default
+            gateway is 10.0.6.254.</para>
           </listitem>
         </itemizedlist>
 
@@ -332,31 +288,43 @@
       </listitem>
 
       <listitem>
-        <para>In the PXE setup menu, the default values can be left
-        unchanged.</para>
+        <para>In the <literal>Security Setup</literal> menu, restrict the
+        <literal>ssh</literal> access on the network:</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/extra.svg" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>In the <literal>PXE setup</literal> menu, the default values can
+        be left unchanged.</para>
       </listitem>
 
       <listitem>
         <para>In the <literal>DNS &amp; Hostname</literal> section the
-        recommended values are as presented in the figure below:</para>
+        recommended values are as such:</para>
 
         <mediaobject>
           <imageobject>
-            <imagedata contentwidth="600" fileref="images/DNS_Hostname.svg" />
+            <imagedata contentwidth="600" fileref="images/dns.svg" />
           </imageobject>
         </mediaobject>
       </listitem>
 
       <listitem>
-        <para>The Bootstrap Image section should be skipped, the ISO will be
-        configured in advance to use the proper repositories.</para>
+        <para>The <literal>Bootstrap Image</literal> section should be
+        skipped, the ISO will be configured in advance to use the proper
+        repositories.</para>
       </listitem>
 
       <listitem>
-        <para>In the <literal>Time Sync</literal> section (see figure below) -
-        Change the following fields to appropriate values. It is strongly
-        advised to avoid using <literal>fuel.pool.ntp.org</literal> values and
-        instead set them to <literal>pool.ntp.org:</literal></para>
+        <para>In the <literal>Time Sync</literal> section, change the fields
+        shown below to appropriate values. It is strongly advised to avoid
+        using <literal>fuel.pool.ntp.org</literal> and instead set the values
+        to <literal>pool.ntp.org.</literal></para>
 
         <mediaobject>
           <imageobject>
@@ -366,13 +334,12 @@
       </listitem>
 
       <listitem>
-        <para>Enable experimental and advanced features</para>
+        <para>Enable Experimental features:</para>
 
         <itemizedlist>
           <listitem>
-            <para>In the &rdquor;Features groups&rdquo; section (see figure
-            below) &ndash; enable the checkboxes for Experimental and Advanced
-            features</para>
+            <para>In the <literal>Feature groups</literal> section, enable the
+            checkbox for <literal>Experimental</literal> features.</para>
           </listitem>
 
           <listitem>
@@ -383,17 +350,18 @@
 
         <mediaobject>
           <imageobject>
-            <imagedata contentwidth="600" fileref="images/features_groups.svg" />
+            <imagedata contentwidth="600" fileref="images/experimental.svg" />
           </imageobject>
         </mediaobject>
       </listitem>
 
       <listitem>
-        <para>Start the installation</para>
+        <para>Start the installation:</para>
 
         <itemizedlist>
           <listitem>
-            <para>Select "Quit Setup" and press [Save and Quit].</para>
+            <para>Select <literal>Quit Setup</literal> and press [Save and
+            Quit].</para>
           </listitem>
 
           <listitem>
@@ -408,22 +376,20 @@
   <section id="boot_the_servers">
     <title>Boot the Servers</title>
 
-    <para>Follow the same steps as indicated in the installation guide. Wait
-    until the Fuel Master installation is complete, which should be indicated
-    by the VM restarting and prompting for user login.</para>
-
-    <para>After the Fuel Master node has rebooted from the above steps and is
-    at the login prompt, you should boot the Node Servers (Your
-    Compute/Control/Storage blades, nested or real) with a PXE booting scheme
-    so that the FUEL Master can pick them up for control.</para>
+    <para>Wait until the Fuel Master installation is complete, indicated by
+    the VM restarting and prompting for user login. After the Fuel Master node
+    (setup in the previous section) has rebooted and is at the login prompt,
+    you should boot the Node Servers (the Compute/Control/Storage blades,
+    nested or real) with a PXE booting scheme so that the FUEL Master can pick
+    them up for control.</para>
 
     <orderedlist>
       <listitem>
-        <para>Enable PXE booting</para>
+        <para>Enable PXE booting:</para>
 
-        <para>For every controller and compute server: enable PXE Booting as
-        the first boot device in the UEFI (EDK2) boot order menu, and hard
-        disk as the second boot device in the same menu.</para>
+        <para>For every controller and compute server, enable PXE Booting as
+        the first boot device in the UEFI (EDK2) boot order menu, with the
+        hard disk as the second boot device in the same menu.</para>
       </listitem>
 
       <listitem>
@@ -431,7 +397,7 @@
       </listitem>
 
       <listitem>
-        <para>Wait for the availability of nodes showing up in the Fuel
+        <para>Wait for the availability of nodes to appear in the Fuel
         GUI.</para>
 
         <itemizedlist>
@@ -459,12 +425,12 @@
   <section id="add_feat_fuel">
     <title>Installing additional Plugins/Features on FUEL</title>
 
-    <para>In order to obtain the set of extra features used by ENEA NFV Core
-    1.0 a few extra Fuel plugins have to be installed at this stage. Further
-    configuration steps will also need to be performed after the installation
-    is complete, details about these later on.</para>
+    <para>In order to obtain the extra features used by Enea NFV Core 1.0, a
+    few added Fuel plugins have to be installed at this stage. Supplementary
+    configuration will also need to be performed after the installation is
+    complete.</para>
 
-    <para>The following extra plugins need to be installed:</para>
+    <para>The following plugins will need to be installed:</para>
 
     <itemizedlist>
       <listitem>
@@ -474,18 +440,14 @@
       <listitem>
         <para>Zabbix for Fuel</para>
       </listitem>
-
-      <listitem>
-        <para>Tacker VNF Manager</para>
-      </listitem>
     </itemizedlist>
 
-    <para>Login to the Fuel master via ssh using the default credentials (e.g.
-    root@10.20.0.2 pwd: r00tme) and install the additional plugins:</para>
+    <para>Login to the Fuel Master via <literal>ssh</literal> using the
+    default credentials (e.g. root@10.20.0.2 pwd: r00tme) and install the
+    additional plugins:</para>
 
     <programlisting>$ fuel plugins --install /opt/opnfv/vitrage-1.0-1.0.4-1.noarch.rpm
-$ fuel plugins --install zabbix_monitoring-2.5-2.5.3-1.noarch.rpm
-$ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
+$ fuel plugins --install zabbix_monitoring-2.5-2.5.3-1.noarch.rpm</programlisting>
 
     <para>Expected output: <programlisting>Plugin ....... was successfully installed.</programlisting></para>
   </section>
@@ -498,8 +460,8 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
 
     <orderedlist>
       <listitem>
-        <para>Connect to Fuel WEB UI with a browser (default:
-        https://10.20.0.2:8443) (login: admin/admin)</para>
+        <para>Connect to Fuel WEB UI with a browser (http://10.0.6.10) (login:
+        admin/admin)</para>
       </listitem>
 
       <listitem>
@@ -508,8 +470,8 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       </listitem>
 
       <listitem>
-        <para>Select &rdquor;&lt;Newton on Debian 9&gt; (aarch64)&rdquo; and
-        press &lt;Next&gt;</para>
+        <para>Select &rdquor;aarch64 or x86_64&rdquo; and press
+        &lt;Next&gt;</para>
 
         <mediaobject>
           <imageobject>
@@ -519,20 +481,21 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       </listitem>
 
       <listitem>
-        <para>Select &rdquor;compute virtualization method&rdquo;, then select
-        &rdquor;QEMU-KVM as hypervisor&rdquo; and press [Next].</para>
+        <para>Select <literal>compute virtualization method</literal>, then
+        choose <filename>QEMU-KVM as hypervisor</filename> and press
+        [Next].</para>
       </listitem>
 
       <listitem>
-        <para>Select &rdquor;network mode&rdquo;</para>
+        <para>Select <literal>network mode</literal>:</para>
 
         <itemizedlist>
           <listitem>
-            <para>Select &rdquor;Neutron with ML2 plugin&rdquo;</para>
+            <para>Select <literal>Neutron with ML2 plugin</literal></para>
           </listitem>
 
           <listitem>
-            <para>Select &rdquor;Neutron with VLAN segmentation&rdquo;
+            <para>Select <literal>Neutron with VLAN segmentation</literal>
             (recommended when enabling DPDK).</para>
           </listitem>
 
@@ -549,8 +512,8 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       </listitem>
 
       <listitem>
-        <para>Select &rdquor;Storage Back-ends&rdquo;, then &rdquor;Ceph for
-        block storage&rdquo; and press [Next]</para>
+        <para>Select <literal>Storage Back-ends</literal>, then <filename>Ceph
+        for block storage</filename> and press [Next]</para>
 
         <mediaobject>
           <imageobject>
@@ -560,7 +523,7 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
         </mediaobject>
       </listitem>
 
-      <listitem>
+      <listitem condition="hidden">
         <para>In the Additional Services select &rdquor;Install
         Vitrage&rdquo;:</para>
 
@@ -591,8 +554,8 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       </listitem>
 
       <listitem>
-        <para>Open the networks tab and select the &rdquor;default&rdquo; Node
-        Networks group to on the left pane (see figure below).</para>
+        <para>Open the networks tab and select <literal>default</literal> in
+        the Node Networks group, on the left side menu:</para>
 
         <mediaobject>
           <imageobject>
@@ -631,7 +594,7 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
           </listitem>
 
           <listitem>
-            <para>Set appropriate VLAN ID</para>
+            <para>Set an appropriate VLAN ID, if needed.</para>
           </listitem>
         </itemizedlist>
       </listitem>
@@ -641,7 +604,7 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
 
         <itemizedlist>
           <listitem>
-            <para>It&rsquo;s recommended to keep the default CIDR</para>
+            <para>It is recommended to keep the default CIDR</para>
           </listitem>
 
           <listitem>
@@ -665,7 +628,7 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
 
         <itemizedlist>
           <listitem>
-            <para>It&rsquo;s recommended to keep the default CIDR</para>
+            <para>It is recommended to keep the default CIDR</para>
           </listitem>
 
           <listitem>
@@ -683,7 +646,7 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
           </listitem>
 
           <listitem>
-            <para>Set appropriate VLAN ID (default 101)</para>
+            <para>Set an appropriate VLAN ID (default 101)</para>
           </listitem>
         </itemizedlist>
       </listitem>
@@ -693,7 +656,7 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
 
         <itemizedlist>
           <listitem>
-            <para>It&rsquo;s recommended to keep the default CIDR</para>
+            <para>It is recommended to keep the default CIDR</para>
           </listitem>
 
           <listitem>
@@ -711,14 +674,14 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
           </listitem>
 
           <listitem>
-            <para>Set appropriate VLAN tag (default 103)</para>
+            <para>Set an appropriate VLAN tag (default 103)</para>
           </listitem>
         </itemizedlist>
       </listitem>
 
       <listitem>
-        <para>Select the &rdquor;Neutron L3&rdquo; Node Networks group on the
-        left pane</para>
+        <para>Select the <literal>Neutron L3</literal> Node Networks group on
+        the left pane:</para>
 
         <mediaobject>
           <imageobject>
@@ -728,7 +691,8 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       </listitem>
 
       <listitem>
-        <para>Update the Floating Network configuration:</para>
+        <para>Update the <literal>Floating Network Parameters</literal>
+        configuration:</para>
 
         <itemizedlist>
           <listitem>
@@ -748,8 +712,7 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
 
         <itemizedlist>
           <listitem>
-            <para>It&rsquo;s recommended to keep the default CIDR and
-            mask</para>
+            <para>It is recommended to keep the default CIDR and mask</para>
           </listitem>
 
           <listitem>
@@ -759,16 +722,17 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       </listitem>
 
       <listitem>
-        <para>Update the Guest OS DNS servers with appropriate values.</para>
+        <para>Update the <literal>Guest OS DNS servers</literal> with
+        appropriate values.</para>
       </listitem>
 
       <listitem>
-        <para>Save Settings</para>
+        <para>Save your settings</para>
       </listitem>
 
       <listitem>
-        <para>Select the &rdquor;Other&rdquo; Node Networks group on the left
-        pane (see figure below).</para>
+        <para>Select the <literal>Other</literal> Node Networks group on the
+        left pane:</para>
 
         <mediaobject>
           <imageobject>
@@ -778,16 +742,20 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       </listitem>
 
       <listitem>
-        <para>Make sure the &rdquor;Public Gateway is Available&rdquo; and
-        &rdquor;Assign public networks to all nodes&rdquo; are checked.</para>
+        <para>Make sure the <literal>Public Gateway is Available</literal> and
+        <literal>Assign public networks to all nodes</literal> are checked.
+        <literal>Public Gateway is Available</literal> could be unchecked if
+        not connected to upstream network.</para>
       </listitem>
 
       <listitem>
-        <para>Update Host OS DNS Servers settings</para>
+        <para>Update the <literal>Host OS DNS Servers</literal>
+        settings</para>
       </listitem>
 
       <listitem>
-        <para>Update Host OS NTP Servers settings</para>
+        <para>Update the <literal>Host OS NTP Servers</literal> settings,
+        changing the NTP servers if needed, and save all your changes.</para>
       </listitem>
     </orderedlist>
   </section>
@@ -795,58 +763,50 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
   <section id="hypervisor_type">
     <title>Select Hypervisor type</title>
 
-    <para>Select the Hypervisor type in the following way:</para>
-
-    <orderedlist>
-      <listitem>
-        <para>In the FUEL UI of your Environment, click the
-        &rdquor;Settings&rdquo; Tab</para>
-      </listitem>
-
-      <listitem>
-        <para>Select &rdquor;Compute&rdquo; on the left side pane, check the
-        KVM box and press [Save settings]:</para>
+    <para>Setting the <literal>Hypervisor type</literal> is done in the
+    <literal>Settings</literal> tab by selecting <literal>Compute</literal> on
+    the left side pane, and checking the KVM box:</para>
 
-        <mediaobject>
-          <imageobject>
-            <imagedata contentwidth="600" fileref="images/compute_kvm.svg" />
-          </imageobject>
-        </mediaobject>
-      </listitem>
-    </orderedlist>
+    <mediaobject>
+      <imageobject>
+        <imagedata contentwidth="600" fileref="images/compute_kvm.svg" />
+      </imageobject>
+    </mediaobject>
   </section>
 
   <section id="add_rm_repos">
-    <title>Add/Remove Repositories</title>
-
-    <para>By default OPNFV Fuel uses a set of repositories as package sources.
-    These hold both OpenStack components as well as other needed
-    packages.</para>
-
-    <para>In order to speed up the deployment process, Fuel will create its
-    own local mirror which can be reachable on the Admin interface (e.g.
-    10.20.0.2:8080/newton-10.0/ubuntu/x86-64). However, more repositories are
-    added that need external connection.</para>
+    <title>Adding/Removing Repositories</title>
+
+    <para>Fuel by default, uses a set of repositories as package sources, that
+    hold both OpenStack components as well as other needed packages. In order
+    to speed up the deployment process, Fuel will create two mirrors. The
+    first, a local mirror, reachable on the Admin interface (e.g.
+    <literal>10.20.0.2:8080/newton-10.0/ubuntu/x86-64</literal>), will add
+    additional repositories that need external connections. The second, a
+    debian testing main:
+    <literal>http://10.20.0.2:8080/mirrors/debian</literal>, requires no other
+    repositories to be added that need external connections, having only (even
+    for offline): <filename>debian-testing-local</filename> and
+    <literal>mos</literal>.</para>
 
     <para>It is possible to avoid using external repositories and make the
-    entire process completely offline. This way only the most basic packages
-    will be installed, but the process will be quicker and not depend on an
-    Internet connection. To do this, just make sure that the Repositories list
-    contain only ubuntu-local, mos and Auxilliary.</para>
+    entire process completely offline. In this way only the most basic
+    packages will be installed, but the process will be more efficient and not
+    depend on an Internet connection. To do this, just make sure that the
+    Repositories list contains only <filename>ubuntu-local</filename>,
+    <literal>mos</literal> and <literal>Auxilliary</literal>.</para>
 
     <itemizedlist>
       <listitem>
-        <para>In the FUEL UI of you Environment, click the
-        &rdquor;Settings&rdquo; Tab</para>
+        <para>In the <literal>Settings</literal> tab of the FUEL UI, select
+        <literal>General</literal> and scroll down to the Repositories list
+        (see figure below).</para>
       </listitem>
 
       <listitem>
-        <para>Select &rdquor;General&rdquo; and scroll down to the
-        Repositories list (see figure below).</para>
-
         <para>Remove any extra repositories that point to external
-        repositories by clicking the delete button on the right of the
-        repository entry.</para>
+        repositories, by clicking the delete/minus button on the far right of
+        the repository entry.</para>
 
         <mediaobject>
           <imageobject>
@@ -859,11 +819,11 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
   </section>
 
   <section id="plugins">
-    <title>Enable Plugins</title>
+    <title>Enabling Plugins</title>
 
     <para>In the FUEL UI of your Environment, click the
-    &rdquor;Settings&rdquo; Tab and select OpenStack Services on the left side
-    pane. Enable the Tacker VNF manager plugin:</para>
+    <literal>Settings</literal> tab and select <literal>OpenStack
+    Services</literal> on the left side pane:</para>
 
     <mediaobject>
       <imageobject>
@@ -871,7 +831,8 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       </imageobject>
     </mediaobject>
 
-    <para>Select "Other" on the left pane and do the following:</para>
+    <para>Click on <literal>Other</literal> on the left pane and do the
+    following:</para>
 
     <itemizedlist>
       <listitem>
@@ -883,7 +844,8 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       </listitem>
 
       <listitem>
-        <para>Check &rdquor;Use Zabbix Datasource in Vitrage&rdquo;</para>
+        <para>Check the box for <literal>Use Zabbix Datasource in
+        Vitrage</literal>:</para>
       </listitem>
     </itemizedlist>
 
@@ -901,8 +863,8 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
 
     <orderedlist>
       <listitem>
-        <para>Click on the &rdquor;Nodes&rdquo; Tab in the FUEL WEB UI (see
-        figure below):</para>
+        <para>Click on the <literal>Nodes</literal> Tab in the FUEL WEB
+        UI:</para>
 
         <mediaobject>
           <imageobject>
@@ -912,7 +874,7 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       </listitem>
 
       <listitem>
-        <para>Assign roles (see figure below):</para>
+        <para>Assign roles:</para>
 
         <itemizedlist>
           <listitem>
@@ -988,16 +950,15 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
         </itemizedlist>
 
         <note>
-          <para>Internally, for testing, the Controller nodes had different
-          network configuration compare to the Compute nodes, but that is not
+          <para>Internally, for testing, the Controller nodes have a different
+          network configuration compared to the Compute nodes, but this is not
           mandatory. The 5 nodes in the cluster can have the exact same
-          configuration</para>
+          configuration.</para>
         </note>
       </listitem>
 
       <listitem>
-        <para>Configure interfaces for Controller nodes (see figure
-        below).</para>
+        <para>Configure interfaces for the Controller nodes:</para>
 
         <itemizedlist>
           <listitem>
@@ -1011,8 +972,8 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
           <listitem>
             <para>Assign interfaces (in this case Public, Storage and
             Management were set on the first 10GbE Port and Private on the
-            second 10GbE port, with Admin on a 1Gb port), and click [Apply]
-            <mediaobject>
+            second 10GbE port, with Admin on a 1Gb port), and click
+            [Apply].<mediaobject>
                 <imageobject>
                   <imagedata contentwidth="600"
                              fileref="images/config_nodes.svg" />
@@ -1062,29 +1023,23 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
   <section id="config_hugepages">
     <title>Configure hugepages</title>
 
-    <para>This step is needed for the DPDK based scenarios and it's not
-    covered in the installation guide.</para>
-
-    <remark>does the comment made above still apply and if so, should this
-    section be removed?</remark>
+    <para>This step is needed for the DPDK based scenarios.</para>
 
     <orderedlist>
       <listitem>
-        <para>Click on the gear on the right of a Compute node</para>
+        <para>Click on the gear/settings icon on the right of a Compute node
+        and do the following:</para>
 
         <itemizedlist>
           <listitem>
-            <para>In the menu that shows up click on Node Attributes</para>
+            <para>In the menu that pops up, expand the <literal>Node
+            Attributes</literal> menu.</para>
           </listitem>
 
           <listitem>
-            <para>Set Huge Pages for Nova and DPDK to appropriate values (see
-            figure below); it&rsquo;s recommended to use at least 2048 pages
-            of 2MB for each of Nova and DPDK</para>
-          </listitem>
-
-          <listitem>
-            <para>Click &lt;Save Settings&gt;</para>
+            <para>Set <literal>Huge Pages</literal> for Nova and DPDK to
+            appropriate values and save your settings. It is recommended to
+            use at least 2048 pages of 2MB for both Nova and DPDK.</para>
 
             <mediaobject>
               <imageobject>
@@ -1097,7 +1052,7 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
 
       <listitem>
         <para>Perform the same configuration for the other Compute
-        nodes</para>
+        nodes.</para>
       </listitem>
     </orderedlist>
   </section>
@@ -1105,55 +1060,52 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
   <section id="target_config">
     <title>Target Specific Configuration</title>
 
-    <para>Follow the guide for setting custom target configuration, as needed.
-    Skip this step if no specific configurations are required.</para>
+    <para>Follow the steps below for setting custom target configuration, as
+    needed. Skip this step if no specific configurations are required.</para>
 
     <orderedlist>
       <listitem>
-        <para>Set up targets for provisioning with non-default
-        &rdquor;Offloading Modes&rdquo;.</para>
+        <para>Set up targets for provisioning with non-default "Offloading
+        Modes".</para>
 
         <para>Some target nodes may require additional configuration after
         they are PXE booted (bootstrapped). The most frequent changes occur in
-        the defaults of ethernet device &rdquor;Offloading Modes&rdquo;
-        settings (e.g. certain target ethernet drivers may strip VLAN traffic
-        by default).</para>
-
-        <para>If your target ethernet drivers have incorrect
-        &rdquor;Offloading Modes&rdquo; defaults, in the &rdquor;Configure
-        interfaces&rdquo; page (described above), expand the affected
-        interface&rsquo;s &rdquor;Offloading Modes&rdquo; and (un)check the
-        settings you need (see figure below): <remark>Insert the appropriate
+        the defaults of ethernet device "Offloading Modes" settings (e.g.
+        certain target ethernet drivers may strip VLAN traffic by
+        default).</para>
+
+        <para>If your target ethernet drivers have incorrect "Offloading
+        Modes" defaults, in the "Configure interfaces" page (described above),
+        expand the affected interface's "Offloading Modes" and (un)check the
+        settings you need. <remark>Insert the appropriate
         figure/screenshot</remark></para>
       </listitem>
 
       <listitem>
-        <para>Set up targets for &rdquor;Verify Networks&rdquo; with
-        non-default &rdquor;Offloading Modes&rdquo;.</para>
+        <para>Set up targets for "Verify Networks" with non-default
+        "Offloading Modes".</para>
+
+        <para>Please check the Release Notes for the 1.0 release of ENFV Core
+        when using Fuel as a deployment tool, <remark>Change this to an Olink
+        to the Release notes once the ID has been created for that book. Add
+        the ID to pardoc-names.xml and pardoc-common if needed, then updated
+        the OlinkDB</remark>for an updated and comprehensive list of known
+        issues and limitations, including the "Offloading Modes" not being
+        applied during the "Verify Networks" step.</para>
 
-        <para>Please check the <ulink
-        url="http://artifacts.opnfv.org/fuel/colorado/3.0/docs/releasenotes/index.html">Release
-        Notes for the 1.0 release of ENFV Core when using Fuel as a deployment
-        tool</ulink>, <remark>Change this to an Olink to the Release notes
-        once the ID has been created for that book. Add the ID to
-        pardoc-names.xml and pardoc-common if needed, then updated the
-        OlinkDB</remark>for an updated and comprehensive list of known issues
-        and limitations, including the &rdquor;Offloading Modes&rdquo; not
-        being applied during the &rdquor;Verify Networks&rdquo; step.</para>
+        <para>Setting custom "Offloading Modes" in the Fuel GUI will only
+        apply during provisioning, not during "Verify Networks". If your
+        targets need this change, you have to apply the "Offloading Modes"
+        settings manually to bootstrapped nodes.</para>
 
-        <para>Setting custom &rdquor;Offloading Modes&rdquo; in Fuel GUI will
-        only apply during provisioning and not during &rdquor;Verify
-        Networks&rdquo;. If your targets need this change, you have to apply
-        &rdquor;Offloading Modes&rdquo; settings manually to bootstrapped
-        nodes. E.g.: Our driver has the &rdquor;rx-vlan-filter&rdquo; default
-        &rdquor;on&rdquo; (expected &rdquor;off&rdquo;) on the OpenStack
-        interface &rdquor;eth1&rdquo;, preventing VLAN traffic from passing
-        during &rdquor;Verify Networks&rdquo;.</para>
+        <para>E.g.: Our driver has the "rx-vlan-filter" default "on" (expected
+        "off") on the OpenStack interface "ETH1", preventing VLAN traffic from
+        passing during "Verify Networks".</para>
 
         <itemizedlist>
           <listitem>
-            <para>From Fuel master console identify target nodes' admin IPs
-            (see figure below):</para>
+            <para>From the Fuel Master console, identify target nodes' admin
+            IPs</para>
 
             <programlisting>$ fuel nodes</programlisting>
 
@@ -1161,16 +1113,16 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
           </listitem>
 
           <listitem>
-            <para>SSH into each of the target nodes and disable the
-            &rdquor;rx-vlan-filter&rdquo; on the affected physical
-            interface(s) allocated for OpenStack traffic (eth1):</para>
+            <para><literal>ssh</literal> into each target node and disable the
+            "rx-vlan-filter" on the affected physical interface(s) allocated
+            for OpenStack traffic (ETH1):</para>
 
             <programlisting>$ ssh root@10.20.0.6 ethtool -K eth1 rx-vlan-filter off</programlisting>
           </listitem>
 
           <listitem>
             <para>Repeat the step above for all affected nodes/interfaces in
-            the POD</para>
+            the POD.</para>
           </listitem>
         </itemizedlist>
       </listitem>
@@ -1188,18 +1140,18 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
 
     <orderedlist>
       <listitem>
-        <para>From the FUEL UI in your environment, select the Networks Tab,
-        then select &rdquor;Connectivity check&rdquo; on the left pane.</para>
+        <para>From the FUEL UI, select the <literal>Networks</literal> tab,
+        then select "Connectivity check" on the left pane.</para>
       </listitem>
 
       <listitem>
-        <para>Select [Verify Networks]</para>
+        <para>Select <literal>Verify Networks</literal></para>
       </listitem>
 
       <listitem>
-        <para>Continue to fix your topology (physical switch, etc) until the
-        &rdquor;Verification Succeeded&rdquo; and &rdquor;Your network is
-        configured correctly&rdquo; messages are shown.</para>
+        <para>Continue to fix your topology (physical switch, etc.) until the
+        "Verification Succeeded" and "Your network is configured correctly"
+        messages are shown.</para>
       </listitem>
     </orderedlist>
   </section>
@@ -1207,12 +1159,14 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
   <section id="deploy_env">
     <title>Deploy your Environment</title>
 
-    <para>As instructed in the installation guide, after the configuration is
-    complete and the network connectivity checked, it&rsquo;s time to deploy.
-    From the Dashboard tab click on Deploy. The process should take around 2
-    hours the first time after a fresh Fuel Master installation. Part of the
-    deploy process is to build the target image, which can take around between
-    30 and 60 minutes.</para>
+    <para>After the configuration is complete and the network connectivity
+    checked, the environment needs to be deployed.</para>
+
+    <para>From the <literal>Dashboard</literal> tab click on
+    <literal>Deploy</literal>. The process should take around 2 hours the
+    first time after a fresh Fuel Master installation. Part of the deploy
+    process is to build the target image, which can take between 30 and 60
+    minutes.</para>
 
     <para>The entire deploy process goes through two phases:</para>
 
@@ -1220,14 +1174,14 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
       <listitem>
         <para>Provisioning &ndash; at this stage the nodes have been booted
         from PXE and are running a small bootstrap image in ramdisk. The
-        provisioning process will write the target image on the disk and make
-        other preparations for running it after reboot</para>
+        provisioning process will write the target image onto the disk and
+        make other preparations for running it after reboot.</para>
       </listitem>
 
       <listitem>
         <para>OpenStack installation &ndash; at this stage the nodes have been
         rebooted on the newly written target image and the OpenStack
-        components are installed and configured</para>
+        components are installed and configured.</para>
       </listitem>
     </itemizedlist>
   </section>
@@ -1236,24 +1190,171 @@ $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting>
     <title>Installation Health-Check</title>
 
     <para>Once the deploy process is complete, it is recommended to run a
-    health check from the Fuel menu, as described in the installation guide.
-    To ensure apt performance, the system health-check must be performed. This
-    is done in the following way:</para>
+    health check from the Fuel menu, done in the following way:</para>
 
     <orderedlist>
       <listitem>
-        <para>Click the &rdquor;Health Check&rdquo; tab inside your
-        Environment in the FUEL Web UI</para>
+        <para>Click the <literal>Health Check</literal> tab inside the FUEL
+        Web UI</para>
       </listitem>
 
       <listitem>
-        <para>Check the [Select All] option, then click [Run Tests]</para>
+        <para>Check the [Select All] option, then [Run Tests]</para>
       </listitem>
 
       <listitem>
         <para>Allow tests to run and investigate results where
-        appropriate</para>
+        appropriate.</para>
       </listitem>
     </orderedlist>
   </section>
+
+  <section id="smoke_test">
+    <title>Smoke Test</title>
+
+    <para>Once deployment is completeed successfully, a smoke test can and
+    should be done.</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Click on the <literal>Horizon</literal> link in the Fuel
+        Dashboard</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/00-Horizon.svg"
+                       format="SVG" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>Login with credentials (admin/admin is the default):</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600"
+                       fileref="images/01-Horizon-Login.svg" format="SVG" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>Select Project|Compute|Instances and all the instances (none in
+        this case) will be displayed. Click <literal>Launch Instance</literal>
+        to create a new instance, causing a causing wizard to appear.</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/02-create.svg"
+                       format="SVG" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>Give a name to the first instance and press Next.</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/03-name.svg" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>The image needed is "Select Boot Source". Add the TestVM image
+        by pressing on the add/plus sign, then press Next.</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/04-image.svg" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>Add the <filename>m1.micro</filename> flavor by pressing on the
+        plus sign, then press Next.</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/05-flavor.svg" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>Add <literal>admin_internal_net</literal> network by pressing on
+        the plus sign and leave the defaults as they are.</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/06-network.svg" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>The <literal>Launch Instance</literal> button is now active and
+        able to be selected.</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/07-launch.svg" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>After a short while, the first virtual machine is created and
+        running.</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/08-created.svg" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>Repeat the above steps to create the second virtual machine.
+        Make a note of the IP addresses allocated:</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/09-created2.svg" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>Click on the <literal>first</literal> Instance Name link, the
+        <literal>Overview</literal> tab will appear. Select the
+        <literal>Console</literal> tab.</para>
+
+        <para>As indicated, if the console is not responding to keyboard
+        input, click the grey status bar. Enter, as shown, user
+        <command>cirros</command> and password
+        <command>cubswin:)</command>.</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/10-VM-login.svg" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+
+      <listitem>
+        <para>It is not possible to verify the IP address received by the
+        machine and ping the other. The ping however, should succeed.</para>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata contentwidth="600" fileref="images/11-VM-ping.svg" />
+          </imageobject>
+        </mediaobject>
+      </listitem>
+    </itemizedlist>
+  </section>
 </chapter>
\ No newline at end of file