8 files changed, 697 insertions, 70 deletions

diff --git a/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
index 83641b1..c387e7f 100644
--- a/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
+++ b/doc/book-enea-edge-getting-started/doc/advanced_configurations.xml
@@ -437,7 +437,7 @@ node0.1048576kB = 3 </programlisting>
         <listitem>
           <para>Run the following command:</para>
 
-          <programlisting>./createCertificate.sh ucpemanager &lt;IP_or_domain&gt; \
+          <programlisting>./createCertificate.sh EneaEdgeManagement &lt;IP_or_domain&gt; \
             /opt/ems [&lt;service_username&gt;]</programlisting>
 
           <para>Where the following need to be included:</para>
diff --git a/doc/book-enea-edge-getting-started/doc/installation_guide.xml b/doc/book-enea-edge-getting-started/doc/installation_guide.xml
index 1eab201..b4324de 100644
--- a/doc/book-enea-edge-getting-started/doc/installation_guide.xml
+++ b/doc/book-enea-edge-getting-started/doc/installation_guide.xml
@@ -490,12 +490,12 @@ userdel postgres</programlisting>
           <listitem>
             <para>Choose the target installation folder, e.g.
             <literal>/opt/ems</literal>. Everything will be installed under a
-            folder called <literal>/ucpemanager</literal> within the target
-            installation folder.</para>
+            folder called <literal>/ucpemanager</literal> within the
+            target installation folder.</para>
 
             <para>The application files will be installed in
-            <literal>/opt/ems/ucpemanager/application</literal>. The database
-            will be installed in
+            <literal>/opt/ems/ucpemanager/application</literal>. The
+            database will be installed in
             <literal>/opt/ems/ucpemanager/database</literal>.</para>
           </listitem>
 
@@ -503,7 +503,7 @@ userdel postgres</programlisting>
             <para>Run the following interactive command:</para>
 
             <programlisting>./install.sh /opt/ems \
-Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</programlisting>
+Enea_Edge_Management_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</programlisting>
 
             <para>The default configuration values are specified in brackets.
             If no other value is preferred and typed in, pressing
@@ -565,12 +565,12 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
                 <itemizedlist spacing="compact">
                   <listitem>
                     <para>Specify a service username
-                    <literal>[ucpemanager]:</literal></para>
+                    <literal>[EneaEdgeManagement]</literal>:</para>
                   </listitem>
 
                   <listitem>
                     <para>Specify a service password
-                    <literal>[ucpemanager]</literal>:</para>
+                    <literal>[EneaEdgeManagement]</literal>:</para>
                   </listitem>
                 </itemizedlist>
               </listitem>
@@ -593,19 +593,21 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
               </listitem>
 
               <listitem>
-                <para>Create the self-signed certificate: <literal>Specify IP or domain name</literal> 
-                  (or press <literal>Enter</literal> to skip):</para>
-
-                  <para>The Tomcat self-signed certificate can be generated
-                  again by running the
-                  <filename>createCertificate.sh</filename>. For more details, please see <olink
-                  targetdoc="book_enea_edge_getting_started"
-                  targetptr="create_certificate">Tomcat Certificate
-                  Generation in the <ns:include
-                  href="../../s_docbuild/olinkdb/pardoc-names.xml"
-                  xpointer="element(book_enea_edge_getting_started/1)"
-                  xmlns:ns="http://www.w3.org/2001/XInclude" /></olink> Manual.</para>
-                
+                <para>Create the self-signed certificate: <literal>Specify IP
+                or domain name</literal> (or press <literal>Enter</literal> to
+                skip):</para>
+
+                <para>The Tomcat self-signed certificate can be generated
+                again by running the
+                <filename>createCertificate.sh</filename>. For more details,
+                please see <olink targetdoc="book_enea_edge_getting_started"
+                targetptr="create_certificate">Tomcat Certificate Generation
+                in the <ns:include
+                href="../../s_docbuild/olinkdb/pardoc-names.xml"
+                xmlns:ns="http://www.w3.org/2001/XInclude"
+                xpointer="element(book_enea_edge_getting_started/1)" /></olink>
+                Manual.</para>
+
                 <note>
                   <para>The generation of the Tomcat self-signed cerificate
                   should be skipped only if another certifcate will be
@@ -614,14 +616,13 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
               </listitem>
 
               <listitem>
-                <para>Heap Configuration:</para> 
-                
+                <para>Heap Configuration:</para>
+
                 <itemizedlist spacing="compact">
-                    <listitem>
-                      <para>Please enter the new Maximum Heap Size
-                      [4g]:</para>
-                    </listitem>
-                  </itemizedlist>
+                  <listitem>
+                    <para>Please enter the new Maximum Heap Size [4g]:</para>
+                  </listitem>
+                </itemizedlist>
               </listitem>
             </itemizedlist>
 
