AccessDocs: update RelInfo, GetStarted, RefGuide

- update Prerequisites in getting_started_nfv_access
- remove chapter 2, this is described in the Rel Info
- remove Default Shell Configuration
- remove "Device Name" VNF is not being managed as a device, so
  there's no device name
- change "OSTree" chapter name in Reference Guide to “Software update”.
- add 4G/LTE modems support to New Feature chapter in the Rel Info

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

8 files changed, 73 insertions, 114 deletions

diff --git a/doc/book-enea-nfv-access-getting-started/doc/book.xml b/doc/book-enea-nfv-access-getting-started/doc/book.xml
index aa58335..6dde8db 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/book.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/book.xml
@@ -17,8 +17,6 @@
 
   <xi:include href="introduction.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude" />                               
-  <xi:include href="documentation.xml"
-              xmlns:xi="http://www.w3.org/2001/XInclude" />     
 
   <xi:include href="getting_started_nfv_access.xml"
                 xmlns:xi="http://www.w3.org/2001/XInclude" />
diff --git a/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml b/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml
index 861c739..d68a342 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/device_configuration_and_provisioning.xml
@@ -45,7 +45,7 @@
       <listitem>
         <para>SSH Port. The NETCONF Port used for communications. This is a
         relevant parameter if the standard NETCONF SSH (i.e. not Call-Home) is
-        being used. Default is set to 22.</para>
+        being used. Default is set to 830.</para>
       </listitem>
     </itemizedlist>
 
@@ -713,14 +713,6 @@
         </listitem>
 
         <listitem>
-          <para><emphasis role="bold">Device Name</emphasis>. The name by
-          which the VNF will be known in the uCPE Manager, if the
-          <literal>Manage Device</literal> checkbox is checked. If unchecked,
-          the VNF will not be shown as a managed device in the uCPE
-          Manager.</para>
-        </listitem>
-
-        <listitem>
           <para><emphasis role="bold">Instantiation Parameters</emphasis>.
           This section contains all the parameters a user needs to supply when
           instantiating a VNF of this type. The <literal>VProbe</literal> VNF
diff --git a/doc/book-enea-nfv-access-getting-started/doc/documentation.xml b/doc/book-enea-nfv-access-getting-started/doc/documentation.xml
deleted file mode 100644
index fb84322..0000000
--- a/doc/book-enea-nfv-access-getting-started/doc/documentation.xml
+++ /dev/null
@@ -1,35 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<chapter id="documentation">
-  <title>Documentation</title>
-
-  <para>User guides and development documentation are available for download
-  on the <ulink url="https://portal.enea.com/">portal</ulink>:</para>
-
-  <orderedlist>
-    <listitem>
-      <para>Log in with the credentials provided by Enea.</para>
-    </listitem>
-
-    <listitem>
-      <para>In the top right menu, select <emphasis
-      role="bold">Access</emphasis> and choose a release version from those
-      listed on the left, (Enea NFV Access X.Y.Z). The newest is always at the
-      top. Enter that version by clicking the blue name text and scroll down
-      until you see the documentation file(s) you wish to download.</para>
-
-      <para>The documents listed below are the primary ones to consult:</para>
-
-      <itemizedlist>
-        <listitem>
-          <para>Enea NFV Access Reference Guide. <remark>make this into an
-          olink</remark></para>
-        </listitem>
-
-        <listitem>
-          <para>Enea NFV Access Getting Started (the present document).</para>
-        </listitem>
-
-      </itemizedlist>
-    </listitem>
-  </orderedlist>
-</chapter>
diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
index 661b951..3fdedad 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_nfv_access.xml
@@ -1,42 +1,13 @@
-<?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">
   <title>Getting Started with Enea NFV Access</title>
 
