Removed section ”2.2 – Enea NFV Access Installer”.

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

1 files changed, 1 insertions, 295 deletions

diff --git a/doc/book-enea-nfv-access-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-guide/doc/getting_started.xml
index b6cf927..5972a90 100644
--- a/doc/book-enea-nfv-access-guide/doc/getting_started.xml
+++ b/doc/book-enea-nfv-access-guide/doc/getting_started.xml
@@ -1,4 +1,4 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
+<?xml version="1.0" encoding="UTF-8"?>
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 <chapter id="plat-release-content">
@@ -42,300 +42,6 @@ Use dash as the default system shell (/bin/sh)? No</programlisting>
     </itemizedlist>
   </section>
 
-  <section id="access_installer">
-    <title>Enea NFV Access Installer</title>
-
-    <para>The easiest way to get started with Enea NFV Access is by using the
-    installer provided for each supported architecture in this release. Each
-    installer guides you in the creation of a bootable Enea NFV Access
-    installation on a physical media.</para>
-
-    <section id="prereq">
-      <title>Prerequisites</title>
-
-      <para>The following files are needed on the development host
-      machine:</para>
-
-      <itemizedlist>
-        <listitem>
-          <para>A GRUB.efi binary - available from the <ulink url="???">GNU
-          GRUB download page</ulink>.</para>
-        </listitem>
-
-        <listitem>
-          <para>For booting from an SSD/HDD: a rootfs that needs to be
-          installed on the board (e.g.
-          <filename>[path_to_EneaNFV_Access_folder]/[architecture]/inteld1521/images/enea-nfv-access/enea-nfv-access.tar.gz</filename>).</para>
-        </listitem>
-
-        <listitem>
-          <para>For USB booting: a development based rootfs (e.g.
-          <filename>[path_to_EneaNFV_Access_folder]/[architecture]/inteld1521/images/enea-nfv-access-dev/enea-nfv-access-dev-inteld1521.tar.gz</filename>).</para>
-        </listitem>
-      </itemizedlist>
-
-      <para>Using the installer on the development host requires the
-      following:</para>
-
-      <itemizedlist>
-        <listitem>
-          <para>A physical drive of 16GB or larger</para>
-        </listitem>
-
-        <listitem>
-          <para>Root permissions</para>
-        </listitem>
-      </itemizedlist>
-    </section>
-
-    <section id="installer_setup_usage">
-      <title>Installer Setup and Usage</title>
-
-      <para><emphasis role="bold">To install Enea NFV Access on a physical
-      drive</emphasis></para>
-
-      <orderedlist>
-        <listitem>
-          <para>Go to the installer location: <programlisting># cd [path_to_EneaNFV_Access_folder]/[architecture]/install/
-nfv-installer/script-installer</programlisting></para>
-        </listitem>
-
-        <listitem>
-          <para>Execute the script file, this will bring you to the installer
-          prompt: <programlisting># sudo ./nfv_installer.sh</programlisting></para>
-        </listitem>
-
-        <listitem>
-          <para>Optionally, press ENTER to see the list of available
-          commands:<programlisting>help - displays a guide on how to use the installer
-list-params - lists all available parameters
-list-steps - lists the installer steps and the parameters that they depend on
-set - sets a parameter (e.g. <literal>set drive=/dev/sda</literal>)
-clear - clears a parameter (e.g. <literal>clear drive</literal>)
-list-partitions - lists current drives and partitions
-dry - performs a simulation test run
-run - executes the installer, using the values you set for each parameter
-q or quit - exits the script</programlisting></para>
-        </listitem>
-
-        <listitem>
-          <para>Set the required parameters depending on what steps you want
-          to run:</para>
-
-          <note>
-            <para>When using the installer for the first time, make sure to
-            set ALL parameters in order to be able to run all steps. See <xref
-                linkend="example_two">
-                 "Example 2" 
-              </xref> for details.</para>
-          </note>
-
-          <para><programlisting># set &lt;parameter_name&gt;=&lt;parameter_value&gt;</programlisting></para>
-
-          <orderedlist>
-            <listitem>
-              <para><parameter>drive=&lt;/dev/sdaX&gt;</parameter> - the drive
-              to partition</para>
-            </listitem>
-
-            <listitem>
-              <para><parameter>grub_binary=&lt;file&gt;</parameter> - points
-              to the <filename>GRUB</filename> executable to be installed
-              where <filename>grub_destination</filename> is set.</para>
-            </listitem>
-
-            <listitem>
-              <para><parameter>grub_destination=&lt;drive&gt;</parameter> -
-              specifies the partition where <filename>GRUB</filename> will be
-              installed</para>
-            </listitem>
-
-            <listitem>
-              <para><parameter>rootfs_destination=&lt;drive&gt;</parameter> -
-              specifies the partition where the <filename>rootfs</filename>
-              will be deployed, used by <filename>GRUB</filename> to boot off
-              of.</para>
-            </listitem>
-
-            <listitem>
-              <para><parameter>rootfs_targz=&lt;rootfs.tar.gz
-              file&gt;</parameter> - the archive of the Enea NFV Access
-              <filename>rootfs</filename> you wish to unpack to where
-              <filename>rootfs_destination</filename> is set. Which file you
-              unpack depends on whether you booting from an SSD/HDD or from a
-              USB drive.</para>
-            </listitem>
-          </orderedlist>
-        </listitem>
-
-        <listitem>
-          <para>Optionally, perform a test run before affecting the actual
-          layout of the physical media with the command: <programlisting>dry</programlisting></para>
-        </listitem>
-
-        <listitem>
-          <para>Run the installer: <programlisting>run</programlisting></para>
-        </listitem>
-
-        <listitem>
-          <para>Exit the script: <programlisting>quit</programlisting></para>
-        </listitem>
-      </orderedlist>
-
-      <para>The Enea NFV Access installer creates a bootable media by
-      performing three steps. Each step is executed or not depending on
-      whether certain parameters are set:</para>
-
-      <orderedlist>
-        <listitem>
-          <para><command>Format drive</command> - creates a 512MB partition
-          which will be used by <filename>GRUB</filename>, and another to be
-          used for the <filename>rootfs</filename> (it should occupy the rest
-          of the physical media minus the first partition). This step depends
-          on the following parameter(s): <programlisting>drive=</programlisting></para>
-        </listitem>
-
-        <listitem>
-          <para><emphasis role="bold">GRUB install</emphasis> - Installs the
-          <literal>grub_binary</literal> on the drive set for
-          <literal>grub_destination</literal>. A <filename>grub.cfg</filename>
-          file will be created that will be configured to boot off of
-          <literal>rootfs_destination</literal>. This step depends on the
-          following parameters:<programlisting>grub_destination=
-grub_binary=
-rootfs_destination=</programlisting></para>
-        </listitem>
-
-        <listitem>
-          <para><emphasis role="bold">Root Filesystem install</emphasis> -
-          Copies and unpacks the files found in
-          <literal>rootfs_targz</literal> to the
-          <literal>rootfs_destination</literal>. This step depends on the
-          following parameters:<programlisting>rootfs_targz=
-rootfs_destination=</programlisting></para>
-        </listitem>
-      </orderedlist>
-
-      <para>After using the installer and setting up the bootable media,
-      connect it to the target machine and configure the target machine to use
-      it as a primary boot device.</para>
-    </section>
-
-    <section id="examples">
-      <title>Examples of Execution</title>
-
-      <para>Below are a few examples of setups that the Enea NFV Access
-      installer can be used for:</para>
-
-      <example id="example_one">
-        <title>Partitioning a drive</title>
-
-        <programlisting>set drive=/dev/sda
-run</programlisting>
-      </example>
-
-      <example id="example_two">
-        <title>Partitioning a drive, installing GRUB and a Root
-        Filesystem:</title>
-
-        <programlisting>set drive=/dev/sda
-set grub_destination=/dev/sda1
-set grub_binary=/home/user/grub-binary.efi
-set rootfs_destination=/dev/sda2
-set rootfs_targz=/home/user/rootfs.tar.gz
-run</programlisting>
-      </example>
-
-      <example id="example_three">
-        <title>Deploying ONLY a root filesystem:</title>
-
-        <programlisting>set rootfs_destination=/dev/sda2
-set rootfs_targz=/home/user/rootfs.tar.gz
-run</programlisting>
-      </example>
-    </section>
-
-    <section id="troubleshooting">
-      <title>Troubleshooting</title>
-
-      <para>GRUB might display the following errors if the default
-      configuration is set to use <filename>hd0</filename> as the primary
-      drive for booting:</para>
-
-      <itemizedlist>
-        <listitem>
-          <para><literal>error: no such partition</literal></para>
-        </listitem>
-
-        <listitem>
-          <para><literal>error: disk not found</literal></para>
-        </listitem>
-      </itemizedlist>
-
-      <para>These errors have two possible causes:</para>
-
-      <itemizedlist>
-        <listitem>
-          <para>The drive where Enea NFV Access was installed is not
-          identified as <literal>hd0</literal> by BIOS.</para>
-        </listitem>
-
-        <listitem>
-          <para>BIOS has assigned the <literal>hd0</literal> label to a
-          different drive (e.g. a USB stick) than the one where Enea NFV
-          Access was installed.</para>
-        </listitem>
-      </itemizedlist>
-
-      <para>To rectify these problems the primary boot drive must be assigned
-      to the correct partition.</para>
-
-      <para><emphasis role="bold">To change the partition for the primary boot
-      drive</emphasis></para>
-
-      <orderedlist>
-        <listitem>
-          <para>Restart the host and in the <filename>GRUB</filename>
-          selection screen, enter the command line by pressing
-          <command>C</command>:</para>
-
-          <mediaobject>
-            <imageobject>
-              <imagedata align="center" contentwidth="600"
-                         fileref="images/select-linux-kernel-in-grub2-boot-loader-on-ubuntu-14.04.svg" />
-            </imageobject>
-          </mediaobject>
-        </listitem>
-
-        <listitem>
-          <para>List all of the available partitions with
-          <command>ls</command>: <programlisting>partition list example</programlisting></para>
-        </listitem>
-
-        <listitem>
-          <para>In order to identify where Enea NFV Access was installed, for
-          each available partition run <emphasis role="bold">ls
-          &lt;partition&gt;</emphasis>: <programlisting>ls hd0</programlisting></para>
-        </listitem>
-
-        <listitem>
-          <para>After identifying the partition, return to the GRUB selection
-          screen by pressing <command>esc</command></para>
-        </listitem>
-
-        <listitem>
-          <para>Press <command>e</command> to edit and set the boot partition
-          to the one identified previously: <programlisting>edit and set partition example</programlisting></para>
-        </listitem>
-
-        <listitem>
-          <para>To reboot to see if the change worked, press:
-          <command>F10</command></para>
-        </listitem>
-      </orderedlist>
-    </section>
-  </section>
-
   <section condition="hidden" id="release-content">
     <title>NFV Access Release content</title>