Added AF TH User Guide Outline + ch1&2 proofed.

Change-Id: Ie6ae43e02f30dd6bba6532b84d41c8d4a5e0bbf9

15 files changed, 1590 insertions, 1 deletions

diff --git a/doc/Makefile b/doc/Makefile
index fbc898e..2cf6e28 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -50,7 +50,7 @@ DOCBOOK_TO_BOOKDIR ?= yes
 DOCBOOK_CLEANTMP ?= yes
 
 #Components (books) in this subsystem. Now use all books found here
-COMPONENTS := book-enea-nfv-access-example-usecases book-enea-nfv-access-getting-started book-enea-nfv-access-open-source book-enea-nfv-access-release-info book-enea-nfv-access-vnf-onboarding-guide book-enea-nfv-access-reference-guide-intel
+COMPONENTS := book-enea-nfv-access-example-usecases book-enea-nfv-access-getting-started book-enea-nfv-access-open-source book-enea-nfv-access-release-info book-enea-nfv-access-vnf-onboarding-guide book-enea-nfv-access-reference-guide-intel book-enea-nfv-access-auto-fw-th-user-guide
 #  COMPONENTS += 
 #book-enea-linux-eclipse-open-source 
 #book-enea-nfv-access-dev-hardening-guide
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
new file mode 100644
index 0000000..53940eb
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/automation_framework_test_harness.xml
@@ -0,0 +1,107 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="auto_fw_test_harness">
+  <title>Automation Framework and Test Harness</title>
+
+  <section id="auto_fw">
+    <title>Automation Framework</title>
+
+    <para></para>
+        
+  <section id="python_testsuite">
+    <title>Python Unit-Test Suite</title>
+
+    <para></para>
+  </section>
+        
+  <section id="add_ucpe_device">
+    <title>Adding a uCPE Device</title>
+
+    <para></para>
+  </section>
+
+  <section id="remove_ucpe_device">
+    <title>Removing a uCPE Device</title>
+
+    <para></para>
+  </section>
+
+  <section id="wait_ucpe_device">
+    <title>Waiting a uCPE Device</title>
+
+    <para></para>
+  </section>
+
+  <section id="bind_ucpe_device">
+    <title>Bind a uCPE Device</title>
+
+    <para></para>
+  </section>
+
+  <section id="unbind_ucpe_device">
+    <title>Unbind a uCPE Device</title>
+
+    <para></para>
+  </section>
+  
+  <section id="create_ovs_net_bridge">
+    <title>Create an OVS Network Bridge</title>
+
+    <para></para>
+  </section>
+
+  <section id="delete_ovs_net_bridge">
+    <title>Delete an OVS Network Bridge</title>
+
+    <para></para>
+  </section>
+
+  <section id="onboard_vnf_bundle">
+    <title>Onboard a VNF Bundle</title>
+
+    <para></para>
+  </section>
+
+  <section id="onboard_vnf_image">
+    <title>Onboard a VNF Image</title>
+
+    <para></para>
+  </section>
+
+  <section id="offboard_vnf">
+    <title>Offboard a VNF</title>
+
+    <para></para>
+  </section>
+
+  <section id="instantiate_vnf">
+    <title>Instantiate a VNF</title>
+
+    <para></para>
+  </section>
+
+  <section id="control_vnf_inst">
+    <title>Control a VNF Instance</title>
+
+    <para></para>
+  </section>
+
+  <section id="destroy_vnf_inst">
+    <title>Destroy a VNF Instance</title>
+
+    <para></para>
+  </section>
+  </section>
+
+  <section id="test_harness">
+    <title>Test Harness</title>
+
+    <para></para>
+        
+  <section id="test_suites">
+    <title>Extending functionality - Test Suites</title>
+
+    <para></para>
+  </section>
+  
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml
new file mode 100644
index 0000000..c2b86f4
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/book.xml
@@ -0,0 +1,33 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
+<!ENTITY % local.common.attrib "xml:base CDATA #IMPLIED">
+]>
+<book id="book_enea_nfv_access_auto_fw_th_user_guide">
+  <title><trademark class="registered">Enea</trademark> NFV Access Automation Framework and Test Harness User Guide</title>
+
+  <subtitle>Release Version <xi:include href="eltf_params_updated.xml"
+  xmlns:xi="http://www.w3.org/2001/XInclude"
+  xpointer="element(EneaLinux_REL_VER/1)" /></subtitle>
+
+  <!-- OLINKDBPATH_USED_BY_XMLMIND ../../s_docbuild/olinkdb  -->
+
+  <xi:include href="../../s_docbuild/template/docsrc_common/bookinfo_userdoc.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="overview.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="getting_started.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="components.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="automation_framework_test_harness.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+                          
+  <xi:include href="troubleshooting_guide.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+</book>
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml
new file mode 100644
index 0000000..0f72709
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/components.xml
@@ -0,0 +1,34 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="components">
+  <title>Components</title>
+
+  <section id="enfva_solution">
+    <title>Enea NFV Access Solution</title>
+
+    <para></para>
+        
+          <section id="eucpe_manager">
+                <title>Enea uCPE Manager</title>
+
+                <para></para>
+          </section>
+          
+          <section id="ena_plat">
+                <title>Enea NFV Access</title>
+
+                <para></para>
+          </section>
+  </section>
+
+  <section id="automation">
+    <title>Automation Framework</title>
+
+    <para></para>
+  </section>
+  
+  <section id="harness">
+    <title>Test Harness</title>
+
+    <para></para>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/eltf_params_template.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/eltf_params_template.xml
new file mode 100644
index 0000000..eaa7ebd
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/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="EneaLinux_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 NFV Access 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
+    NFV Access 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/book-enea-nfv-access-auto-fw-th-user-guide/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/eltf_params_updated.xml
new file mode 100644
index 0000000..feabc9f
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/eltf_params_updated.xml
@@ -0,0 +1,286 @@
+<?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># Host Ubuntu 16.04 LTS 64bit
+sudo apt-get -y update
+sudo apt-get -y 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</programlisting></para>
+
+    <bridgehead>A programlisting, ID
+    "eltf-getting-repo-install-command"</bridgehead>
+
+    <para id="eltf-getting-repo-install-command"><programlisting>mkdir -p ~/bin
+curl https://storage.googleapis.com/git-repo-downloads/repo &gt; ~/bin/repo
+chmod a+x ~/bin/repo
+export PATH=~/bin:$PATH</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="EneaLinux_REL_VER"><phrase>2.2.1</phrase></para>
+
+    <para id="Yocto_VER"><phrase>2.4</phrase></para>
+
+    <para id="Yocto_NAME"><phrase>rocko</phrase></para>
+
+    <para id="ULINK_YOCTO_PROJECT_DOWNLOAD"><ulink
+    url="http://www.yoctoproject.org/downloads">http://www.yoctoproject.org/downloads</ulink></para>
+
+    <para id="ULINK_ENEA_LINUX_URL"><ulink
+    url="https://linux.enea.com/6">https://linux.enea.com/6</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>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</programlisting></para>
+
+    <bridgehead>A table with ONE row, only the row with ID
+    "eltf-eclipse-version-row" is included in the book. MANUALLY in book, set
+    condition hidden if eclipse is not in the release. Do this both in
+    template.xml and updated.xml.</bridgehead>
+
+    <informaltable>
+      <tgroup cols="1">
+        <tbody>
+          <row condition="hidden" id="eltf-eclipse-version-row">
+            <entry>Eclipse version 4.3 (Mars) plus command line development
+            tools are included in this Enea NFV Access 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 Reference Boards with Parameters</title>
+
+    <para>The table(s) below describes the target(s) supported in this Enea
+    NFV Access release.</para>
+
+    <table>
+      <title>MACHINE Information Intel Xeon D</title>
+
+      <tgroup cols="2">
+        <colspec align="center" />
+
+        <thead>
+          <row>
+            <entry align="center">Component</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry align="left">Target official name</entry>
+
+            <entry>Intel Xeon D</entry>
+          </row>
+
+          <row>
+            <entry align="left">Architecture and Description</entry>
+
+            <entry>x86-64</entry>
+          </row>
+
+          <row>
+            <entry align="left">Link to target 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>
+            <entry align="left">Poky version</entry>
+
+            <entry>Git-commit-id:
+            7e7ee662f5dea4d090293045f7498093322802cc</entry>
+          </row>
+
+          <row>
+            <entry align="left">GCC version</entry>
+
+            <entry>7.3</entry>
+          </row>
+
+          <row>
+            <entry align="left">Linux Kernel Version</entry>
+
+            <entry>4.14</entry>
+          </row>
+
+          <row condition="hidden">
+            <entry align="left">Supported Drivers</entry>
+
+            <entry>Ethernet, RTC, UART</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+
+    <table>
+      <title>MACHINE Information Intel Atom C3000</title>
+
+      <tgroup cols="2">
+        <colspec align="center" />
+
+        <thead>
+          <row>
+            <entry align="center">Component</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry align="left">Target official name</entry>
+
+            <entry>Intel Atom C3000</entry>
+          </row>
+
+          <row>
+            <entry align="left">Architecture and Description</entry>
+
+            <entry>x86-64</entry>
+          </row>
+
+          <row>
+            <entry align="left">Link to target 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>
+            <entry align="left">Poky version</entry>
+
+            <entry>Git-commit-id:
+            7e7ee662f5dea4d090293045f7498093322802cc</entry>
+          </row>
+
+          <row>
+            <entry align="left">GCC version</entry>
+
+            <entry>7.3</entry>
+          </row>
+
+          <row>
+            <entry align="left">Linux Kernel Version</entry>
+
+            <entry>4.14</entry>
+          </row>
+
+          <row condition="hidden">
+            <entry align="left">Supported Drivers</entry>
+
+            <entry>Ethernet, RTC, UART</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+
+    <table condition="arm">
+      <title>MACHINE Information</title>
+
+      <tgroup cols="2">
+        <colspec align="center" />
+
+        <thead>
+          <row>
+            <entry align="center">Component</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry align="left">Target official name</entry>
+
+            <entry>OCTEON TX™ cn8304</entry>
+          </row>
+
+          <row>
+            <entry align="left">Architecture and Description</entry>
+
+            <entry>arm64</entry>
+          </row>
+
+          <row>
+            <entry align="left">Link to target datasheet</entry>
+
+            <entry><ulink
+            url="http://www.cavium.com/OCTEON-TX-CN82XX-83XX.html">OCTEON
+            TX™ cn8304 datasheet</ulink></entry>
+          </row>
+
+          <row>
+            <entry align="left">Poky version</entry>
+
+            <entry>Git-commit-id:
+            f01b909a266498853e6b3f10e6b39f2d95148129</entry>
+          </row>
+
+          <row>
+            <entry align="left">GCC version</entry>
+
+            <entry>5.3<remark>FIXME</remark></entry>
+          </row>
+
+          <row>
+            <entry align="left">Linux Kernel Version</entry>
+
+            <entry>3.12<remark>FIXME</remark></entry>
+          </row>
+
+          <row condition="hidden">
+            <entry align="left">Supported Drivers</entry>
+
+            <entry>Ethernet, RTC, UART</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+  </section>
+</section>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/eltf_params_updated_template_how_to_use.txt b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/eltf_params_updated_template_how_to_use.txt
new file mode 100755
index 0000000..62e5d02
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/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 NFV Access 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 EneaLinux_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
+
+_____________________________________________________________________________
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
new file mode 100644
index 0000000..b7ff8f4
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml
@@ -0,0 +1,223 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="getting_started">
+  <title>Getting Started with the Automation Framework and Test
+  Harness</title>
+
+  <section id="prerequisites">
+    <title>Prerequisites</title>
+
+    <para>For installation of the Automation Framework and Test Harness a
+    CentOS 7 host machine is needed with support for:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Python 2.7</para>
+      </listitem>
+
+      <listitem>
+        <para>EPEL Repository installed:<programlisting>sudo yum install epel-release</programlisting></para>
+      </listitem>
+
+      <listitem>
+        <para>PIP package manager installed: <programlisting>sudo yum -y install python-pip</programlisting></para>
+      </listitem>
+
+      <listitem>
+        <para>Virtualenv tool installed: <programlisting>sudo pip install virtualenv</programlisting></para>
+      </listitem>
+    </itemizedlist>
+
+    <note>
+      <para>The Automation Framework and Test Harness installation may be done
+      on the same machine used for uCPE Manager installation, although this is
+      not encouraged. For more details see <link linkend="automation">chapter
+      3.2</link>.</para>
+    </note>
+  </section>
+
+  <section id="envrion">
+    <title>Environment</title>
+
+    <para><figure>
+        <title>Lab setup overview for Basic Setup</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center"
+                       fileref="images/environment_basicsetup.png" scale="35" />
+          </imageobject>
+        </mediaobject>
+      </figure>The following enviroment setup is needed for running all the
+    tests defined in the Enea NFV Access System Test Specification
+    document:</para>
+
+    <para><emphasis role="bold">Lab Network</emphasis><itemizedlist>
+        <listitem>
+          <para>DHCP enabled.</para>
+        </listitem>
+
+        <listitem>
+          <para>Internet Connectivity.</para>
+        </listitem>
+      </itemizedlist></para>
+
+    <para><emphasis role="bold">uCPE Manager host</emphasis></para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Running CentOS 7.</para>
+      </listitem>
+
+      <listitem>
+        <para>Connected to Lab Network.</para>
+      </listitem>
+
+      <listitem>
+        <para>uCPE Manager installed.</para>
+
+        <note>
+          <para>For details on how to install the uCPE Manager, see "Getting
+          Started with Enea uCPE Manager" from the Enea NFV Access Getting
+          Started manual.</para>
+        </note>
+      </listitem>
+    </itemizedlist>
+
+    <para><emphasis role="bold">1<superscript>st</superscript> Intel Whitebox
+    target device</emphasis><itemizedlist>
+        <listitem>
+          <para>Minimum 4 Physical Network Devices.</para>
+        </listitem>
+
+        <listitem>
+          <para>4GB RAM and 4 cores (Intel C3000 or Xeon D).</para>
+        </listitem>
+
+        <listitem>
+          <para>2 Physical connections to Lab Network.</para>
+        </listitem>
+
+        <listitem>
+          <para>Enea NFV Access installed.</para>
+
+          <note>
+            <para>For information on how to install Enea NFV Access<remark>the
+            solution or the platform?</remark>, refer to "Getting Started with
+            Enea NFV Access" from the Enea NFV Access Getting Started
+            manual.</para>
+          </note>
+        </listitem>
+      </itemizedlist><figure>
+        <title>Lab setup overview for ChainedVNFsService Setup</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center"
+                       fileref="images/ChainedVNFsService_setup.png"
+                       scale="40" />
+          </imageobject>
+        </mediaobject>
+      </figure></para>
+
+    <para><emphasis role="bold">Changes to 1st Intel Whitebox target
+    device</emphasis></para>
+
+    <itemizedlist>
+      <listitem>
+        <para>16GB RAM and 8 cores (Intel C3000 or Xeon D).</para>
+      </listitem>
+
+      <listitem>
+        <para>1 Physical connection back to back with the 2nd Intel Whitebox
+        target device.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para><emphasis role="bold">2<superscript>nd</superscript> Intel Whitebox
+    target device</emphasis><itemizedlist>
+        <listitem>
+          <para>Minimum 4 Physical Network Devices.</para>
+        </listitem>
+
+        <listitem>
+          <para>16GB RAM and 8 cores (Intel C3000 or Xeon D).</para>
+        </listitem>
+
+        <listitem>
+          <para>2 Physical connections to Lab Network.</para>
+        </listitem>
+
+        <listitem>
+          <para>1 Physical connection back to back with the
+          1<superscript>st</superscript> Intel Whitebox target device.</para>
+        </listitem>
+
+        <listitem>
+          <para>Enea NFV Access installed.</para>
+
+          <note>
+            <para>For information on how to install Enea NFV Access<remark>the
+            solution or the platform?</remark>, refer to "Getting Started with
+            Enea NFV Access" from the Enea NFV Access Getting Started
+            manual.</para>
+          </note>
+        </listitem>
+      </itemizedlist></para>
+  </section>
+
+  <section id="initial_setup">
+    <title>Installation and Initial Setup</title>
+
+    <para>Download <filename>nfvaccess22_af-th.zip</filename> from the Enea
+    Portal and unzip it on the a supported host machine. Henceforth, the
+    directory in which the ZIP archive has been unpacked will be denoted as
+    <literal>&lt;AF-TH-installdir&gt;</literal>.</para>
+
+    <para>Enter the <literal>&lt;AF-TH-install-dir&gt;</literal> directory and
+    run the <filename>setup_env.sh</filename> script to do the initial setup
+    of the Test Harness environment: <filename>source
+    setup_env.sh</filename>.</para>
+
+    <para>Setup the uCPE Manager which will be used by the TH:</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Create the uCPE Manager JSON config file in the
+        <literal>&lt;AF-TH-install-dir&gt;/uCPEM_config/</literal>
+        directory:<programlisting>{
+"ucpe_usr":"uCPE Manager Username",
+"ucpe_pass":"uCPE Manager Password",
+"ucpe_host":"uCPE Manager IP/Hostname",
+"ftp_usr":"FTP Username",
+"ftp_pass":"FTP Password",
+"ftp_port":"FTP Port"
+}</programlisting>See the
+        <filename>&lt;AF-TH-install-dir&gt;/uCPEM_config/ucpem01.json</filename>
+        file as an example.</para>
+      </listitem>
+
+      <listitem>
+        <para>Run the <filename>setupuCPEManager.yml</filename> Ansible
+        Playbook with the JSON config path as parameter: <programlisting>ansible-playbook playbooks/setupuCPEManager.yml -e\ 
+"@uCPEM_config/&lt;config_name&gt;.json"</programlisting></para>
+
+        <para><emphasis role="bold">Example</emphasis> <programlisting>ansible-playbook playbooks/setupuCPEManager.yml -e\ 
+"@uCPEM_config/ucpem01.json"</programlisting></para>
+      </listitem>
+    </orderedlist>
+
+    <para>Note that the steps presented in this sub-chapter are to be executed
+    only once, for the initial setup of the TH environment. Afterwards, each
+    session ends by closing the Python virtual environment (<literal>source
+    &lt;AF-THinstall-dir&gt;/testHarness/bin/deactivate</literal>) and
+    subsequent use of the installation requires activating the Python virtual
+    enviroment before using the Automation Framework and Test Harness
+    (<literal>source
+    &lt;AF-THinstall-dir&gt;/testHarness/bin/activate</literal>).</para>
+
+    <para>Furthermore, if a user wants to use a new uCPE Manager instance for
+    a new session, the user also has to re-run the
+    <filename>setupuCPEManager.yml</filename> playbook with the corresponding
+    JSON config for the new uCPE Manager instance.</para>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml~ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml~
new file mode 100755
index 0000000..a52f99b
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/getting_started.xml~
@@ -0,0 +1,223 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="getting_started">
+  <title>Getting Started with the Automation Framework and Test
+  Harness</title>
+
+  <section id="prerequisites">
+    <title>Prerequisites</title>
+
+    <para>For installation of the Automation Framework and Test Harness a
+    CentOS 7 host machine is needed with support for:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Python 2.7</para>
+      </listitem>
+
+      <listitem>
+        <para>EPEL Repository installed:<programlisting>sudo yum install epel-release</programlisting></para>
+      </listitem>
+
+      <listitem>
+        <para>PIP package manager installed: <programlisting>sudo yum -y install python-pip</programlisting></para>
+      </listitem>
+
+      <listitem>
+        <para>Virtualenv tool installed: <programlisting>sudo pip install virtualenv</programlisting></para>
+      </listitem>
+    </itemizedlist>
+
+    <note>
+      <para>The Automation Framework and Test Harness installation may be done
+      on the same machine used for uCPE Manager installation, although this is
+      not encouraged. For more details see <link linkend="automation">chapter
+      3.2</link>.</para>
+    </note>
+  </section>
+
+  <section id="envrion">
+    <title>Environment</title>
+
+    <para><figure>
+        <title>Lab setup overview for Basic Setup</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center"
+                       fileref="images/environment_basicsetup.png" scale="35" />
+          </imageobject>
+        </mediaobject>
+      </figure>The following enviroment setup is needed for running all the
+    tests defined in the Enea NFV Access System Test Specification
+    document:</para>
+
+    <para><emphasis role="bold">Lab Network</emphasis><itemizedlist>
+        <listitem>
+          <para>DHCP enabled.</para>
+        </listitem>
+
+        <listitem>
+          <para>Internet Connectivity.</para>
+        </listitem>
+      </itemizedlist></para>
+
+    <para><emphasis role="bold">uCPE Manager host</emphasis></para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Running CentOS 7.</para>
+      </listitem>
+
+      <listitem>
+        <para>Connected to Lab Network.</para>
+      </listitem>
+
+      <listitem>
+        <para>uCPE Manager installed.</para>
+
+        <note>
+          <para>For details on how to install the uCPE Manager, see "Getting
+          Started with Enea uCPE Manager" from the Enea NFV Access Getting
+          Started manual.</para>
+        </note>
+      </listitem>
+    </itemizedlist>
+
+    <para><emphasis role="bold">1<superscript>st</superscript> Intel Whitebox
+    target device</emphasis><itemizedlist>
+        <listitem>
+          <para>Minimum 4 Physical Network Devices.</para>
+        </listitem>
+
+        <listitem>
+          <para>4GB RAM and 4 cores (Intel C3000 or Xeon D).</para>
+        </listitem>
+
+        <listitem>
+          <para>2 Physical connections to Lab Network.</para>
+        </listitem>
+
+        <listitem>
+          <para>Enea NFV Access installed.</para>
+
+          <note>
+            <para>For information on how to install Enea NFV Access<remark>the
+            solution or the platform?</remark>, refer to "Getting Started with
+            Enea NFV Access" from the Enea NFV Access Getting Started
+            manual.</para>
+          </note>
+        </listitem>
+      </itemizedlist><figure>
+        <title>Lab setup overview for ChainedVNFsService Setup</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center"
+                       fileref="images/ChainedVNFsService_setup.png"
+                       scale="40" />
+          </imageobject>
+        </mediaobject>
+      </figure></para>
+
+    <para><emphasis role="bold">Changes to 1st Intel Whitebox target
+    device</emphasis></para>
+
+    <itemizedlist>
+      <listitem>
+        <para>16GB RAM and 8 cores (Intel C3000 or Xeon D).</para>
+      </listitem>
+
+      <listitem>
+        <para>1 Physical connection back to back with the 2nd Intel Whitebox
+        target device.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para><emphasis role="bold">2<superscript>nd</superscript> Intel Whitebox
+    target device</emphasis><itemizedlist>
+        <listitem>
+          <para>Minimum 4 Physical Network Devices.</para>
+        </listitem>
+
+        <listitem>
+          <para>16GB RAM and 8 cores (Intel C3000 or Xeon D).</para>
+        </listitem>
+
+        <listitem>
+          <para>2 Physical connections to Lab Network.</para>
+        </listitem>
+
+        <listitem>
+          <para>1 Physical connection back to back with the
+          1<superscript>st</superscript> Intel Whitebox target device.</para>
+        </listitem>
+
+        <listitem>
+          <para>Enea NFV Access installed.</para>
+
+          <note>
+            <para>For information on how to install Enea NFV Access<remark>the
+            solution or the platform?</remark>, refer to "Getting Started with
+            Enea NFV Access" from the Enea NFV Access Getting Started
+            manual.</para>
+          </note>
+        </listitem>
+      </itemizedlist></para>
+  </section>
+
+  <section id="initial_setup">
+    <title>Installation and Initial Setup</title>
+
+    <para>Download <filename>nfvaccess22_af-th.zip</filename> from the Enea
+    Portal and unzip it on the a supported host machine. Henceforth, the
+    directory in which the ZIP archive has been unpacked will be denoted as
+    <literal>&lt;AF-TH-installdir&gt;</literal>.</para>
+
+    <para>Enter the <literal>&lt;AF-TH-install-dir&gt;</literal> directory and
+    run the <filename>setup_env.sh</filename> script to do the initial setup
+    of the Test Harness environment: <filename>source
+    setup_env.sh</filename>.</para>
+
+    <para>Setup the uCPE Manager which will be used by the TH:</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Create the uCPE Manager JSON config file in the
+        <literal>&lt;AF-TH-install-dir&gt;/uCPEM_config/</literal>
+        directory:<programlisting>{
+"ucpe_usr":"uCPE Manager Username",
+"ucpe_pass":"uCPE Manager Password",
+"ucpe_host":"uCPE Manager IP/Hostname",
+"ftp_usr":"FTP Username",
+"ftp_pass":"FTP Password",
+"ftp_port":"FTP Port"
+}</programlisting>See the
+        <filename>&lt;AF-TH-install-dir&gt;/uCPEM_config/ucpem01.json</filename>
+        file as an example.</para>
+      </listitem>
+
+      <listitem>
+        <para>Run the <filename>setupuCPEManager.yml</filename> Ansible
+        Playbook with the JSON config path as parameter: <programlisting>ansible-playbook playbooks/setupuCPEManager.yml &ndash;e\ 
+"@uCPEM_config/&lt;config_name&gt;.json"</programlisting></para>
+
+        <para><emphasis role="bold">Example</emphasis> <programlisting>ansible-playbook playbooks/setupuCPEManager.yml &ndash;e\ 
+"@uCPEM_config/ucpem01.json"</programlisting></para>
+      </listitem>
+    </orderedlist>
+
+    <para>Note that the steps presented in this sub-chapter are to be executed
+    only once, for the initial setup of the TH environment. Afterwards, each
+    session ends by closing the Python virtual environment (<literal>source
+    &lt;AF-THinstall-dir&gt;/testHarness/bin/deactivate</literal>) and
+    subsequent use of the installation requires activating the Python virtual
+    enviroment before using the Automation Framework and Test Harness
+    (<literal>source
+    &lt;AF-THinstall-dir&gt;/testHarness/bin/activate</literal>). </para>
+
+    <para>Furthermore, if a user wants to use a new uCPE Manager instance for
+    a new session, the user also has to re-run the
+    <filename>setupuCPEManager.yml</filename> playbook with the corresponding
+    JSON config for the new uCPE Manager instance.</para>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png
new file mode 100755
index 0000000..fad8009
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/ChainedVNFsService_setup.png
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png
new file mode 100755
index 0000000..7599ead
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/autofw_testh_overview.png
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/environment_basicsetup.png b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/environment_basicsetup.png
new file mode 100755
index 0000000..0b92f7a
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/images/environment_basicsetup.png
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml
new file mode 100644
index 0000000..9b9eaaa
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/overview.xml
@@ -0,0 +1,196 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="overview">
+  <title>Overview</title>
+
+  <para>This document describes the Automation Framework and Test Harness for
+  the Enea NFV Access Solution, a long with providing instructions regarding
+  the necessary steps to run these software tools.</para>
+
+  <section id="descrip">
+    <title>Description</title>
+
+    <para>The Automation Framework provides a way for driving configuration
+    with Python scripting. It complements the Enea uCPE Manager GUI and uses
+    the northbound REST APIs, given for full availability of the Enea uCPE
+    Manager features.</para>
+
+    <para>The Test Harness is based on running Ansible Playbooks to complete
+    different test cases, which make use of the Automation Framework Python
+    modules and/or direct commands on the boards running Enea NFV
+    Access.</para>
+  </section>
+
+  <section id="def_acro">
+    <title>Definitions and Acronyms</title>
+
+    <table>
+      <title>Definitions</title>
+
+      <tgroup cols="2">
+        <colspec align="center" />
+
+        <thead>
+          <row>
+            <entry align="center">Component</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry>Enea NFV Access Solution</entry>
+
+            <entry>Enea NFV Access (with ODM) Runtime Platform and Enea uCPE
+            Manager.</entry>
+          </row>
+
+          <row>
+            <entry>Enea Portal</entry>
+
+            <entry><ulink
+            url="https://portal.enea.com">https://portal.enea.com</ulink></entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+
+    <table>
+      <title>Acronyms</title>
+
+      <tgroup cols="2">
+        <colspec align="center" />
+
+        <thead>
+          <row>
+            <entry align="center">Component</entry>
+
+            <entry align="center">Description</entry>
+          </row>
+        </thead>
+
+        <tbody>
+          <row>
+            <entry>AF</entry>
+
+            <entry>Automation Framework for Enea NFV Access.</entry>
+          </row>
+
+          <row>
+            <entry>API</entry>
+
+            <entry>Application Programming Interface.</entry>
+          </row>
+
+          <row>
+            <entry>DHCP</entry>
+
+            <entry>Dynamic Host Configuration Protocol.</entry>
+          </row>
+
+          <row>
+            <entry>DPDK</entry>
+
+            <entry>Data Plane Development Kit.</entry>
+          </row>
+
+          <row>
+            <entry>FTP</entry>
+
+            <entry>File Transfer Protocol.</entry>
+          </row>
+
+          <row>
+            <entry>GUI</entry>
+
+            <entry>Graphical User Interface.</entry>
+          </row>
+
+          <row>
+            <entry>IP</entry>
+
+            <entry>Internet Protocol.</entry>
+          </row>
+
+          <row>
+            <entry>JSON</entry>
+
+            <entry>JavaScript Object Notation.</entry>
+          </row>
+
+          <row>
+            <entry>NIC</entry>
+
+            <entry>Network Interface Card.</entry>
+          </row>
+
+          <row>
+            <entry>NETCONF</entry>
+
+            <entry>Network Configuration Protocol.</entry>
+          </row>
+
+          <row>
+            <entry>NFV</entry>
+
+            <entry>Network Functions Virtualization.</entry>
+          </row>
+
+          <row>
+            <entry>ODM</entry>
+
+            <entry>Enea Element On Device Management.</entry>
+          </row>
+
+          <row>
+            <entry>OVS</entry>
+
+            <entry>Open vSwitch.</entry>
+          </row>
+
+          <row>
+            <entry>REST</entry>
+
+            <entry>Representational State Transfer.</entry>
+          </row>
+
+          <row>
+            <entry>SR-IOV</entry>
+
+            <entry>Single Root Input/Output Virtualization.</entry>
+          </row>
+
+          <row>
+            <entry>SSH</entry>
+
+            <entry>Secure Shell.</entry>
+          </row>
+
+          <row>
+            <entry>TH</entry>
+
+            <entry>Test Harness for Enea NFV Access.</entry>
+          </row>
+
+          <row>
+            <entry>uCPE Manager</entry>
+
+            <entry>Enea Universal Customer Premises Equipment Manager.</entry>
+          </row>
+
+          <row>
+            <entry>VCPE</entry>
+
+            <entry>Virtual Customer Premises Equipment</entry>
+          </row>
+
+          <row>
+            <entry>VNF</entry>
+
+            <entry>Virtualized Network Function</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </table>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
new file mode 100644
index 0000000..f9d4381
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/doc/troubleshooting_guide.xml
@@ -0,0 +1,6 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="troubleshooting_guide">
+  <title>Troubleshooting Guide</title>
+
+    <para></para>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk b/doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk
new file mode 100755
index 0000000..9f0a075
--- /dev/null
+++ b/doc/book-enea-nfv-access-auto-fw-th-user-guide/swcomp.mk
@@ -0,0 +1,10 @@
+# Component build specification
+
+# Version of THIS book
+BOOK_VER ?= $(REL_VER)-dev
+
+DOCBOOK_SRC := $(COMP)/swcomp.mk $(COMP)/doc/book.xml $(shell find $(COMP)/doc -type f \( -name "*.xml" -o -name "*.svg" -o -name "*.png" \) ! -name "book.xml" -print)
+
+BOOKPACKAGES := book-enea-nfv-access-auto-fw-th-user-guide
+BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) Automation Framework and Test Harness User Guide"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)