@@ -639,11 +640,13 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
 
               <listitem>
                 <para>Install the Enea Edge Management application as a
-                service with the name <literal>ucpemanager</literal>.</para>
+                service with the name
+                <literal>ucpemanager</literal>.</para>
               </listitem>
 
               <listitem>
-                <para>Start the <literal>ucpemanager</literal> service.</para>
+                <para>Start the <literal>ucpemanager</literal>
+                service.</para>
               </listitem>
             </itemizedlist>
           </listitem>
@@ -657,8 +660,8 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
         </orderedlist>
 
         <note>
-          <para>The IPv4 address of the CentOS 7 Server will be used as a configuration
-          parameter when setting up the uCPE devices.</para>
+          <para>The IPv4 address of the CentOS 7 Server will be used as a
+          configuration parameter when setting up the uCPE devices.</para>
 
           <para>If the CentOS 7 Server is installed behind NAT, the IPv4
           address used will be the public IP of the NAT device and port
@@ -680,8 +683,8 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
         role="bold">System</emphasis> menu, and clicking <emphasis
         role="bold">System Backup</emphasis>, from the Enea Edge Management
         GUI. The resulting zip archive will be located in the
-        <filename>/opt/ems/ucpemanager/application/backup</filename> folder
-        and will be named
+        <filename>/opt/ems/ucpemanager/application/backup</filename>
+        folder and will be named
         <literal>SystemBackup_MMMDD_YYYY_HHMM_SS.zip</literal> (e.g
         System-Backup_Feb19_2013_2257_42.zip). Save the archive to another
         location outside the Enea Edge Management installation folder for
@@ -708,7 +711,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
         installation:</para>
 
         <programlisting>./install.sh \
-/opt/ems Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz \
+/opt/ems Enea_Edge_Management_&lt;version&gt;-build&lt;build_number&gt;.tar.gz \
 SystemBackup_MMMDD_YYYY_HHMM_SS.zip</programlisting>
       </section>
     </section>
@@ -757,9 +760,10 @@ sdb       8:0    0    111.8G  0   disk
           <programlisting>sudo dd if=./enea-edge-runtime-&lt;machine&gt;.hddimg \
 of=/dev/sdb bs=4M conv=fsync</programlisting>
 
-          <para>Where <filename>enea-edge-runtime-&lt;machine&gt;.hddimg</filename> is
-          the <filename>.hddimg</filename> file and <literal>sdb</literal> is
-          the assigned USB device name.</para>
+          <para>Where
+          <filename>enea-edge-runtime-&lt;machine&gt;.hddimg</filename> is the
+          <filename>.hddimg</filename> file and <literal>sdb</literal> is the
+          assigned USB device name.</para>
         </listitem>
       </orderedlist>
     </section>
@@ -1252,4 +1256,4 @@ of=/dev/sdb bs=4M conv=fsync</programlisting>
       </note>
     </section>
   </section>
-</chapter>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-edge-getting-started/doc/log_collector.xml b/doc/book-enea-edge-getting-started/doc/log_collector.xml
index 1148dc2..d7d99dd 100644
--- a/doc/book-enea-edge-getting-started/doc/log_collector.xml
+++ b/doc/book-enea-edge-getting-started/doc/log_collector.xml
@@ -341,7 +341,7 @@
       collected uCPE device logs to the support team provides important
       information for troubleshooting (especially in cases of connectivity
       issues with the uCPE device and error popups).</para>
-
+          
       <para>Enea Edge Management log files are located in
       <filename>application/logs/</filename> in the Enea Edge Management
       application's installation folder
@@ -358,7 +358,7 @@
 
         <listitem>
           <para>Select the desired log file
