path: root/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml

<?xml version="1.0" encoding="ISO-8859-1"?>
<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
<chapter id="install_instructions">
  <title>Installation Instructions</title>

  <para>Enea NFV Core <xi:include
  href="../../s_docsrc_common/pardoc-distro.xml"
  xmlns:xi="http://www.w3.org/2001/XInclude"
  xpointer="element(EneaNFV_REL_VER/1)" /> 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.</para>

  <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.</para>

  <para>Enea NFV Core <xi:include
  href="../../s_docsrc_common/pardoc-distro.xml"
  xmlns:xi="http://www.w3.org/2001/XInclude"
  xpointer="element(EneaNFV_REL_VER/1)" /> is based on the OPNFV <emphasis
  role="bold">Danube </emphasis>release. The <ulink
  url="https://www.opnfv.org/software/downloads">OPNFV download page</ulink>
  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>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 Enea NFV Core,
  certain preparations must be done to ensure optimal performance.</para>

  <section id="retrieve-ISO-image">
    <title>The ISO image</title>

    <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>Reading the following documents aides in familiarizing yourself with
    Fuel:</para>

    <itemizedlist>
      <listitem>
        <para><ulink
        url="https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-install-guide.html">Fuel
        Installation Guide</ulink></para>
      </listitem>

      <listitem>
        <para><ulink
        url="https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-user-guide.html">Fuel
        User Guide</ulink></para>
      </listitem>

      <listitem>
        <para><ulink
        url="https://docs.openstack.org/fuel-docs/latest/devdocs/develop.html">Fuel
        Developer Guide</ulink> (optional)</para>
      </listitem>

      <listitem>
        <para><ulink
        url="http://docs.openstack.org/developer/fueldocs/plugindocs/fuel-plugin-sdk-guide.html">Fuel
        Plugin Developers Guide</ulink> (optional)</para>
      </listitem>

      <listitem>
        <para><ulink
        url="http://docs.opnfv.org/en/stable-danube/submodules/armband/docs/release/installation/index.html">OPNFV
        Fuel Installation Guide for aarch64</ulink></para>
      </listitem>

      <listitem>
        <para><ulink
        url="http://docs.opnfv.org/en/stable-danube/submodules/fuel/docs/release/installation/index.html#fuel-installation">OPNFV
        Fuel Installation Guide for x86</ulink></para>
      </listitem>
    </itemizedlist>

    <para>Prior to installation, a number of deployment specific parameters
    must be collected:</para>

    <remark>Change the following parameters as appropriate</remark>

    <itemizedlist>
      <listitem>
        <para>Provider sub-net and gateway information</para>
      </listitem>

      <listitem>
        <para>Provider VLAN information</para>
      </listitem>

      <listitem>
        <para>Provider DNS addresses</para>
      </listitem>

      <listitem>
        <para>Provider NTP addresses</para>
      </listitem>

      <listitem>
        <para>Network overlay planned for deployment (VLAN, VXLAN, FLAT). Only
        VLAN is supported in this release.</para>
      </listitem>

      <listitem>
        <para>How many nodes and what roles you want to deploy (Controllers,
        Storage, Computes)</para>
      </listitem>

      <listitem>
        <para>Monitoring options you want to deploy (Ceilometer, Syslog,
        etc.).</para>
      </listitem>

      <listitem>
        <para>Other options not covered in the document are available in the
        links above.</para>

        <para>This information will be needed for the configuration procedures
        that follow.</para>
      </listitem>
    </itemizedlist>
  </section>

  <section id="hw_req">
    <title>Hardware Requirements</title>

    <para>Enea NFV Core <xi:include
    href="../../s_docsrc_common/pardoc-distro.xml"
    xmlns:xi="http://www.w3.org/2001/XInclude"
    xpointer="element(EneaNFV_REL_VER/1)" /> has been validated with the
    requirements shown below, which represent the recommended configuration
    that must be met for the installation of Enea NFV Core <xi:include
    href="../../s_docsrc_common/pardoc-distro.xml"
    xmlns:xi="http://www.w3.org/2001/XInclude"
    xpointer="element(EneaNFV_REL_VER/1)" /> using Fuel, to be
    successful.</para>

    <note>
      <para>Enea NFV Core 1.1 can also be installed on a cluster consisting of
      servers with mixed CPU architectures. The user can deploy x86
      Controllers and a combination of x86 and aarch64 Compute nodes.</para>
    </note>

    <para><emphasis role="bold">Hardware Requirements for
    Aarch64:</emphasis></para>

    <informaltable>
      <tgroup cols="2">
        <tbody>
          <row>
            <entry align="left">Nr. of nodes</entry>

            <entry>6 physical nodes:<itemizedlist>
                <listitem>
                  <para>1 x Fuel deployment master (which was virtualized),
                  x86 based</para>
                </listitem>

                <listitem>
                  <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>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>RAM</entry>

            <entry>128 GB on the Controller nodes, 256 GB on the Compute
            nodes</entry>
          </row>

          <row>
            <entry>Disk</entry>

            <entry>1 x 120GB SSD and 1 x 2TB SATA 5400 rpm</entry>
          </row>

          <row>
            <entry>Networks</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><emphasis role="bold">Hardware Requirements for
    x86</emphasis>:</para>

    <informaltable>
      <tgroup cols="2">
        <tbody>
          <row>
            <entry align="left">Nr. of nodes</entry>

            <entry>Controllers (3x):<itemizedlist>
                <listitem>
                  <para>Chassis: SuperChassis <ulink
                  url="http://www.supermicro.com/products/chassis/1U/813/SC813MTQ-350CB">SC813MTQ-350CB</ulink></para>
                </listitem>

                <listitem>
                  <para>Motherboard: <ulink
                  url="http://www.supermicro.com/products/motherboard/Xeon/D/X10SDV-7TP4F.cfm">X10SDV-7TP4F</ulink></para>
                </listitem>
              </itemizedlist></entry>
          </row>

          <row>
            <entry>CPU</entry>

            <entry>Intel&reg; Xeon&reg; D-1537 8-core/HT 1.7 GHz 35W</entry>
          </row>

          <row>
            <entry>RAM</entry>

            <entry>128 GB</entry>
          </row>

          <row>
            <entry>Disk</entry>

            <entry>1 x 120GB SSD and 1 x 2TB SATA 5400 rpm</entry>
          </row>

          <row>
            <entry>Networks</entry>

            <entry><para>NICs: </para><itemizedlist>
                <listitem>
                  <para>Intel&reg; i350-AM2 Dual port GbE LAN</para>
                </listitem>

                <listitem>
                  <para>Intel X552-AT2 dual port</para>
                </listitem>
              </itemizedlist></entry>
          </row>
        </tbody>
      </tgroup>
    </informaltable>

    <informaltable>
      <tgroup cols="2">
        <tbody>
          <row>
            <entry align="left">Nr. of nodes</entry>

            <entry>Compute (2x):<itemizedlist>
                <listitem>
                  <para>Chassis: SuperChassis <ulink
                  url="http://www.supermicro.com/products/chassis/2U/825/SC825TQ-R740WB">SC825TQ-R740WB</ulink></para>
                </listitem>

                <listitem>
                  <para>Motherboard: <ulink
                  url="https://www.supermicro.com/products/motherboard/Xeon/C600/X10DRW-E.cfm">X10DRW-E</ulink></para>
                </listitem>
              </itemizedlist></entry>
          </row>

          <row>
            <entry>CPU</entry>

            <entry>2 x Intel&reg; Xeon&reg; E5-2620 v4 8 -core/HT 2.0 GHz
            85W</entry>
          </row>

          <row>
            <entry>RAM</entry>

            <entry>128 GB</entry>
          </row>

          <row>
            <entry>Networks</entry>

            <entry><para>NICs: </para><itemizedlist>
                <listitem>
                  <para>Intel&reg; i350-AM2 Dual port GbE LAN</para>
                </listitem>

                <listitem>
                  <para>Intel 82599ES 10Gb SFI/SFP+</para>
                </listitem>
              </itemizedlist></entry>
          </row>
        </tbody>
      </tgroup>
    </informaltable>
  </section>

  <section id="install_fuel_master">
    <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
    Enea NFV Core reference platform stack across a server cluster.</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 <xi:include
        href="../../s_docsrc_common/pardoc-distro.xml"
        xmlns:xi="http://www.w3.org/2001/XInclude"
        xpointer="element(EneaNFV_REL_VER/1)" /> ISO file/media as a boot
        device to the Fuel Master VM.</para>
      </listitem>

      <listitem>
        <para>Reboot the VM and make sure it boots from the ISO:</para>

        <itemizedlist>
          <listitem>
            <para>The system now boots from the ISO image</para>
          </listitem>

          <listitem>
            <para>Select <literal>Fuel Install (Static IP)</literal> as shown
            in the figure below.</para>
          </listitem>

          <listitem>
            <para>Press [Enter]</para>

            <mediaobject>
              <imageobject role="fo">
                <imagedata align="center" contentwidth="600"
                           fileref="images/fuel_install_static_ip.svg" />
              </imageobject>

              <imageobject role="html">
                <imagedata align="center"
                           fileref="images/fuel_install_static_ip.png" />
              </imageobject>
            </mediaobject>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Wait until the Fuel setup screen is shown, this can take up to
        30 minutes.</para>
      </listitem>

      <listitem>
        <para>In the <literal>Fuel User</literal> section, confirm/change the
        default password:</para>

        <itemizedlist>
          <listitem>
            <para>Enter "admin" in the Fuel password input</para>
          </listitem>

          <listitem>
            <para>Enter "admin" in the Confirm password input</para>
          </listitem>

          <listitem>
            <para>Select "Check" and press [Enter]</para>
          </listitem>
        </itemizedlist>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/fuel_user.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/fuel_user.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>In the <literal>Network Setup</literal> section, configure the
        network interfaces of the Fuel Master node:</para>

        <itemizedlist>
          <listitem>
            <para>eth0 is the interface used by nodes to boot via PXE (Admin
            network) and eth1 is the interface on the corporate/lab network
            (Public network).</para>
          </listitem>

          <listitem>
            <para>eth0 should be enabled and assigned static IP address
            10.20.0.2/24, with no gateway.</para>
          </listitem>

          <listitem>
            <para>eth1 should be enabled and configured with a static IP
            address, netmask and gateway on your Public network.</para>
          </listitem>
        </itemizedlist>

        <para>You will access Fuel from your Public network using the IP
        configured for eth1.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/net_setup_1.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/net_setup_1.png" />
          </imageobject>
        </mediaobject>

        <para></para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/net_setup_2.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/net_setup_2.png" />
          </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 such:</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="610"
                       fileref="images/dns.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/dns.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>The <literal>Bootstrap Image</literal> section should be
        skipped, the ISO will be configured in advance to use the proper
        repositories.</para>

        <para>During the Fuel installation process bootstrap images for x86_64
        and aarch64 architectures will be created so that the user can
        directly install single or mixed arch clusters.</para>
      </listitem>

      <listitem>
        <para>In the <literal>Time Sync</literal> section, change the fields
        shown below to appropriate values if needed,
        <literal>pool.ntp.org</literal> is set by default.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/time_sync.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/time_sync.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>In the <literal>Feature groups</literal> section, enable the
        checkbox for <literal>Experimental</literal> features. Move to the
        <literal>&lt;Apply&gt;</literal> button and press
        <literal>&lt;Enter&gt;</literal></para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="620"
                       fileref="images/experimental.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/experimental.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Start the installation:</para>

        <itemizedlist>
          <listitem>
            <para>Select <literal>Quit Setup</literal> and press [Save and
            Quit].</para>
          </listitem>

          <listitem>
            <para>The installation will now start. Wait until the login screen
            is shown.</para>
          </listitem>
        </itemizedlist>
      </listitem>
    </orderedlist>
  </section>

  <section id="boot_the_servers">
    <title>Boot the Servers</title>

    <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>For every controller and compute server, enable PXE Booting as
        the first boot device in the BIOS boot menu (for x86) or UEFI boot
        order menu (for aarch64).</para>
      </listitem>

      <listitem>
        <para>Reboot all the control and compute blades.</para>
      </listitem>

      <listitem>
        <para>Connect to the FUEL UI via the URL provided in the Console
        (default: http://10.0.6.10)</para>
      </listitem>

      <listitem>
        <para>Wait for the availability of nodes to appear in the Fuel
        GUI.</para>
      </listitem>

      <listitem>
        <para>Wait until all nodes are displayed in top right corner of the
        Fuel GUI: Total nodes and Unallocated nodes (see figure below).</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" fileref="images/nodes.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/nodes.png" />
          </imageobject>
        </mediaobject>
      </listitem>
    </orderedlist>
  </section>

  <section id="add_feat_fuel">
    <title>Installing additional Plugins/Features on FUEL</title>

    <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 plugins will need to be installed:</para>

    <itemizedlist>
      <listitem>
        <para>Fuel Vitrage Plugin</para>
      </listitem>

      <listitem>
        <para>Zabbix for Fuel</para>
      </listitem>

      <listitem>
        <para>Tacker VNF Manager</para>
      </listitem>

      <listitem>
        <para>KVM For NFV Plugin</para>

        <note>
          <para>Currently the KVM For NFV Plugin is only available for x86
          architectures. Refer to the OPNFV KVMforNFV Project for more
          information.</para>
        </note>
      </listitem>
    </itemizedlist>

    <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 in <literal>/opt/opnfv</literal>:</para>

    <programlisting>$ fuel plugins --install /opt/opnfv/vitrage-1.0-1.0.4-1.noarch.rpm
$ fuel plugins --install /opt/opnfv/zabbix_monitoring-2.5-2.5.3-1.noarch.rpm
$ fuel plugins --install /opt/opnfv/tacker-1.0-1.0.0-1.noarch.rpm
$ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm</programlisting>

    <para>Expected output: <programlisting>Plugin ....... was successfully installed.</programlisting></para>
  </section>

  <section id="create_opstack_env">
    <title>Create an OpenStack Environment</title>

    <para>Follow the procedure below to create an OpenStack
    environment:</para>

    <orderedlist>
      <listitem>
        <para>Connect to Fuel WEB UI with a browser (http://10.0.6.10) (login:
        admin/admin)</para>
      </listitem>

      <listitem>
        <para>Create and name a new OpenStack environment that you want to
        install.</para>
      </listitem>

      <listitem>
        <para>Only Debian 9 is supported in this release. Select
        <filename>Newton on Debian 9 (x86_64)</filename> or <filename>Newton
        on Debian 9 (aarch64)</filename>if you are deploying on a cluster with
        servers of the same CPU architectures or <filename>Newton on Debian 9
        (amd64,arm64) </filename>if you are using Compute nodes of mixed
        architectures:</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/openstack_envs_mixed.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center"
                       fileref="images/openstack_envs_mixed.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Select <literal>compute virtualization method</literal>, then
        choose <filename>QEMU-KVM as hypervisor</filename> and press
        [Next].</para>
      </listitem>

      <listitem>
        <para>Select <filename>Neutron with VLAN segmenation</filename>.
        <filename>Neutron with tunneling segmentation</filename> is available
        but not supported in this release. DPDK scenarios only work with VLAN
        segmentation.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/openstack_env.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/openstack_env.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Select <literal>Storage Back-ends</literal>, then <filename>Ceph
        for block storage</filename>.</para>

        <para><literal>Ceph</literal> for <filename>Image Storage</filename>,
        <literal>Object storage</literal> and <literal>Ephemeral
        storage</literal> have not been validated for this release. It is
        advisable to only use the option mentioned above.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/storage_backends.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/storage_backends.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem condition="hidden">
        <para>In the Additional Services select &rdquor;Install
        Vitrage&rdquo;:</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/additional_services.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/additional_services.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Create the new environment by clicking the [Create]
        Button.</para>
      </listitem>
    </orderedlist>
  </section>

  <section id="config_net_env">
    <title>Configure the Network Environment</title>

    <para>To configure the network environment, please follow these
    steps:</para>

    <orderedlist>
      <listitem>
        <para>Open the environment you previously created.</para>
      </listitem>

      <listitem>
        <para>Open the <literal>Networks</literal> tab and select
        <literal>default</literal> in the <literal>Node Networks</literal>
        group, on the left side menu:</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/networks_tab.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/networks_tab.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Update the Public network configuration and change the following
        fields to appropriate values:</para>

        <itemizedlist>
          <listitem>
            <para>CIDR to &lt;CIDR for Public IP Addresses&gt;</para>
          </listitem>

          <listitem>
            <para>IP Range Start to &lt;Public IP Address start&gt;
            (recommended to start with x.x.x.41)</para>
          </listitem>

          <listitem>
            <para>IP Range End to &lt;Public IP Address end&gt; (recommended
            to end with x.x.x.100)</para>
          </listitem>

          <listitem>
            <para>Gateway to &lt;Gateway for Public IP Addresses&gt;</para>
          </listitem>

          <listitem>
            <para>Check &lt;Use VLAN tagging&gt; if needed. For simplicity it
            is recommended to use the public network in untagged mode.</para>
          </listitem>

          <listitem>
            <para>Set an appropriate VLAN ID, if needed.</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Update the Storage Network Configuration:</para>

        <itemizedlist>
          <listitem>
            <para>It is recommended to keep the default CIDR</para>
          </listitem>

          <listitem>
            <para>Set IP Range Start to an appropriate value (default
            192.168.1.1)</para>
          </listitem>

          <listitem>
            <para>Set IP Range End to an appropriate value (default
            192.168.1.254)</para>
          </listitem>

          <listitem>
            <para>Set VLAN tagging as needed</para>
          </listitem>

          <listitem>
            <para>Set an appropriate VLAN ID (default 102)</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Update the Management Network configuration:</para>

        <itemizedlist>
          <listitem>
            <para>It is recommended to keep the default CIDR</para>
          </listitem>

          <listitem>
            <para>Set IP Range Start to an appropriate value (default
            192.168.0.1)</para>
          </listitem>

          <listitem>
            <para>Set IP Range End to an appropriate value (default
            192.168.0.254)</para>
          </listitem>

          <listitem>
            <para>Set VLAN tagging as needed</para>
          </listitem>

          <listitem>
            <para>Set an appropriate VLAN ID (default 101)</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Select the <literal>Neutron L3</literal> Node Networks group on
        the left pane:</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/neutron_L3.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/neutron_L3.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Update the <literal>Floating Network Parameters</literal>
        configuration:</para>

        <itemizedlist>
          <listitem>
            <para>Set the Floating IP range start (recommended to start with
            x.x.x.101)</para>
          </listitem>

          <listitem>
            <para>Set the Floating IP range end (recommended to end with
            x.x.x.200)</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Update the Internal Network configuration:</para>

        <itemizedlist>
          <listitem>
            <para>It is recommended to keep the default CIDR and mask</para>
          </listitem>

          <listitem>
            <para>Set Internal network gateway to an appropriate value</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Update the <literal>Guest OS DNS servers</literal> with
        appropriate values.</para>
      </listitem>

      <listitem>
        <para>Save your settings</para>
      </listitem>

      <listitem>
        <para>Select the <literal>Other</literal> Node Networks group on the
        left pane:</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/other_networks.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/other_networks.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <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 the <literal>Host OS DNS Servers</literal>
        settings</para>
      </listitem>

      <listitem>
        <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>

  <section id="lag_lacp">
    <title>Configure Network Bonding with LAG/LACP</title>

    <para>Network bonding, network aggregation, or NIC bonding, is a network
    technology that enables a user to maximize throughput by aggregating
    multiple physical links into a single high-speed aggregated network
    interface. In addition to increasing bandwidth, network bonding provides
    fault tolerance.</para>

    <para>The user must configure NIC bonding before or in the scope of
    mapping logical networks to physical network interfaces.</para>

    <para><emphasis role="bold">To configure network
    interfaces</emphasis></para>

    <para><orderedlist>
        <listitem>
          <para>In the Fuel web UI, click the <literal>Nodes</literal>
          tab.</para>
        </listitem>

        <listitem>
          <para>Select the nodes you want to configure the interfaces
          on.</para>
        </listitem>

        <listitem>
          <para>Click <literal>Configure Interfaces</literal>.</para>
        </listitem>

        <listitem>
          <para>Select the network interfaces that you want to
          aggregate.</para>
        </listitem>

        <listitem>
          <para>Click <literal>Bond Interfaces</literal>.</para>
        </listitem>

        <listitem>
          <para>In the <literal>Mode</literal> drop-down list, select
          <literal>802.3ad(LACP)</literal> bonding mode: <mediaobject>
              <imageobject role="fo">
                <imagedata align="center" contentwidth="600"
                           fileref="images/bonding_mode_LACP.svg" />
              </imageobject>

              <imageobject role="html">
                <imagedata align="center"
                           fileref="images/bonding_mode_LACP.png" />
              </imageobject>
            </mediaobject></para>
        </listitem>

        <listitem>
          <para>Configure the LACP rate and the Xmit Hash Policy
          <remark>Should there be an picture here to illustrate this
          step?</remark></para>
        </listitem>

        <listitem>
          <para>Optionally, create and configure additional network
          interfaces, if needed.</para>
        </listitem>

        <listitem>
          <para>Click <literal>Apply</literal>.</para>
        </listitem>

        <listitem>
          <para>Configure LAG/LACP bonding on the corresponding physical
          switch ports you use in your infrastructure.</para>

          <para>For example, on a Extreme Network Summit X670 switch:</para>

          <programlisting>enable sharing 14 grouping 14,16 algorithm address-based L2 lacp</programlisting>

          <para>The aggregated link will look as such:</para>

          <programlisting>* X670-48x #2.9 # show lacp lag 14
 Lag   Actor    Actor  Partner           Partner  Partner Agg   Actor
       Sys-Pri  Key    MAC               Sys-Pri  Key     Count MAC
--------------------------------------------------------------------------------
14          0  0x03f6 00:00:00:00:00:00       0  0x0000      0 00:04:96:9a:31:54
Port list:
Member     Port      Rx           Sel          Mux            Actor     Partner
Port       Priority  State        Logic        State          Flags     Port
--------------------------------------------------------------------------------
14         0         Defaulted    Unselected   Detached       A-G---F-  0
16         0         Defaulted    Unselected   Detached       A-G---F-  0
================================================================================
Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization
             C-Collecting, D-Distributing, F-Defaulted, E-Expired</programlisting>
        </listitem>
      </orderedlist></para>
  </section>

  <section id="add_rm_repos">
    <title>Adding/Removing Repositories</title>

    <para>Enea NFV Core has been validated for complete offline deployment. To
    this end, two repositories are defined and used. The first,
    <literal>debian-testing-local</literal> (<filename>deb
    http://10.20.0.2:8080/mirrors/debian testing main</filename>), contains a
    snapshot of the Debian base OS, while the second, <literal>mos</literal>,
    (<literal>deb http://10.20.0.2:8080/newton-10.0/ubuntu/x86_64 mos10.0 main
    restricted</literal>), stores the Enea NFV Core specific Openstack and
    Openstack related packages.</para>

    <para>These repositories provide only the minimum necessary packages, but
    it is possible to add extra repositories as needed. It is recommended
    however, that the first deployment be performed without extra
    repositories.</para>

    <itemizedlist>
      <listitem>
        <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>Remove any extra repositories that point to external
        repositories, by clicking the delete/minus button on the far right of
        the repository entry.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/general_settings.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/general_settings.png" />
          </imageobject>
        </mediaobject>
      </listitem>
    </itemizedlist>
  </section>

  <section id="hypervisor_type">
    <title>Select Hypervisor type</title>

    <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 <literal>KVM</literal> box:</para>

    <mediaobject>
      <imageobject role="fo">
        <imagedata align="center" contentwidth="600"
                   fileref="images/compute_kvm.svg" />
      </imageobject>

      <imageobject role="html">
        <imagedata align="center" fileref="images/compute_kvm.png" />
      </imageobject>
    </mediaobject>
  </section>

  <section id="storage_plugins_addicomps">
    <title>Storage, Plugins and Additional Components</title>

    <para>In the FUEL UI of your Environment, click the
    <literal>Settings</literal> tab and select <literal>Storage</literal>.
    Make sure the components shown below in <literal>Common</literal> and
    <literal>Storage Backends</literal> are enabled:</para>

    <mediaobject>
      <imageobject role="fo">
        <imagedata align="center" contentwidth="600"
                   fileref="images/Ceph_replication.svg" />
      </imageobject>

      <imageobject role="html">
        <imagedata align="center" fileref="images/Ceph_replication.png" />
      </imageobject>
    </mediaobject>

    <para>Save your settings and select <literal>OpenStack Services</literal>
    on the left side pane. <literal>Install Ceilometer and Aodh</literal>
    should be enabled, while <literal>Tacker VNF manager</literal> should not.
    Tacker functionality will be enabled after deployment is performed.</para>

    <mediaobject>
      <imageobject role="fo">
        <imagedata align="center" contentwidth="600"
                   fileref="images/Ceilometer_Aodhchecked_Tackerunchecked.svg" />
      </imageobject>

      <imageobject role="html">
        <imagedata align="center"
                   fileref="images/Ceilometer_Aodhchecked_Tackerunchecked.png" />
      </imageobject>
    </mediaobject>

    <para>Select <literal>Other</literal> on the left pane and do the
    following:</para>

    <itemizedlist>
      <listitem>
        <para>Enable and configure Zabbix for Fuel</para>
      </listitem>

      <listitem>
        <para>Enable and configure Fuel Vitrage Plugin</para>
      </listitem>

      <listitem>
        <para>Check the box for <literal>Use Zabbix Datasource in
        Vitrage</literal>:</para>
      </listitem>

      <listitem>
        <para>Enable and configure the KVM For NFV Plugin.</para>

        <note>
          <para>Currently the KVM For NFV Plugin is only available for x86
          architectures. Refer to the <emphasis role="bold">OPNFV
          KVMforNFV</emphasis> Project for more information.</para>
        </note>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/Vitrage_KVM_2.11.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/Vitrage_KVM_2.11.png" />
          </imageobject>
        </mediaobject>
      </listitem>
    </itemizedlist>
  </section>

  <section id="allocate_nodes_assign_roles">
    <title>Allocate Nodes and assign Functional Roles</title>

    <para>This is accomplished in the following way:</para>

    <orderedlist>
      <listitem>
        <para>Click on the <literal>Nodes</literal> Tab in the FUEL WEB
        UI:</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/allocate_nodes.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/allocate_nodes.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Assign roles:</para>

        <itemizedlist>
          <listitem>
            <para>Click on the <literal>+Add Nodes</literal> button</para>
          </listitem>

          <listitem>
            <para>Check the <literal>Controller, Ceph OSD</literal>
            roles</para>
          </listitem>

          <listitem>
            <para>Check one node which you want to act as a Controller from
            the bottom half of the screen.</para>
          </listitem>

          <listitem>
            <para>Click <literal>Apply Changes</literal></para>
          </listitem>

          <listitem>
            <para>Click on the <literal>+Add Nodes</literal> button</para>
          </listitem>

          <listitem>
            <para>Check <literal>Controller, Telemetry -
            MongoDB</literal></para>
          </listitem>

          <listitem>
            <para>Check one node to assign these roles</para>
          </listitem>

          <listitem>
            <para>Click <literal>Apply Changes</literal></para>
          </listitem>

          <listitem>
            <para>Click on <literal>+Add Nodes</literal> button</para>
          </listitem>

          <listitem>
            <para>Check <literal>Controller, Vitrage</literal></para>
          </listitem>

          <listitem>
            <para>Check one node to assign as a Controller</para>
          </listitem>

          <listitem>
            <para>Click <literal>Apply Changes</literal></para>
          </listitem>

          <listitem>
            <para>Check the <literal>Compute, Ceph OSD</literal> roles</para>
          </listitem>

          <listitem>
            <para>Check the nodes you want to act as Computes from the bottom
            half of the screen.</para>
          </listitem>

          <listitem>
            <para>Click <literal>Apply Changes</literal></para>

            <mediaobject>
              <imageobject role="fo">
                <imagedata align="center" contentwidth="600"
                           fileref="images/Corrected_node_roles_result.svg" />
              </imageobject>

              <imageobject role="html">
                <imagedata align="center"
                           fileref="images/Corrected_node_roles_result.png" />
              </imageobject>
            </mediaobject>
          </listitem>
        </itemizedlist>

        <note>
          <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>
        </note>
      </listitem>

      <listitem>
        <para>Configure interfaces for the Controller nodes:</para>

        <itemizedlist>
          <listitem>
            <para>Select all Controller nodes</para>
          </listitem>

          <listitem>
            <para>Click [Configure Interfaces]</para>
          </listitem>

          <listitem>
            <para>Assign physical interfaces or bonds (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>
                <imageobject role="fo">
                  <imagedata align="center" contentwidth="600"
                             fileref="images/config_nodes.svg" />
                </imageobject>

                <imageobject role="html">
                  <imagedata align="center" fileref="images/config_nodes.png" />
                </imageobject>
              </mediaobject></para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Configure Compute nodes interfaces:</para>

        <itemizedlist>
          <listitem>
            <para>Select the Compute nodes</para>
          </listitem>

          <listitem>
            <para>Click &lt;Configure Interfaces&gt;</para>
          </listitem>

          <listitem>
            <para>Assign physical interfaces or bonds (in this case Public,
            Storage and Management were set on the first 10GbE Port and
            Private on the second 10GbE port; Admin is on a 1Gb port)</para>
          </listitem>

          <listitem>
            <para>For the Private network enable DPDK</para>
          </listitem>

          <listitem>
            <para>Click Apply</para>

            <mediaobject>
              <imageobject role="fo">
                <imagedata align="center" contentwidth="600"
                           fileref="images/config_nodes_2.svg" />
              </imageobject>

              <imageobject role="html">
                <imagedata align="center" fileref="images/config_nodes_2.png" />
              </imageobject>
            </mediaobject>
          </listitem>
        </itemizedlist>
      </listitem>
    </orderedlist>
  </section>

  <section id="config_wl_accel">
    <title>Configure Workload Acceleration</title>

    <para>Enea NFV Core <xi:include
    href="../../s_docsrc_common/pardoc-distro.xml"
    xmlns:xi="http://www.w3.org/2001/XInclude"
    xpointer="element(EneaNFV_REL_VER/1)" /> supports NFV workload
    acceleration features such as Huge Pages, Single-Root I/O Virtualization
    (SR-IOV), Data Plane Developer Kit (DPDK), Non-Uniform Memory Access
    (NUMA) and CPU pinning. Please refer to the <ulink
    url="https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-user-guide/configure-environment/nfv.html">Fuel
    User Guide</ulink> for more information.</para>

    <para><remark>Describe how to enable SR-IOV on the compute nodes (in the
    Interface Configuration menu). Add: Make sure to select a network
    interface which has no network assigned to it.</remark></para>

    <para>This step is needed for the DPDK based scenarios.</para>

    <orderedlist>
      <listitem>
        <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 pops up, expand the <literal>Node
            Attributes</literal> menu.</para>
          </listitem>

          <listitem>
            <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 Nova and 2048MB for
            DPDK.</para>

            <mediaobject>
              <imageobject role="fo">
                <imagedata align="center" contentwidth="600"
                           fileref="images/hugepages.svg" />
              </imageobject>

              <imageobject role="html">
                <imagedata align="center" fileref="images/hugepages.png" />
              </imageobject>
            </mediaobject>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Perform the same configuration for the other Compute
        nodes.</para>
      </listitem>
    </orderedlist>
  </section>

  <section id="target_config">
    <title>Target Specific Configuration</title>

    <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 "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 "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 "Verify Networks" with non-default
        "Offloading Modes".</para>

        <para>Please see the chapter <olink
        targetdoc="book_enea_nfv_core_release_info"
        targetptr="bugs-limitations">Known Issues and Limitations, in the
        <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
        xmlns:xi="http://www.w3.org/2001/XInclude"
        xpointer="element(book_enea_nfv_core_release_info/1)" /></olink> for
        the <phrase>1.1</phrase> release, 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>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>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 the Fuel Master console, identify target nodes' admin
            IPs</para>

            <programlisting>$ fuel nodes</programlisting>

            <remark>Insert the appropriate figure/screenshot</remark>
          </listitem>

          <listitem>
            <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>
          </listitem>
        </itemizedlist>
      </listitem>
    </orderedlist>
  </section>

  <section id="verify_net">
    <title>Verify Networks</title>

    <para>It is important that the Verify Networks action is performed as it
    will verify that Communicate <remark>what is Communicate and does this
    apply to our settings</remark> works for the networks you have setup.
    Also, check that packages needed for a successful deployment can be
    fetched:</para>

    <orderedlist>
      <listitem>
        <para>From the FUEL UI, select the <literal>Networks</literal> tab,
        then select "Connectivity check" on the left pane.</para>
      </listitem>

      <listitem>
        <para>Select <literal>Verify Networks</literal></para>
      </listitem>

      <listitem>
        <para>Continue to fix your topology (physical switch, etc.) until the
        <literal>Verification succeeded. Your network is configured
        correctly.</literal> message is shown.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/verification_succeeded.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center"
                       fileref="images/verification_succeeded.png" />
          </imageobject>
        </mediaobject>
      </listitem>
    </orderedlist>
  </section>

  <section id="deploy_env">
    <title>Deploy your Environment</title>

    <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
    Changes</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>

    <itemizedlist>
      <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 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>
      </listitem>
    </itemizedlist>
  </section>

  <section id="health_check">
    <title>Installation Health-Check</title>

    <para>Once the deploy process is complete, it is recommended to run a
    health check from the Fuel menu, done in the following way:</para>

    <orderedlist>
      <listitem>
        <para>Click the <literal>Health Check</literal> tab inside the FUEL
        Web UI</para>
      </listitem>

      <listitem>
        <para>Check the [Select All] option, then [Run Tests]</para>
      </listitem>

      <listitem>
        <para>Allow tests to run and investigate results where
        appropriate.</para>
      </listitem>
    </orderedlist>

    <para>On Mixed Arch deployments, certain tests might fail due to
    limitations detailed in the <olink
    targetdoc="book_enea_nfv_core_release_info"
    targetptr="bugs-limitations-gen">Know Issues and Limitations in the
    <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml"
    xmlns:xi="http://www.w3.org/2001/XInclude"
    xpointer="element(book_enea_nfv_core_release_info/1)" /></olink>.</para>
  </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 role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/00-Horizon.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/00-Horizon.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Login with credentials (admin/admin is the default):</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/01-Horizon-Login.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/01-Horizon-Login.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>If DPDK is used, the default flavour
        <filename>m1.micro</filename> should be modified.</para>

        <para>In order to do this, select Admin|System|Flavors and all flavors
        will be displayed. Note that <filename>m1.micro</filename> has no
        metadata. Specific metadata for DPDK will be added.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/1-Admin_Flavors.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/1-Admin_Flavors.png" />
          </imageobject>
        </mediaobject>

        <para>Click on No under Metadata. The "Update Flavor Metadata" window
        will appear. Write "hw:mem_page_size" in Custom field and press the
        plus sign.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/2-Update_Flavour_Metadata_Create.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center"
                       fileref="images/2-Update_Flavour_Metadata_Create.png" />
          </imageobject>
        </mediaobject>

        <para>Now set the value "any" for the "hw:mem_page_size" metadata you
        created previously and press Save.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/3-Update_Flavour_Metadata_Set.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center"
                       fileref="images/3-Update_Flavour_Metadata_Set.png" />
          </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 wizard to appear.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/02-create.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/02-create.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Give a name to the first instance and press Next.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/03-name.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/03-name.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Select <filename>Image</filename> in the <literal>Select Boot
        Source</literal> in the dropdown list. Add the TestVM image by
        pressing on the add/plus sign, then press Next.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/04-image.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/04-image.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Add the <filename>m1.micro</filename> flavor by clicking on the
        plus sign, then press Next.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/05-flavor.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/05-flavor.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Add the <literal>admin_internal_net</literal> network by
        pressing on the plus sign and leave the defaults as they are.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/06-network.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/06-network.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>The <literal>Launch Instance</literal> button is now active and
        able to be selected.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/07-launch.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/07-launch.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>After a short while, the first virtual machine is created and
        running.</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/08-created.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/08-created.png" />
          </imageobject>
        </mediaobject>
      </listitem>

      <listitem>
        <para>Repeat the steps above to create the second virtual machine.
        Make a note of the IP addresses allocated:</para>

        <mediaobject>
          <imageobject role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/09-created2.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/09-created2.png" />
          </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 role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/10-VM-login.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/10-VM-login.png" />
          </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 role="fo">
            <imagedata align="center" contentwidth="600"
                       fileref="images/11-VM-ping.svg" />
          </imageobject>

          <imageobject role="html">
            <imagedata align="center" fileref="images/11-VM-ping.png" />
          </imageobject>
        </mediaobject>
      </listitem>
    </itemizedlist>
  </section>
</chapter>