-  <para>Using Enea NFV Access requires access to a Linux machine, which is
-  used for preparing a bootable drive or for developing applications.</para>
-
-  <section id="sysshell_config">
-    <title>Default Shell Configuration</title>
-
-    <para>Before installing Enea NFV Access, make sure that <emphasis
-    role="bold">bash</emphasis> is the default shell.</para>
-
-    <para><emphasis role="bold">To verify the default system
-    shell</emphasis></para>
-
-    <itemizedlist>
-      <listitem>
-        <para>If your system runs Ubuntu, use list to verify if
-        <filename>/bin/sh</filename> is a symbolic link to
-        <literal>bash</literal>:</para>
-
-        <programlisting># ls -l /bin/sh
-lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -&gt; bash</programlisting>
-      </listitem>
-
-      <listitem>
-        <para>Optionally, in case the link points to <literal>dash</literal>,
-        change it through the following steps:</para>
-
-        <programlisting># ls -l /bin/sh
-lrwxrwxrwx 1 root root 4 2012-03-02 11:53 /bin/sh -&gt; dash
-# sudo dpkg-reconfigure dash
-Use dash as the default system shell (/bin/sh)? No</programlisting>
-      </listitem>
-    </itemizedlist>
-  </section>
+  <para>Enea NFV Access is a virtualization and management platform for white
+  box uCPEs. It scales from ultra-low to high end CPEs, providing minimal
+  footprint and maximum networking performance. NFV Access can be deployed on
+  large number of devices with various hardware configurations.</para>
 
   <section id="access_installer">
     <title>Enea NFV Access Installer</title>
@@ -49,22 +20,51 @@ Use dash as the default system shell (/bin/sh)? No</programlisting>
       <title>Prerequisites</title>
 
       <para>To install the Enea NFV Access platform, 3 things are required: a
-      USB stick (16GB or larger), a development machine (Linux or Windows) and
-      a target device.</para>
+      USB stick (16GB or larger), a development machine with root
+      permissions(Linux or Windows) and a target device.</para>
 
-      <para>The target device requires:</para>
+      <para>Minimal requirements for white box for NFV Access:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>EFI and virtualization support</para>
+        </listitem>
+
+        <listitem>
+          <para>2 cores</para>
+        </listitem>
+
+        <listitem>
+          <para>4GB RAM</para>
+        </listitem>
+
+        <listitem>
+          <para>Stoarge Device (SSD recommended)</para>
+        </listitem>
+
+        <listitem>
+          <para>2 physical interfaces</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>Following BIOS settings to be enabled:</para>
 
       <itemizedlist spacing="compact">
+
         <listitem>
-          <para>Root permissions</para>
+          <para>EFI</para>
         </listitem>
 
         <listitem>
-          <para>EFI is enabled in BIOS</para>
+          <para>Intel Virtualization Technology (VT-x )</para>
         </listitem>
 
         <listitem>
-          <para>KVM support is enabled in BIOS</para>
+          <para>Intel Virtualization Technology for Directed I/O (VT-d)</para>
+        </listitem>
+
+        <listitem>
+          <para>SR-IOV</para>
         </listitem>
       </itemizedlist>
     </section>
@@ -212,8 +212,8 @@ rootfs_destination=</programlisting></para>
 
       <orderedlist>
         <listitem>
-          <para>Download the HDDIMG file from the download portal onto a Linux
-          machine or Cygwin.</para>
+          <para>Download the HDDIMG file from the download portal onto a
+          development machine (Linux or Windows with Cygwin support).</para>
         </listitem>
 
         <listitem>
@@ -260,7 +260,8 @@ of=/dev/sdb bs=4M conv=fsync</programlisting></para>
 
           <itemizedlist>
             <listitem>
-              <para>live-boot. Boots NFV Access directly from the USB stick.</para>
+              <para>live-boot. Boots NFV Access directly from the USB
+              stick.</para>
             </listitem>
 
             <listitem>
@@ -276,9 +277,8 @@ of=/dev/sdb bs=4M conv=fsync</programlisting></para>
         </listitem>
 
         <listitem>
-          <para>To launch the installer, select one of the
-          <command>installer</command> options below from the GRUB
-          menu:</para>
+          <para>To launch the installer, select <command>installer</command>
+          option from the GRUB menu:</para>
 
           <itemizedlist>
             <listitem>
@@ -407,9 +407,8 @@ of=/dev/sdb bs=4M conv=fsync</programlisting></para>
       BIOS/UEFI) to boot the system from the media storage device where NFV
       Access was installed.</para>
 
-      <para>Once set, GRUB will start automatically when the device is
-      connected and a menu will appear to let the user select one of the boot
-      options:</para>
+      <para>Once set, GRUB will start automatically and a menu will appear to
+      let the user select one of the boot options:</para>
 
       <figure>
         <title>Booting NFV Access</title>
@@ -423,8 +422,8 @@ of=/dev/sdb bs=4M conv=fsync</programlisting></para>
 
       <itemizedlist>
         <listitem>
-          <para><literal>Enea NFV Access 2.2 (rocko) (ostre:0)</literal>:
-          The recommended configuration boot commands.</para>
+          <para><literal>Enea NFV Access 2.2 (rocko) (ostre:0)</literal>: The
+          recommended configuration boot commands.</para>
         </listitem>
 
         <listitem>