-          (<filename>ucpemanager.log</filename> or
+          (<filename>EneaEdgeManagement.log</filename> or
           <filename>watchdog.log</filename>) and press the <emphasis
           role="bold">Download</emphasis> button.</para>
         </listitem>
diff --git a/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml b/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
index ac2ebb6..e213a0f 100644
--- a/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
+++ b/doc/book-enea-edge-getting-started/doc/upgrade_ena.xml
@@ -37,7 +37,7 @@
         Management installation:</para>
 
         <programlisting>./upgrade.sh /opt/ems \
-Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</programlisting>
+Enea_Edge_Management_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</programlisting>
       </listitem>
     </orderedlist>
 
@@ -52,7 +52,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
       <listitem>
         <para>Create a compressed file of the <literal>ucpemanager</literal>
         application folder
-        (<filename>ucpemanager-Back-up-YYYYddMMHHmm.tar.gz</filename>), which
+        (<filename>EneaEdgeManagement-Backup-YYYYddMMHHmm.tar.gz</filename>), which
         contains a snapshot of the existing installation in the
         <literal>&lt;uCPEM-installerdir&gt;/dist</literal> directory.</para>
 
@@ -109,7 +109,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
 
         <listitem>
           <para>Copy the snapshot file
-          (<filename>ucpemanager-Backup-YYYYddMMHHmm.tar.gz</filename>)
+          (<filename>EneaEdgeManagement-Backup-YYYYddMMHHmm.tar.gz</filename>)
           created during a previous Enea Edge Management Upgrade or Enea Edge
           Management Uninstall Operation into the
           <literal>&lt;uCPEM-installerdir&gt;/dist</literal> directory.</para>
@@ -124,7 +124,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
           <literal>/opt/ems</literal> to the correct location of the Enea Edge
           Management installation:</para>
 
-          <programlisting>./restore.sh /opt/ems ucpemanager-Backup-YYYYddMMHHmm.tar.gz</programlisting>
+          <programlisting>./restore.sh /opt/ems EneaEdgeManagement-Backup-YYYYddMMHHmm.tar.gz</programlisting>
         </listitem>
       </orderedlist>
 
@@ -186,7 +186,7 @@ Enea_NFV_Access_uCPEManager_&lt;version&gt;-build&lt;build_number&gt;.tar.gz</pr
         <listitem>
           <para>Create a compressed file of the <literal>ucpemanager</literal>
           application folder:
-          <filename>ucpemanager-Back-up-YYYYddMMHHmm.tar.gz</filename>, which
+          <filename>EneaEdgeManagement-Backup-YYYYddMMHHmm.tar.gz</filename>, which
           contains a snapshot of the existing installation and functions as a
           restore point.</para>
 
diff --git a/doc/book-enea-edge-release-info/doc/about_release.xml b/doc/book-enea-edge-release-info/doc/about_release.xml
index 349c955..3cc854e 100644
--- a/doc/book-enea-edge-release-info/doc/about_release.xml
+++ b/doc/book-enea-edge-release-info/doc/about_release.xml
@@ -12,9 +12,9 @@
     private or public cloud.</para>
 
   <para>The Enea Edge <xi:include
-  href="../../s_doceneacommon/doc/eltf_params_updated.xml"
+  href="../../eltf_params_updated.xml"
   xmlns:xi="http://www.w3.org/2001/XInclude"
-  xpointer="element(EneaLinux_REL_VER/1)" /> Release includes new features, 
+  xpointer="element(EneaEdge_REL_VER/1)" /> Release includes new features, 
     optimizations, corrections, and updates to the user documentation.. 
     A list of major new features and improvements can be found in  
     <xref linkend="relinfo-changes-other">Section 2.1 New Features and Improvements</xref>.</para>
@@ -103,7 +103,7 @@
   it is in the beginning. The subtitles shall have the directory name of the
   target in the manifest.</remark>
 
-  <xi:include href="../../s_doceneacommon/doc/eltf_params_updated.xml"
+  <xi:include href="../../eltf_params_updated.xml"
               xmlns:xi="http://www.w3.org/2001/XInclude"
               xpointer="element(eltf-target-tables-section)" />
 
@@ -164,25 +164,4 @@
       </listitem>
     </itemizedlist>
   </section>
-
-  <section id="release-browsers">
-    <title>Supported Web Browsers</title>
-
-    <para>The current release supports using the following web
-    browsers:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>Google Chrome (tested with version 89).</para>
-      </listitem>
-
-      <listitem>
-        <para>Mozilla Firefox (tested with version 87).</para>
-      </listitem>
-
-      <listitem>
-        <para>Microsoft Edge (tested with version 89).</para>
-      </listitem>
-    </itemizedlist>
-  </section>
 </chapter>
\ No newline at end of file
diff --git a/doc/eltf_params_template.xml b/doc/eltf_params_template.xml
new file mode 100644
index 0000000..8a05079
--- /dev/null
+++ b/doc/eltf_params_template.xml
@@ -0,0 +1,151 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="eltf_created_params">
+  <title>File with Parameters in the Book Auto-updated by ELFT</title>
+
+  <note>
+    <para>See the <emphasis
+    role="bold">eltf_params_updated_template_howto_use.txt</emphasis> text
+    file for description of how to create the final <emphasis
+    role="bold">eltf_params_updated.xml</emphasis> from this template and for
+    all <emphasis role="bold">REQUIREMENTS</emphasis>. Use the command
+    "<emphasis role="bold">make eltf</emphasis>" to extract a full list of all
+    ELTF variables, which always begins with ELTF_ and don't only rely on the
+    howto text file list! The plan is that ELTF will auto-update this when
+    needed.</para>
+  </note>
+
+  <section id="host_prereq">
+    <title>Common Parameters</title>
+
+    <bridgehead>A programlisting, ID
+    "eltf-prereq-apt-get-commands-host"</bridgehead>
+
+    <para id="eltf-prereq-apt-get-commands-host"><programlisting>ELTF_PL_HOST_PREREQ</programlisting></para>
+
+    <bridgehead>A programlisting, ID
+    "eltf-getting-repo-install-command"</bridgehead>
+
+    <para id="eltf-getting-repo-install-command"><programlisting>ELTF_PL_GET_REPO</programlisting></para>
+
+    <bridgehead>Several phrase elements, various IDs. Ensure EL_REL_VER is
+    correct also compared to the "previous" REL VER in pardoc-distro.xml
+    "prev_baseline".</bridgehead>
+
+    <para id="EneaEdge_REL_VER"><phrase>ELTF_EL_REL_VER</phrase></para>
+
+    <para id="Yocto_VER"><phrase>ELTF_YOCTO_VER</phrase></para>
+
+    <para id="Yocto_NAME"><phrase>ELTF_YOCTO_NAME</phrase></para>
+
+    <para id="ULINK_YOCTO_PROJECT_DOWNLOAD"><ulink
+    url="ELTF_YOCTO_PROJ_DOWNLOAD_URL">ELTF_YOCTO_PROJ_DOWNLOAD_TXTURL</ulink></para>
+
+    <para id="ULINK_ENEA_LINUX_URL"><ulink
+    url="ELTF_EL_DOWNLOAD_URL">ELTF_EL_DOWNLOAD_TXTURL</ulink></para>
+
+    <bridgehead>A programlisting, ID "eltf-repo-cloning-enea-linux". Use
+    $MACHINE/default.xml as parameter, where MACHINE is one of the target
+    directory names in the manifest.</bridgehead>
+
+    <para id="eltf-repo-cloning-enea-linux"><programlisting>ELTF_PL_CLONE_W_REPO</programlisting></para>
+
+    <bridgehead>A table with ONE row, only the row with ID
+    "eltf-eclipse-version-row" is included in the book. MANUALLY BOTH in the
+    template.xml and in the updated.xml, set condition hidden on the
+    &lt;row&gt;, if eclipse is not in the release.</bridgehead>
+
+    <informaltable>
+      <tgroup cols="1">
+        <tbody>
+          <row id="eltf-eclipse-version-row">
+            <entry>Eclipse version ELTF_ECLIPSE_VERSION plus command line
+            development tools are included in this Enea Linux release.</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+
+    <bridgehead>Below is one big section with title "Supported Targets with
+    Parameters". The entire section is included completely in the book via ID
+    "eltf-target-tables-section" and shall be LAST in the template. The
+    template contains ONE target subsection. COPY/APPEND it, if multiple
+    targets exist in the release and optionally add rows with additional
+    target parameters in each target subsection table.</bridgehead>
+  </section>
+
+  <section id="eltf-target-tables-section">
+    <title>Supported Targets with Parameters</title>
+
+    <para>The tables below describes the target(s) supported in this Enea
+    Linux release.</para>
+
+    <section id="eltf-target-table-ELTF_T_MANIFEST_DIR">
+      <title>MACHINE ELTF_T_MANIFEST_DIR - Information</title>
+
+      <para><informaltable>
+          <tgroup cols="2">
+            <colspec colwidth="6*" />
+
+            <colspec colwidth="9*" />
+
+            <tbody>
+              <row>
+                <entry>Target official name</entry>
+
+                <entry>ELTF_T_NAME</entry>
+              </row>
+
+              <row>
+                <entry>Architecture and Description</entry>
+
+                <entry>ELTF_T_ARC_DESC</entry>
+              </row>
+
+              <row>
+                <entry>Link to target datasheet</entry>
+
+                <entry>See <ulink
+                url="ELTF_T_DS_URL">ELTF_T_DS_TXTURL</ulink></entry>
+              </row>
+
+              <row>
+                <entry>Poky version</entry>
+
+                <entry>ELTF_T_POKY_VER</entry>
+              </row>
+
+              <row>
+                <entry>GCC version</entry>
+
+                <entry>ELTF_T_GCC_VER</entry>
+              </row>
+
+              <row>
+                <entry>Linux Kernel Version</entry>
+
+                <entry>ELTF_T_KERN_VER</entry>
+              </row>
+
+              <row>
+                <entry>Supported Drivers</entry>
+
+                <entry>ELTF_T_DRIVERS</entry>
+              </row>
+
+              <row>
+                <entry>Enea rpm folder for downloading RPM packages for this
+                target</entry>
+
+                <entry><ulink
+                url="ELTF_T_EL_RPM_URL">ELTF_T_EL_RPM_TXTURL</ulink></entry>
+              </row>
+            </tbody>
+          </tgroup>
+        </informaltable></para>
+    </section>
+
+    <!-- ELTFADD_MORE_TARGET_SECTIONS_BELOW_IF_NEEDED -->
+  </section>
+</section>
\ No newline at end of file
diff --git a/doc/eltf_params_updated.xml b/doc/eltf_params_updated.xml
new file mode 100644
index 0000000..f5f3f7d
--- /dev/null
+++ b/doc/eltf_params_updated.xml
@@ -0,0 +1,173 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE section PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<section id="eltf_created_params">
+  <title>File with Parameters in the Book Auto-updated by ELFT</title>
+
+  <section id="host_prereq">
+    <title>Common Parameters</title>
+
+    <bridgehead>Several phrase elements, various IDs. Ensure EL_REL_VER is
+    correct also compared to the "previous" REL VER in pardoc-distro.xml
+    "prev_baseline".</bridgehead>
+    
+    <para id="EneaEdge_REL_VER"><phrase>2.5.0</phrase></para>
+
+    <para id="ENA_BUILD_VER"><phrase>1</phrase></para>
+
+    <bridgehead>Below is one big section with title "Supported Processor with
+    Parameters". The entire section is included completely in the book via ID
+    "eltf-target-tables-section" and shall be LAST in the template. The
+    template contains ONE target subsection. COPY/APPEND it, if multiple
+    targets exist in the release and optionally add rows with additional
+    target parameters in each target subsection table.</bridgehead>
+  </section>
+
+  <section id="eltf-target-tables-section">
+    <title>Reference Processors with Parameters</title>
+
+    <para>The table(s) below describes the tested processors for this Enea
+    Edge release.</para>
+
+    <table>
+      <title>Processor Product Family Information - Intel Xeon D-1500</title>
+
+      <tgroup cols="2">
+        <colspec align="left" />
+
+        <thead>
+          <row>
+            <entry align="center">Component</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry>Processor official product family name</entry>
+
+            <entry>Intel Xeon D-1500 (Broadwell)</entry>
+          </row>
+
+          <row>
+            <entry>Architecture and Description</entry>
+
+            <entry>x86-64</entry>
+          </row>
+
+          <row>
+            <entry>Link to processor datasheet</entry>
+
+            <entry><ulink
+            url="https://www.intel.com/content/www/us/en/processors/xeon/xeon-d-1500-datasheet-vol-1.html">Intel's
+            datasheet</ulink></entry>
+          </row>
+
+          <row condition="hidden">
+            <entry>Supported Drivers</entry>
+
+            <entry>Ethernet, RTC, UART</entry>
+          </row>
+
+          <row>
+            <entry>Tested Whiteboxes</entry>
+
+            <entrytbl cols="1">
+              <tbody>
+                <row>
+                  <entry>Supermicro X10SDV-4C-TLN2F (Intel Xeon
+                  D-1521)</entry>
+                </row>
+
+                <row>
+                  <entry>Kontron ME1100 (Intel Xeon D-1548).</entry>
+                </row>
+              </tbody>
+            </entrytbl>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+
+    <table>
+      <title>Processor Product Family Information - Intel Atom C3000</title>
+
+      <tgroup cols="2">
+        <colspec align="left" />
+
+        <thead>
+          <row>
+            <entry align="center">Component</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry>Processor official product family name</entry>
+
+            <entry>Intel Atom C3000 (Denverton)</entry>
+          </row>
+
+          <row>
+            <entry>Architecture and Description</entry>
+
+            <entry>x86-64</entry>
+          </row>
+
+          <row>
+            <entry>Link to the processor datasheet</entry>
+
+            <entry><ulink
+            url="https://www.intel.com/content/www/us/en/products/docs/processors/atom/c-series/c3000-family-datasheet.html">Intel's
+            datasheet</ulink></entry>
+          </row>
+
+          <row condition="hidden">
+            <entry>Supported Drivers</entry>
+
+            <entry>Ethernet, RTC, UART</entry>
+          </row>
+
+          <row>
+            <entry>Tested Whiteboxes</entry>
+
+            <entrytbl cols="1">
+              <tbody>
+                <row>
+                  <entry>Dell EMC Networking VEP1445 (Intel Atom
+                  C3758)</entry>
+                </row>
+
+                <row>
+                  <entry>Advantech FWA-1012VCR-4CA1S (Intel Atom
+                  C3558)</entry>
+                </row>
+
+                <row>
+                  <entry>Advantech FWA-1112VCL-2CA1S (Intel Atom
+                  C3558-4C)</entry>
+                </row>
+
+                <row>
+                  <entry>Supermicro A2SDi-TP8F (Intel Atom C3858)</entry>
+                </row>
+
+                <row>
+                  <entry>Supermicro SuperServer 5019A-12TN4 (Intel Atom
+                  C3850)</entry>
+                </row>
+
+                <row>
+                  <entry>Silicom C3000 (Intel Atom 3558)</entry>
+                </row>
+              </tbody>
+            </entrytbl>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+  </section>
+</section>
\ No newline at end of file
diff --git a/doc/eltf_params_updated_template_how_to_use.txt b/doc/eltf_params_updated_template_how_to_use.txt
new file mode 100644
index 0000000..97b07aa
--- /dev/null
+++ b/doc/eltf_params_updated_template_how_to_use.txt
@@ -0,0 +1,320 @@
+eltf_params_template_updated_howto_use.txt
+
+This is a way to collect all parameters for an Enea Edge release
+in one parameter file, easy to automatically update by ELTF regularly.
+
+NOTE: Both the release info AND the open source books use parameters from
+      here, but the XML file is inside the release info book directory.
+
+NOTE: The manifest_conf.mk, or overridden by the environment variable
+      MANIFESTHASH, contains the full tag (or hashvalue) for downloading
+      the manifest when the books are built. The list of target
+      directories are fetched from the manifest into the book.
+      The eltf_params_updates.xml can all the time contain
+      the final next complete tag e.g. refs/tags/EL6 or similar
+      in the ELTF_PL_CLONE_W_REPO parameter command lines.
+
+The ordinary book XML files use xi:include statements to include elements
+from this parameter file. The book XML files can thus be manually edited.
+Before editing, you must run "make init".
+Any other text in the template or updated.xml file, outside the parts that
+are included in the book, are not used but still all must be correct
+DocBook XML files.
+
+ELTF work:
+ template => ELTF replaces ALL ELTF_xxx variables => updated XML file
+    => push to git only if changed
+
+
+eltf_params_template.xml  (in git)
+   File used by ELTF to autocreate/update the real parameter
+   file eltf_params_updated.xml.
+
+eltf_params_updated.xml  (in git)
+   Real parameter file where ELTF has replaced all ELTF_xx variables with
+   strings, in several cases with multiline strings.
+   No spaces or linefeed allowed in beginning or end of the variable values!
+
+
+xi:include: Each parameter is xi:include'ed in various book files, using
+   the IDs existing in the parameter files.
+   In most cases the 1:st element inside an element with an ID is included
+   using a format like eltf-prereq-apt-get-commands-host/1.
+   In very few cases the element with the ID is included in the book, one
+   example is the target section which has an ID, but which contains
+   multiple subsections, one per target.
+   All IDs in a book must be unique.
+
+DocBook XML: All XML files must be correct DocBook XML files.
+
+Do NOT edit/save the real *updated.xml file with XMLmind to avoid changes
+   not done by ELTF. But it is OK to open the real file in XMLmind to
+   check that the format is correct.
+
+ELTF should autocreate a temporary "real" file but only replace
+   and push the eltf_params_updated.xml if it is changed.
+
+
+make eltf
+   This lists all ELTF_xxx variables and some rules how to treat them
+
+DocBook Format: All elements - rules:
+   Several strict generic XML rules apply for all strings:
+    1. No TABs allowed or any other control chr than "linefeed"
+    2. Only 7-bit ASCII
+    3. Any < > & must be converted to &lt; &gt; and &amp;
+       Similar for any other non-7-bit-ASCII but avoid those!
+    4. No leading spaces or linefeeds when replacing the ELTF_* variable
+    5. No trailing spaces or linefeeds when replacing the ELTF_* variable
+    6. Note: Keep existing spaces before/efter ELTF_* in a few cases.
+
+DocBook Format: <programlisting> - rules: ELTF*PL* variables
+   Several strict rules apply for the multiline string in programlisting
+   in addition to the general XML rules above:
+    7. Max line length < 80 char
+    8. Use backslash (\) to break longer lines
+    9. Use spaces (e.g. 4) to indent continuation lines in programlistings
+   10. No trailing spaces on any line
+   11. No spaces or linefeed immediately after leading <programlisting>
+   12. No spaces or linefeed before trailing </programlisting>
+
+DocBook Format: <ulink> - rules: ELTF_*URL* variables
+   13. ELTF_*URL and corresponding ELTF_*TXTURL shall be identical strings
+   14. Only if the URL is extremely long, the TXTURL can be a separate string
+
+Each target has one section with target parameters:
+       <section id="eltf-target-table-ELTF_T_MANIFEST_DIR">
+        <title>MACHINE ELTF_T_MANIFEST_DIR - Information</title>
+          ..... with many ELTF_ variables ....
+       </section>
+
+   15. If there is only one target. ELTF just replaces ELTF parameters
+
+   16. It there are multiple targets. ELTF copies the section and appends the
+       section the required number of times.
+       Each section ID will become unique: eltf-target-table-ELTF_T_MANIFEST_DIR
+       Each section title will become unique
+
+Tables with target parameters in each target section:
+   17. It is possible for ELTF to append more rows with one parameter each
+       to these tables, because the entire tables are included in the book
+
+Special - NOT YET READY DEFINED how to handle the optionally included
+   Eclipse and its version, but this is a first suggestion:
+   18. Just now ELTF can define ELFT_ECLIPSE_VERSION as a full string
+       with both version number and name,
+   19. MANUALLY if Eclipse is NOT included in the release,
+       the release manager should manually set condition="hidden" on
+       the entire section in the book XML about Eclipse
+
+
+
+BELOW WE TRY TO EXPLAIN EACH ELTF_* variable, but always check with make eltf
+if there are more new variables, missing in this description file.
+
+_____________________________________________________________________________
+ELTF_PL_HOST_PREREQ       Multiline list of host prerequisites, e.g. commands
+                          like sudo apt-get install xxxx or similar.
+                          First line = comment with the complete host name!
+                          It is possible to include multiple hosts by just
+                          adding an empty line, comment with host name, etc.
+                          xi:include eltf-prereq-apt-get-commands-host/1
+                          This is a <programlisting>...</programlisting>
+                          Example:
+# Host Ubuntu 14.04.5 LTS 64bit
+sudo apt-get update
+sudo apt-get install sed wget subversion git-core coreutils unzip texi2html \
+   texinfo libsdl1.2-dev docbook-utils fop gawk python-pysqlite2 diffstat \
+   make gcc build-essential xsltproc g++ desktop-file-utils chrpath  \
+   libgl1-mesa-dev libglu1-mesa-dev autoconf automake groff libtool xterm \
+   libxml-parser-perl
+
+_____________________________________________________________________________
+ELTF_PL_GET_REPO          Multiline commands to download the repo tool
+                          xi:include eltf-getting-repo-install-command/1
+                          This is a <programlisting>...</programlisting>
+                          Example:
+mkdir -p ~/bin
+curl https://storage.googleapis.com/git-repo-downloads/repo > ~/bin/repo
+chmod a+x ~/bin/repo
+export PATH=~/bin:$PATH
+
+_____________________________________________________________________________
+ELTF_EL_REL_VER           General parameter string: The version of this Enea
+                          NFV Access release. Major version and optional .Minor
+                          Typically created from MAJOR and MINOR in enea.conf
+                          MINOR in enea.conf is empty or contains a dot+minor
+                          xi_include EneaEdge_REL_VER/1
+                          This is a <phrase>X.x</phrase> used in many places.
+                          Examples:
+6
+  or
+6.1
+
+_____________________________________________________________________________
+ELTF_YOCTO_VER            General parameter string: Yocto version, created
+                          from DISTRO in poky.ent
+                          xi:include Yocto_VER/1
+                          This is a <phrase>X.x</phrase> used in many places.
+                          Example:
+2.1
+
+_____________________________________________________________________________
+ELTF_YOCTO_NAME           General parameter string: Yocto name (branch), created
+                          from DISTRO_NAME_NO_CAP in poky.ent
+                          xi:include Yocto_NAME/1
+                          This is a <phrase>X.x</phrase> used in many places.
+                          Example:
+krogoth
+
+_____________________________________________________________________________
+ELTF_YOCTO_PROJ_DOWNLOAD_TXTURL  General parameters. These two are IDENTICAL
+ELTF_YOCTO_PROJ_DOWNLOAD_URL     strings with correct Yocto version string
+                                 at the end, typically without "dot".
+                          xi:include ULINK_YOCTO_PROJECT_DOWNLOAD/1
+                          This is an <ulink url="...">...</ulink>
+                          Example:
+http://www.yoctoproject.org/downloads/core/krogoth/21
+
+_____________________________________________________________________________
+ELTF_EL_DOWNLOAD_TXTURL   General parameters. These two are IDENTICAL strings
+ELTF_EL_DOWNLOAD_URL      and shall be the http:/..... address where
+                          Enea NFV Access can be downloaded
+                          Often containing same version as in ELTF_EL_REL_VER
+                          xi:include ULINK_ENEA_LINUX_URL/1
+                          This is an <ulink url="...">...</ulink>
+                          Example:
+http://linux.enea.com/6
+
+_____________________________________________________________________________
+ELTF_PL_CLONE_W_REPO      Multiline commands to run repo to clone everything.
+                          Use the variable $MACHINE/default.xml (the text in
+                          the book will list the avaiable values of MACHINE,
+                          taken from the manifest repository)
+                          xi:include eltf-repo-cloning-enea-linux/1
+                          This is a <programlisting>...</programlisting>
+                          Example:
+mkdir enea-linux
+cd enea-linux
+repo init -u git@git.enea.com:linux/manifests/el_manifests-virtualization.git \
+    -b refs/tags/EL6 -m $MACHINE/default.xml
+repo sync
+
+_____________________________________________________________________________
+ELTF_ECLIPSE_VERSION      Optional general parameter string.
+                          NOT YET READY DEFINED
+                          Just now a release manage must manually set
+                          condition="hidden" on the Eclipse section,
+                          if Eclipse is not included in the release.
+                          ELTF just replaces ELTF_ECLIPSE_VERSION with a full
+                          string with "X.Y (name)"
+                          It includes the ID and can only be ONCE in the book.
+                          xi:include eltf-eclipse-version-row
+                          Example.
+4.5 (Mars)
+
+
+_____________________________________________________________________________
+ELTF_T_*                  All these are in each target (MACHINE) and ELTF
+                          must separately replace them with strings for
+                          each target
+                          NOTE: All (except the MANIFEST_DIR) are in rows
+                                in a table and ELTF can select to append
+                                more parameters by adding more rows
+
+_____________________________________________________________________________
+ELTF_T_MANIFEST_DIR       This happens to be in two places. Must be exactly
+ELTF_T_MANIFEST_DIR       the directory name in the manifest, e.g. same
+                          as the MACHINE names in $MACHINE/default.xml.
+                          In book: a) Part of section ID
+                                   b) Part of section title
+                          Examples:
+p2041rgb
+  or
+ls1021aiot
+  or
+qemuarm
+
+_____________________________________________________________________________
+ELTF_T_NAME               Target specific: "Target Official Name"
+                          NOT same as the target directory name in most cases.
+                          In book: An <entry> element in a row
+                          Examples:
+P2041RGB
+  or
+LS1021a-IoT
+  or
+qemuarm
+
+_____________________________________________________________________________
+ELTF_T_ARC_DESC           Target specific: "Architecture and Description"
+                          It can be a short identification string or
+                          it can be a longer descriptive sentence.
+                          In book: An <entry> element in a row
+                          Examples:
+Power, e500mc
+  or
+ARM Cortex-A7
+
+_____________________________________________________________________________
+ELTF_T_DS_TXTURL          Target specific: "Link to target datasheet. These
+ELTF_T_DS_URL             two usually are IDENTICAL strings with correct
+                          hyperlink to the target's official datasheet.
+                          In book: an <ulink url="...">...</ulink>
+                          Only if the link is VERY LONG, the text part shall
+                          instead be a descriptive string (see 2:nd example).
+                          NOTE: Also here no spaces or line-feeds!
+                          Examples:
+url="http://wiki.qemu.org">http://wiki.qemu.org
+or
+url="http://www.nxp.com/products/microcontrollers-and-processors/arm-processors/qoriq-arm-processors/qoriq-ls1021a-iot-gateway-reference-design:LS1021A-IoT">link to NXP's datasheet
+
+_____________________________________________________________________________
+ELTF_T_POKY_VER           Target specific: "Poky version" created either
+                          from POKYVERSION in poky.ent
+                          or using a hashvalue with a leading string, in
+                          which case it may be different per target.
+                          In book: An <entry> in a row
+                          Examples:
+15.0.0
+or
+Git commit id: 75ca53211488a3e268037a44ee2a7ac5c7181bd2
+
+_____________________________________________________________________________
+ELTF_T_GCC_VER            Target specific: "GCC Version". Should be in poky
+                          but not easy to find among various parameters.
+                          ELTF would extract it from build logs building SDK
+                          and it is possibly different per target.
+                          In book: An <entry> in a row
+                          Example:
+5.3
+
+_____________________________________________________________________________
+ELTF_T_KERN_VER           Target specific: "Linux Kernel Version". Often
+                          different per target.
+                          In book: An <entry> in a row
+                          Example:
+3.12
+
+_____________________________________________________________________________
+ELTF_T_DRIVERS            Target specific: "Supported Drivers". This is a
+                          comma-separated list of driver names.
+                          ELTF should create the list in same order for each
+                          target, e.g. alphabetic migth be OK.
+                          In book: An <entry> in a row
+                          Example:
+Ethernet, I2C, SPI, PCI, USB, SD/SDHC/SDXC
+
+
+_____________________________________________________________________________
+ELTF_T_EL_RPM_TXTURL      Target specific: "Enea rpm folder for downloading
+ELTF_T_EL_RPM_URL         RPM packages for this target". These two are
+                          INDENTICAL strings with hyperlink to the web site
+                          at Enea where the customer can download RPMs
+                          Note: Often the ELFT_EL_REL_VER value and
+                                the ELTF_T_MANIFEST_DIR are used in the link.
+                          In book: an <ulink url="...">...</ulink>
+                          Example:
+url="https://linux.enea.com/6/ls1021aiot/rpm">https://linux.enea.com/6/ls1021aiot/rpm
+
+_____________________________________________________________________________