path: root/book-enea-nfv-installation-guide/doc/installation_deployment.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="sw-installation-deployment">
  <title>ENFV Software Installation and Deployment</title>

  <para>This section describes the installation of the ENFV installation
  server (Fuel master) as well as the deployment of the full ENFV reference
  platform stack across a server cluster.</para>

  <section id="instal-fuel-master">
    <title>Install Fuel master</title>

    <orderedlist>
      <listitem>
        <para>Mount the ENFV Fuel ISO file/media as a boot device to the jump
        host server.</para>
      </listitem>

      <listitem>
        <para>Reboot the jump host to establish the Fuel server:</para>

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

          <listitem>
            <para>Select &rdquor;Fuel Install (Static IP)&rdquo; (See figure
            below)</para>

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

          <listitem>
            <para>Press [Enter]</para>
          </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 &rdquor;Fuel User&rdquo; section, confirm/change the
        default password (see figure below) <remark>Insert the appropriate
        figure/screenshot</remark></para>

        <itemizedlist>
          <listitem>
            <para>Enter &rdquor;admin&rdquo; in the Fuel password input</para>
          </listitem>

          <listitem>
            <para>Enter &rdquor;admin&rdquo; in the Confirm password
            input</para>
          </listitem>

          <listitem>
            <para>Select &rdquor;Check&rdquo; and press [Enter]</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>In the &rdquor;Network Setup&rdquo; 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 (see figure below) <remark>Insert the appropriate
        figure/screenshot</remark>.</para>

        <itemizedlist>
          <listitem>
            <para>Configure eth1 or other network interfaces here as well (if
            you have them present on your FUEL server).</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>In the &rdquor;PXE Setup&rdquo; section (see figure below),
        change the following fields to appropriate values, for example:</para>

        <itemizedlist>
          <listitem>
            <para>DHCP Pool Start 10.20.0.3</para>
          </listitem>

          <listitem>
            <para>DHCP Pool End 10.20.0.254</para>
          </listitem>

          <listitem>
            <para>DHCP Pool Gateway 10.20.0.2 (IP address of Fuel node)</para>

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

      <listitem>
        <para>In the &rdquor;DNS &amp; Hostname&rdquo; section (see figure
        below), change the following fields to appropriate values:</para>

        <itemizedlist>
          <listitem>
            <para>Hostname</para>
          </listitem>

          <listitem>
            <para>Domain</para>
          </listitem>

          <listitem>
            <para>Search Domain</para>
          </listitem>

          <listitem>
            <para>External DNS</para>
          </listitem>

          <listitem>
            <para>Hostname to test DNS</para>
          </listitem>

          <listitem>
            <para>Select &lt;Check&gt; and press [Enter]</para>

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

      <listitem>
        <para>You have the option to enable PROXY SUPPORT. In the
        &rdquor;Bootstrap Image&rdquo; section (see figure below), edit the
        following fields to define a proxy. This cannot be used in tandem with
        local repository support.</para>

        <itemizedlist>
          <listitem>
            <para>Navigate to &rdquor;HTTP proxy&rdquo; and enter your http
            proxy address</para>
          </listitem>

          <listitem>
            <para>Select &lt;Check&gt; and press [Enter]</para>

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

      <listitem>
        <para>In the &rdquor;Time Sync&rdquo; section (see figure below),
        change the following fields to appropriate values:</para>

        <itemizedlist>
          <listitem>
            <para>NTP Server 1 &lt;Customer NTP server 1&gt;</para>
          </listitem>

          <listitem>
            <para>NTP Server 2 &lt;Customer NTP server 2&gt;</para>
          </listitem>

          <listitem>
            <para>NTP Server 3 &lt;Customer NTP server 3&gt;</para>

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

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

        <itemizedlist>
          <listitem>
            <para>Select "Quit Setup" 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-node-servers">
    <title>Boot the Node Servers</title>

    <para>After the Fuel Master node has rebooted from the steps mentioned
    above 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>

        <itemizedlist>
          <listitem>
            <para>For every controller and compute server: enable PXE Booting
            as the first boot device in the BIOS boot order menu, and hard
            disk as the second boot device in the same menu.</para>
          </listitem>
        </itemizedlist>
      </listitem>

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

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

        <itemizedlist>
          <listitem>
            <para>Connect to the FUEL UI via the URL provided in the Console
            (default: https://10.20.0.2:8443).</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): <remark>Insert the appropriate
            figure/screenshot</remark></para>
          </listitem>
        </itemizedlist>
      </listitem>
    </orderedlist>
  </section>

  <section id="plugins-features">
    <title>Install additional Plugins/Features on the FUEL node</title>

    <para>Use the following procedure to install additional plugins and
    features:</para>

    <orderedlist>
      <listitem>
        <para>SSH to your FUEL node (e.g. root@10.20.0.2 pwd: r00tme)</para>
      </listitem>

      <listitem>
        <para>Select wanted plugins/features from the /opt/enfv/
        directory.</para>
      </listitem>

      <listitem>
        <para>Install each wanted plugin with the command:</para>

        <programlisting>$ fuel plugins --install /opt/enfv/&lt;plugin-name&gt;-&lt;version&gt;.&lt;arch&gt;.rpm</programlisting>

        <para>Expected output (see figure below):</para>

        <programlisting>Plugin ....... was successfully installed.</programlisting>

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

  <section id="create-openstack">
    <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 (default:
        https://10.20.0.2:8443) (login: admin/admin)</para>
      </listitem>

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

      <listitem>
        <para>Select &rdquor;Mitaka on Ubuntu 14.04&rdquo; and press
        [Next]</para>
      </listitem>

      <listitem>
        <para>Select &rdquor;compute virtualization method&rdquo;, then select
        &rdquor;QEMU-KVM as hypervisor&rdquo; and press [Next]</para>
      </listitem>

      <listitem>
        <para>Select &rdquor;network mode&rdquo;</para>

        <itemizedlist>
          <listitem>
            <para>Select &rdquor;Neutron with ML2 plugin&rdquo;</para>
          </listitem>

          <listitem>
            <para>Select &rdquor;Neutron with tunneling segmentation&rdquo;,
            required when using the ODL or ONOS plugins.</para>
          </listitem>

          <listitem>
            <para>Press [Next]</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Select &rdquor;Storage Back-ends&rdquo;, then &rdquor;Ceph for
        block storage&rdquo; and press [Next]</para>
      </listitem>

      <listitem>
        <para>Select the &rdquor;additional services&rdquo; you wish to
        install</para>

        <itemizedlist>
          <listitem>
            <para>Check option &rdquor;Install Ceilometer and Aodh&rdquo; and
            press [Next]</para>
          </listitem>
        </itemizedlist>
      </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 networks tab and select the &rdquor;default&rdquo; Node
        Networks group on the left pane (see figure below) .</para>

        <remark>Insert the appropriate figure/screenshot</remark>
      </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;</para>
          </listitem>

          <listitem>
            <para>IP Range End to &lt;Public IP Address end&gt;</para>
          </listitem>

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

          <listitem>
            <para>Check &lt;VLAN tagging&gt;</para>
          </listitem>

          <listitem>
            <para>Set appropriate VLAN ID</para>
          </listitem>
        </itemizedlist>
      </listitem>

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

        <itemizedlist>
          <listitem>
            <para>Set CIDR to an appropriate value (default
            192.168.1.0/24)</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 to an appropriate value (default 102)</para>
          </listitem>
        </itemizedlist>
      </listitem>

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

        <itemizedlist>
          <listitem>
            <para>Set CIDR to an appropriate value (default
            192.168.0.0/24)</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>Check &lt;VLAN tagging&gt;</para>
          </listitem>

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

      <listitem>
        <para>Update the Private Network information:</para>

        <itemizedlist>
          <listitem>
            <para>Set CIDR to an appropriate value (default
            192.168.2.0/24)</para>
          </listitem>

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

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

          <listitem>
            <para>Check &lt;VLAN tagging&gt;</para>
          </listitem>

          <listitem>
            <para>Set 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>
      </listitem>

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

        <itemizedlist>
          <listitem>
            <para>Set the Floating IP range start (default
            172.16.0.130)</para>
          </listitem>

          <listitem>
            <para>Set the Floating IP range end (default 172.16.0.254)</para>
          </listitem>

          <listitem>
            <para>Set the Floating network name (default
            admin_floating_net)</para>
          </listitem>
        </itemizedlist>
      </listitem>

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

        <itemizedlist>
          <listitem>
            <para>Set Internal network CIDR to an appropriate value (default
            192.168.111.0/24)</para>
          </listitem>

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

          <listitem>
            <para>Set the Internal network name (default
            admin_internal_net)</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Update the Guest OS DNS servers by setting Guest OS DNS Server
        values appropriately</para>
      </listitem>

      <listitem>
        <para>Save Settings</para>
      </listitem>

      <listitem>
        <para>Select the &rdquor;Other&rdquo; Node Networks group on the left
        pane (see figure below) <remark>Insert the appropriate
        figure/screenshot</remark></para>
      </listitem>

      <listitem>
        <para>Update the Public Network assignment by checking the box for
        &rdquor;Assign public network to all nodes&rdquo; (required by
        OpenDaylight).</para>
      </listitem>

      <listitem>
        <para>Update Host OS DNS Servers by providing the DNS server
        settings</para>
      </listitem>

      <listitem>
        <para>Update Host OS NTP Servers by providing the NTP server
        settings</para>
      </listitem>
    </orderedlist>
  </section>

  <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 (see figure
        below), check the KVM box and press [Save settings]</para>

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

  <section id="enable-plugins">
    <title>Enable Plugins</title>

    <para>To enable needed plugins, follow these steps:</para>

    <orderedlist>
      <listitem>
        <para>In the FUEL UI of your Environment, click the
        &rdquor;Settings&rdquo; Tab</para>
      </listitem>

      <listitem>
        <para>Select "Other" on the left side pane (see figure below), then
        enable and configure the plugins of your choice <remark>Insert the
        appropriate figure/screenshot</remark></para>
      </listitem>
    </orderedlist>
  </section>

  <section id="allocate-nodes-assign-roles">
    <title>Allocate Nodes to Environment and assign Functional Roles</title>

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

    <orderedlist>
      <listitem>
        <para>Click on the &rdquor;Nodes&rdquo; Tab in the FUEL WEB UI (see
        figure below) <remark>Insert the appropriate
        figure/screenshot</remark></para>
      </listitem>

      <listitem>
        <para>Assign roles (see figure below):</para>

        <itemizedlist>
          <listitem>
            <para>Click on the [+Add Nodes&gt;] button</para>
          </listitem>

          <listitem>
            <para>Check &lt;Controller&gt;, &lt;Telemetry - MongoDB&gt; and
            optionally an SDN Controller role (OpenDaylight controller/ONOS)
            in the &rdquor;Assign Roles&rdquo; Section.</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 [Apply Changes]</para>
          </listitem>

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

          <listitem>
            <para>Check the &lt;Controller&gt; and &lt;Storage - Ceph OSD&gt;
            roles</para>
          </listitem>

          <listitem>
            <para>Check the next two nodes you want to act as Controllers from
            the bottom half of the screen</para>
          </listitem>

          <listitem>
            <para>Click [Apply Changes]</para>
          </listitem>

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

          <listitem>
            <para>Check the &lt;Compute&gt; and &lt;Storage - Ceph OSD&gt;
            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 [Apply Changes] <remark>Insert the appropriate
            figure/screenshot</remark></para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Configure Interfaces (see figure below):</para>

        <itemizedlist>
          <listitem>
            <para>Check [Select &lt;All&gt;] to select all allocated
            nodes</para>
          </listitem>

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

          <listitem>
            <para>Assign interfaces (bonded) for mgmt-, admin-, private-,
            public- and storage networks, and click [Apply] <remark>Insert the
            appropriate figure/screenshot</remark></para>
          </listitem>
        </itemizedlist>
      </listitem>
    </orderedlist>
  </section>

  <section id="set-local-mirror-repos">
    <title>OPTIONAL - Set Local Mirror Repos</title>

    <para>The following steps must be executed if you are in an environment
    with no connection to the Internet. The Fuel server delivers a local repo
    that can be used for installation/deployment of Openstack.</para>

    <orderedlist>
      <listitem>
        <para>In the Fuel UI of your environment, click the Settings Tab and
        select "General" from the left pane</para>
      </listitem>

      <listitem>
        <para>Replace the URI values for the &rdquor;Name&rdquo; values
        outlined below:</para>

        <itemizedlist>
          <listitem>
            <para>&rdquor;ubuntu&rdquo; URI=&rdquo;deb
            http://&lt;ip-of-fuel-server&gt;:8080/mirrors/ubuntu/trusty main
            universe multiverse&rdquo;</para>
          </listitem>

          <listitem>
            <para>&rdquor;ubuntu-security&rdquo; URI=&rdquo;deb
            http://&lt;ip-of-fuelserver&gt;:8080/mirrors/ubuntu/trusty-security
            main universe multiverse&rdquo;</para>
          </listitem>

          <listitem>
            <para>&rdquor;ubuntu-updates&rdquo; URI=&rdquo;deb
            http://&lt;ip-of-fuelserver&gt;:8080/mirrors/ubuntu/trusty-updates
            main universe multiverse&rdquo;</para>
          </listitem>

          <listitem>
            <para>&rdquor;mos&rdquo; URI=&rdquo;deb
            http://&lt;ip-of-fuel-server&gt;::8080/mitaka-9.0/ubuntu/x86_64
            mos9.0 main restricted&rdquo;</para>
          </listitem>

          <listitem>
            <para>&rdquor;Auxiliary&rdquo; URI=&rdquo;deb
            http://&lt;ip-of-fuel-server&gt;:8080/mitaka-9.0/ubuntu/auxiliary
            auxiliary main restricted&rdquo;</para>
          </listitem>
        </itemizedlist>
      </listitem>

      <listitem>
        <para>Click [Save Settings] at the bottom to save your changes.</para>
      </listitem>
    </orderedlist>
  </section>

  <section id="target-spec-config">
    <title>Target Specific Configuration</title>

    <orderedlist>
      <listitem>
        <para>Set up targets for provisioning with non-default
        &rdquor;Offloading Modes&rdquo;.</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
        figure/screenshot</remark></para>
      </listitem>

      <listitem>
        <para>Set up targets for &rdquor;Verify Networks&rdquo; with
        non-default &rdquor;Offloading Modes&rdquo;.</para>

        <para>Please check the <ulink
        url="http://artifacts.opnfv.org/fuel/colorado/3.0/docs/releasenotes/index.html">ENFV
        Release Notes for the 1.0 release of ENFV 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 &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>

        <itemizedlist>
          <listitem>
            <para>From Fuel master console identify target nodes' admin IPs
            (see figure below):</para>

            <programlisting>$ fuel nodes</programlisting>

            <remark>Insert the appropriate figure/screenshot</remark>
          </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>

            <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-networks">
    <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 in your environment, select the Networks Tab,
        then select &rdquor;Connectivity check&rdquo; on the left pane (see
        figure below): <remark>Insert the appropriate
        figure/screenshot</remark></para>
      </listitem>

      <listitem>
        <para>Select [Verify Networks]</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>
      </listitem>
    </orderedlist>
  </section>

  <section id="deploy-env">
    <title>Deploy your Environment</title>

    <para>In order to deploy your environment, do the following steps:</para>

    <orderedlist>
      <listitem>
        <para>In the Fuel GUI, click on the &rdquor;Dashboard&rdquo;
        Tab</para>
      </listitem>

      <listitem>
        <para>Click on [Deploy Changes] in the &rdquor;Ready to Deploy?&rdquo;
        section</para>
      </listitem>

      <listitem>
        <para>Examine any information notice that pops up and click
        [Deploy]</para>
      </listitem>
    </orderedlist>

    <para>Wait for your deployment to complete. You can view the
    &rdquor;Dashboard&rdquo; Tab to see the progress and status of your
    deployment.</para>
  </section>
</chapter>