@@ -511,9 +510,9 @@ run</programlisting>
 
     <itemizedlist>
       <listitem>
-        <para>If a system has an amount of memory up to 8GB, the allocation
-        algorithm will reserve up to 30%, but no more than 2GB, for the OS and
-        the rest as huge pages.</para>
+        <para>If a system has an amount of memory that's higher than 8GB, the
+        allocation algorithm will reserve 2GB of memory for OS and the rest of
+        memory will try to allocate as 1GB hugepages.</para>
       </listitem>
 
       <listitem>
diff --git a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
index 72c4b32..2704fc8 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/getting_started_ucpe_manager.xml
@@ -5,8 +5,8 @@
   <section id="prere">
     <title>Prerequisites</title>
 
-    <para>Listed below are the main generic prerequisites required so that NFV
-    Access can be deployed on your host platform:</para>
+    <para>Listed below are the main generic prerequisites required so that
+    uCPE Manager can be deployed on your host platform:</para>
 
     <itemizedlist>
       <listitem>
@@ -35,9 +35,8 @@
     defaults to Y), and not the machine as part of a cluster (which defaults
     to N). Installing on a Windows machine, will require the user to follow
     the Windows password policies when defining the password for the <emphasis
-    role="bold">ucpemanager</emphasis> service. A default password will not be
-    accepted. A good example for an acceptable password would be:
-    <emphasis>_1ucpe#2manager!3_</emphasis>.</para>
+    role="bold">ucpemanager</emphasis> service. A good example for an acceptable
+    password would be:<emphasis>_1ucpe#2manager!3_</emphasis>.</para>
 
     <para>Check that the Windows or CentOS machine where the uCPE Manager is
     installed has the firewall disabled. To disable the firewall, if using
diff --git a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
index 9913aaf..c0496e7 100644
--- a/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
+++ b/doc/book-enea-nfv-access-getting-started/doc/introduction.xml
@@ -97,6 +97,13 @@
         <para>In-band management</para>
       </listitem>
     </itemizedlist>
+    <para>For additional information about features provided in Enea NFV
+    Access, refer to the <olink targetdoc=
+    "book_enea_nfv_access_reference_guide_intel">Enea NFV Access Reference Guide</olink>
+    provided with your release. For how to install and run Enea
+    NFV Access on supported devices, please refer to <xref
+    linkend="plat-release-content">
+    Chapter 4, Getting Started with Enea NFV Access</xref>.</para>
 
   </section>
 
@@ -133,12 +140,5 @@
       </listitem>
     </itemizedlist>
 
-    <para>For additional information about features provided in Enea NFV
-    Access, refer to the <olink targetdoc=
-    "book_enea_nfv_access_reference_guide_intel">Enea NFV Access Reference Guide</olink>
-    provided with your release. For how to install and run Enea
-    NFV Access on supported devices, please refer to <xref
-    linkend="plat-release-content">
-    Chapter 4, Getting Started with Enea NFV Access</xref>.</para>
   </section>
 </chapter>
diff --git a/doc/book-enea-nfv-access-reference-guide-intel/doc/ostree.xml b/doc/book-enea-nfv-access-reference-guide-intel/doc/ostree.xml
index c1af593..dc6a693 100755
--- a/doc/book-enea-nfv-access-reference-guide-intel/doc/ostree.xml
+++ b/doc/book-enea-nfv-access-reference-guide-intel/doc/ostree.xml
@@ -2,8 +2,9 @@
 <!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
 <chapter id="ostree">
-  <title>OSTree</title>
+  <title>Software Update</title>
 
+  <para>Enea's Software Update solution is based on OSTree.</para>
   <para>OSTree is an upgrade system for Linux-based operating systems that
   performs atomic upgrades of complete filesystem trees. The underlying
   architecture might be summarized as "git for operating system binaries". It
diff --git a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
index 86244f6..792a1a1 100644
--- a/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
+++ b/doc/book-enea-nfv-access-release-info/doc/main_changes.xml
@@ -18,7 +18,12 @@
       </listitem>
 
       <listitem>
-        <para>OSTree-based upgrade system support.</para>
+        <para>OSTree-based Software upgrade system support.</para>
+      </listitem>
+
+      <listitem>
+        <para>4G/LTE modems support (can be used as device management
+        interface).</para>
       </listitem>
 
       <listitem>