Added the System Test Spec Doc.

Change-Id: I532d2f343e5c6a0ddb7bf06961b6f889e9108952

9 files changed, 1807 insertions, 1 deletions

diff --git a/doc/Makefile b/doc/Makefile
index 2cf6e28..b9e7bac 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 book-enea-nfv-access-auto-fw-th-user-guide
+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 book-enea-nfv-access-system-test-specification
 #  COMPONENTS += 
 #book-enea-linux-eclipse-open-source 
 #book-enea-nfv-access-dev-hardening-guide
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/book.xml b/doc/book-enea-nfv-access-system-test-specification/doc/book.xml
new file mode 100644
index 0000000..d1b0cae
--- /dev/null
+++ b/doc/book-enea-nfv-access-system-test-specification/doc/book.xml
@@ -0,0 +1,27 @@
+<?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_system_test_specification">
+  <title><trademark class="registered">Enea</trademark> NFV Access System Test Specification</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="configuration.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="sample_test_cases.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+</book>
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml b/doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml
new file mode 100644
index 0000000..d1415c2
--- /dev/null
+++ b/doc/book-enea-nfv-access-system-test-specification/doc/configuration.xml
@@ -0,0 +1,32 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="config_sts">
+  <title>Configuration</title>
+
+  <section id="test_objects">
+    <title>Test Objects</title>
+
+    <para>The test objects for the Test Harness are considered to be the Enea
+    NFV Access and Enea uCPE Manager installations performed as indicated in
+    chapter 3 of the Enea NFV Access Automation Framework and Test Harness
+    User Guide.</para>
+  </section>
+
+  <section id="test_env">
+    <title>Test Environment</title>
+
+    <para>To setup the required Test Harness environment please refer to the
+    "Environment" chapter from the Enea NFV Access Automation Framework and
+    Test Harness User Guide.</para>
+  </section>
+
+  <section id="precon_exe_steps">
+    <title>Preconditions and Execution Steps</title>
+
+    <para>Please refer to the "Prerequisites" and "Installation and Initial
+    Setup" chapters from Enea NFV Access Automation Framework and Test Harness
+    User Guide.</para>
+
+    <para>For detailed execution steps of the sample test cases included with
+    the Test Harness please see chapter 3 in this document.</para>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-system-test-specification/doc/eltf_params_template.xml b/doc/book-enea-nfv-access-system-test-specification/doc/eltf_params_template.xml
new file mode 100644
index 0000000..eaa7ebd
--- /dev/null
+++ b/doc/book-enea-nfv-access-system-test-specification/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-system-test-specification/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-system-test-specification/doc/eltf_params_updated.xml
new file mode 100644
index 0000000..feabc9f
--- /dev/null
+++ b/doc/book-enea-nfv-access-system-test-specification/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-system-test-specification/doc/eltf_params_updated_template_how_to_use.txt b/doc/book-enea-nfv-access-system-test-specification/doc/eltf_params_updated_template_how_to_use.txt
new file mode 100755
index 0000000..62e5d02
--- /dev/null
+++ b/doc/book-enea-nfv-access-system-test-specification/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-system-test-specification/doc/overview.xml b/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml
new file mode 100644
index 0000000..7df9acc
--- /dev/null
+++ b/doc/book-enea-nfv-access-system-test-specification/doc/overview.xml
@@ -0,0 +1,125 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="overview_sts">
+  <title>Overview</title>
+
+  <para>This document specifies a Sample Test Suite for System Testing of the
+  Enea NFV Access Solution. It also provides information regarding the
+  necessary steps to run these tests.</para>
+
+  <section id="scope">
+    <title>Scope</title>
+
+    <para>The scope of this document is to describe the Test Harness (TH)
+    sample test cases for System Testing of the Enea NFV Access Solution.
+    Furthermore, this document shall also describe the necessary environment
+    setup to run these tests successfully.</para>
+  </section>
+
+  <section id="def_acro_sts">
+    <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>JSON</entry>
+
+            <entry>JavaScript Object Notation.</entry>
+          </row>
+
+          <row>
+            <entry>NIC</entry>
+
+            <entry>Network Interface Card.</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>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>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-system-test-specification/doc/sample_test_cases.xml b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
new file mode 100644
index 0000000..50907ca
--- /dev/null
+++ b/doc/book-enea-nfv-access-system-test-specification/doc/sample_test_cases.xml
@@ -0,0 +1,855 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="sample_testcases">
+  <title>Sample Test Cases</title>
+
+  <para>The test cases specified in this chapter are implemented as a Sample
+  Test Suite included in the TH.</para>
+
+  <section id="vnf_dev_net_smoke">
+    <title>VNF, Device and Network Smoke Test Cases</title>
+
+    <para>The following is an automated test suite that acts as basic smoke
+    tests for the Enea NFV Access Solution and as a sanity-check test suite
+    for the AF and TH.</para>
+
+    <section id="onb_vnf_image">
+      <title>VNF - Onboard_VNF_Image</title>
+
+      <para><emphasis role="bold">Description: </emphasis>Onboarding a VNF
+      Image into the uCPE Manager. For details please refer to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/onboardVNFImage.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/vnf/onboardVNFRaw.py</filename></para>
+
+      <para><emphasis role="bold">Preconditions:</emphasis></para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Add the VNF Image in the <literal>vnf_image</literal> folder
+          in QCOW2 format: <programlisting>&lt;AF-TH-install-dir&gt;/vnf_image/&lt;VNF-Image-name&gt;.qcow2</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>A VNF Image JSON configuration file is created:
+          <filename>&lt;AF-TH-install-dir&gt;/vnf_config/&lt;VNF-Descriptor-name&gt;/&lt;VNF-Descriptor-name&gt;.json</filename>.</para>
+
+          <para><emphasis role="bold">Example:</emphasis><programlisting>&lt;AF-TH-install-dir&gt;/vnf_config/fortigateImage/fortigateImage.json</programlisting></para>
+        </listitem>
+      </itemizedlist>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>onboardVNFImage.yml</filename> Ansible Playbook with the
+      <literal>&lt;VNF-Image-name&gt;</literal> and the
+      <literal>&lt;VNF-Descriptor-name&gt;</literal> as extra-vars:
+      <programlisting>ansible-playbook playbooks/onboardVNFImage.yml -e "vnfb=&lt;VNF-Image-name&gt; \
+vnfd=&lt;VNF-Descriptor-name&gt;"</programlisting></para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># Onboard VNF Image task result
+&lt;VNF-Descriptor-name&gt; successfully onboarded!</programlisting><emphasis
+      role="bold">Note:</emphasis> The test will not fail if the VNF Image is
+      already onboarded. The output will instead contain: <programlisting># debug &lt;VNF-Descriptor-name&gt; already onboarded!</programlisting></para>
+    </section>
+
+    <section id="onb_vnf_bundle">
+      <title>VNF - Onboard_VNF_Bundle<remark>since we're removing mention of
+      bundles is this section still relevant?</remark></title>
+
+      <para><emphasis role="bold">Description:</emphasis> Onboarding a VNF
+      Bundle into the uCPE Manager. For details please refer to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/onboardVNFBundle.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/vnf/onboardVNF.py</filename></para>
+
+      <para><emphasis role="bold">Precondition:</emphasis> Add the VNF Bundle
+      in the <literal>vnf_image</literal> folder in the zip format:
+      <filename>&lt;AF-TH-install-dir&gt;/vnf_image/&lt;VNF-Bundle-name&gt;.zip</filename>.</para>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>onboardVNFBundle.yml</filename> Ansible Playbook with the
+      <literal>&lt;VNF-Bundle-name&gt;</literal> as extra-vars:
+      <programlisting>ansible-playbook playbooks/onboardVNFBundle.yml -e "vnfb=&lt;VNF-Bundle-name&gt;"</programlisting></para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># Onboard VNF Bundle task result
+&lt;VNF-Bundle-name&gt; successfully onboarded!</programlisting><emphasis
+      role="bold">Note:</emphasis> The test will not fail if the VNF Bundle is
+      already onboarded. The output will instead contain: <programlisting># debug &lt;VNF-Bundle-name&gt; already onboarded!</programlisting></para>
+    </section>
+
+    <section id="offb_vnf">
+      <title>VNF - Offboard_VNF</title>
+
+      <para><emphasis role="bold">Description:</emphasis> Removing a VNF
+      Descriptor from the uCPE Manager. For details please refer to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/offboardVNF.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/vnf/offboardVNF.py</filename>.</para>
+
+      <para><emphasis role="bold">Precondition:</emphasis> The VNF has been
+      previously onboarded in the uCPE Manager instance.</para>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>offboardVNF.yml</filename> Ansible Playbook with the
+      <literal>&lt;VNF-Descriptor-name&gt;</literal> as extra-vars:
+      <programlisting>ansible-playbook playbooks/offboardVNF.yml -e "vnfd=&lt;VNF-Descriptor-name&gt;"</programlisting></para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># Remove Descriptor task result
+&lt;VNF-Descriptor-name&gt; was removed!</programlisting><emphasis
+      role="bold">Note:</emphasis> The test will not fail if the VNF
+      Descriptor does not exist. The output will instead contain:
+      <programlisting># debug No Descriptor with name &lt;VNF-Descriptor-name&gt;!</programlisting></para>
+    </section>
+
+    <section id="add_device">
+      <title>Device - Add_Device</title>
+
+      <para><emphasis role="bold">Description:</emphasis> Adding a uCPE device
+      to the uCPE Manager. For details please refer to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/addDevice.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/device/addDevice.py</filename>.</para>
+
+      <para><emphasis role="bold">Precondition:</emphasis> A device JSON
+      configuration file must be created:
+      <filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/&lt;Device-name&gt;.json</filename>.</para>
+
+      <para><emphasis role="bold">Example:</emphasis> <programlisting>&lt;AF-TH-install-dir&gt;/lab_config/intelc3850-2/intelc3850-2.json</programlisting></para>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>addDevice.yml</filename> Ansible playbook with the
+      <filename>&lt;Device-name&gt;</filename> as extra-vars: <programlisting>ansible-playbook playbooks/addDevice.yml -e "device=&lt;Device-name&gt;"</programlisting></para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># Add Device task result
+&lt;Device-name&gt; device was added!</programlisting><emphasis
+      role="bold">Note:</emphasis> The test will not fail if the device
+      already exists. The output will instead contain: <programlisting># debug
+&lt;Device-name&gt; device already exists!</programlisting></para>
+    </section>
+
+    <section id="remv_dev">
+      <title>Device - Remove_Device</title>
+
+      <para><emphasis role="bold">Description:</emphasis> Removing a uCPE
+      device from the uCPE Manager. For details please refer to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/removeDevice.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/device/removeDevice.py</filename>.</para>
+
+      <para><emphasis role="bold">Preconditions:</emphasis></para>
+
+      <itemizedlist>
+        <listitem>
+          <para>The device has to be previously added to the uCPE Manager
+          instance.</para>
+        </listitem>
+
+        <listitem>
+          <para>The device JSON configuration file must exist:
+          <programlisting>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/&lt;Device-name&gt;.json</programlisting></para>
+        </listitem>
+      </itemizedlist>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>removeDevice.yml</filename> Ansible Playbook with the
+      <literal>&lt;Device-name&gt;</literal> as extra-vars: <programlisting>ansible-playbook playbooks/removeDevice.yml -e "device=&lt;Device-name&gt;"</programlisting></para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness:<programlisting># Remove Device task result
+&lt;Device-name&gt; device was removed!</programlisting> <emphasis
+      role="bold">Note:</emphasis> The test will not fail if the device does
+      not exist. The output will contain: <programlisting># debug
+&lt;Device-name&gt; device was not found!</programlisting></para>
+    </section>
+
+    <section id="bind_nic">
+      <title>Network - Bind_NIC</title>
+
+      <para><emphasis role="bold">Description:</emphasis> Binding a physical
+      network interface (NIC) to a device. For details please refer to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/bindNIC.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/network/bindNetworkInterface.py</filename>.</para>
+
+      <para><emphasis role="bold">Preconditions:</emphasis></para>
+
+      <itemizedlist>
+        <listitem>
+          <para>A device must have been previously added to the uCPE Manager
+          instance.</para>
+        </listitem>
+
+        <listitem>
+          <para>A NIC JSON configuration file must exist:
+          <filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/&lt;NIC&gt;.json</filename>.</para>
+
+          <para><emphasis role="bold">Example:</emphasis> <programlisting>&lt;AF-TH-install-dir&gt;/lab_config/intelc3850-2/wan_nic.json
+&lt;AF-TH-install-dir&gt;/lab_config/intelc3850-2/lan_nic.json</programlisting></para>
+        </listitem>
+      </itemizedlist>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>bindNIC.yml</filename> Ansible Playbook with the
+      <literal>&lt;Device-name&gt;</literal> and
+      <literal>&lt;NIC&gt;</literal> as extra-vars: <programlisting>ansible-playbook playbooks/bindNIC.yml -e "device=&lt;Device-name&gt; nic=&lt;NIC&gt;"</programlisting></para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># Bind NIC task result
+&lt;NIC&gt; binded successfully!</programlisting> <emphasis
+      role="bold">Note:</emphasis> The test will not fail if the NIC is
+      already bound, it will be unbound and bound again with the provided
+      configuration.</para>
+    </section>
+
+    <section id="unbind_nic">
+      <title>Network - Unbind_NIC</title>
+
+      <para><emphasis role="bold">Description:</emphasis> Unbinding a physical
+      network interface (NIC) from a device. For details please refer
+      to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/unbindNIC.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/network/unbindNetworkInterface.py</filename>.</para>
+
+      <para><emphasis role="bold">Preconditions:</emphasis></para>
+
+      <itemizedlist>
+        <listitem>
+          <para>A NIC is bound to a device in a uCPE Manager instance.</para>
+        </listitem>
+
+        <listitem>
+          <para>A NIC JSON configuration file exists:
+          <filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/&lt;NIC&gt;.json</filename></para>
+        </listitem>
+      </itemizedlist>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>unbindNIC.yml</filename> Ansible Playbook with the
+      <literal>&lt;Device-name&gt;</literal> and
+      <literal>&lt;NIC&gt;</literal> as extra-vars: <programlisting>ansible-playbook playbooks/unbindNIC.yml -e "device=&lt;Device-name&gt; nic=&lt;NIC&gt;"</programlisting></para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># Unbind NIC task result
+&lt;NIC&gt; unbinded!</programlisting> <emphasis role="bold">Note:</emphasis>
+      The test will not fail if the NIC is not bound. The output will instead
+      contain:<programlisting># debug
+&lt;NIC&gt; is not binded!</programlisting></para>
+    </section>
+
+    <section id="create_bri">
+      <title>Network - Create_Bridge</title>
+
+      <para><emphasis role="bold">Description:</emphasis> Creating an OVS
+      network bridge on a uCPE device. For details please refer to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/addBridge.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/network/newNetworkBridge.py</filename>.</para>
+
+      <para><emphasis role="bold">Precondition:</emphasis><itemizedlist>
+          <listitem>
+            <para>A NIC is bound to a device in a uCPE Manager
+            instance.</para>
+          </listitem>
+
+          <listitem>
+            <para>A Bridge JSON configuration file is created:
+            <filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/&lt;Bridge-name&gt;.json</filename></para>
+
+            <para><emphasis role="bold">Example:</emphasis><programlisting>&lt;AF-TH-install-dir&gt;/lab_config/intelc3850-2/wan_br.json
+&lt;AF-TH-install-dir&gt;/lab_config/intelc3850-2/lan_br.json</programlisting></para>
+          </listitem>
+        </itemizedlist></para>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>addBridge.yml</filename> Ansible Playbook with the
+      <literal>&lt;Device-name&gt;</literal> and the
+      <literal>&lt;Bridge-name&gt;</literal> as extra-vars: <programlisting>ansible-playbook playbooks/addBridge.yml -e "device=&lt;Device-name&gt; bridge=&lt;Bridge-name&gt;"</programlisting></para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># Add Bridge task result
+&lt;Bridge-name&gt; network bridge was added!</programlisting><emphasis
+      role="bold">Note:</emphasis> The test will not fail if there already
+      exists a bridge with the same name, it will be deleted and the bridge
+      will be created again with the provided configuration.</para>
+    </section>
+
+    <section id="remov_bri">
+      <title>Network - Remove_Bridge</title>
+
+      <para><emphasis role="bold">Description:</emphasis> Removing an OVS
+      network bridge from a uCPE device. For details please refer to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/deleteBridge.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/network/delNetworkBridge.py</filename>.</para>
+
+      <para><emphasis role="bold">Preconditions:</emphasis> <itemizedlist>
+          <listitem>
+            <para>A Bridge is created in a uCPE Manager instance.</para>
+          </listitem>
+
+          <listitem>
+            <para>A Bridge JSON configuration file exists:
+            <filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/&lt;Bridge-name&gt;.json</filename>.</para>
+          </listitem>
+        </itemizedlist><emphasis role="bold">Action:</emphasis> Run the
+      <filename>deleteBridge.yml</filename> Ansible Playbook with the
+      <literal>&lt;Device-name&gt;</literal> and the
+      <literal>&lt;Bridge-name&gt;</literal> as extra-vars: <programlisting>ansible-playbook playbooks/deleteBridge.yml -e "device=&lt;Device-name&gt; \
+bridge=&lt;Bridge-name&gt;"</programlisting></para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># Delete Bridge task result
+&lt;Bridge-name&gt; network bridge was deleted!</programlisting><emphasis
+      role="bold">Note:</emphasis> The test will not fail if the bridge does
+      not exist: <programlisting># debug
+&lt;Bridge-name&gt; bridge not found!</programlisting></para>
+    </section>
+  </section>
+
+  <section id="vnf_deploy_lifecycle">
+    <title>VNF Deployment and Lifecycle</title>
+
+    <para>The following details the automated suite that handles the testing
+    of the instantiation, lifecycle and destruction of a VNF for the Enea NFV
+    Access Solution.</para>
+
+    <section id="inst_vnfi">
+      <title>Instantiate_VNFI</title>
+
+      <para><emphasis role="bold">Description:</emphasis> Creating a VNF
+      instance on a uCPE device. For details please refer to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/instantiateVNFI.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/vnf/instantiateVNFI.py</filename>.</para>
+
+      <para><emphasis role="bold">Preconditions:</emphasis> <itemizedlist>
+          <listitem>
+            <para>A VNF Image is onboarded and a device is added to the uCPE
+            Manager. Depending on the VNF, other steps may be required.</para>
+          </listitem>
+
+          <listitem>
+            <para>A VNFI JSON configuration file is created:
+            <filename>&lt;AF-TH-install-dir&gt;/vnf_config/&lt;VNF-Descriptor-name&gt;/&lt;VNFI-name&gt;.json</filename></para>
+
+            <para><emphasis role="bold">Example:</emphasis> <programlisting>&lt;AF-TH-install-dir&gt;/vnf_config/fortigateImage/fortigateFWInstance.json</programlisting></para>
+          </listitem>
+        </itemizedlist></para>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>instantiateVNFI.yml</filename> Ansible Playbook with the
+      <literal>&lt;Device-name&gt;</literal>,
+      <literal>&lt;VNF-Descriptor-name&gt;</literal> and the
+      <literal>&lt;VNFI-name&gt;</literal> as extra-vars: <programlisting>ansible-playbook playbooks/instantiateVNFI.yml -e "device=&lt;Device-name&gt; \
+vnfd=&lt;VNF-Descriptor-name&gt; vnfi=&lt;VNFI-name&gt;"</programlisting></para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># Instantiate VNF task result
+&lt;VNFI-name&gt; was instantiated!</programlisting><emphasis
+      role="bold">Note:</emphasis> The test will not fail when the VNF
+      instance already exists. The output will contain: <programlisting># debug
+&lt;VNFI-name&gt; already exists!</programlisting></para>
+    </section>
+
+    <section id="control_vnfi">
+      <title>Control_VNFI</title>
+
+      <para><emphasis role="bold">Description:</emphasis> Changing the status
+      of a VNF instance (Pause, Resume, Stop, Start). For details please refer
+      to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/controlVNFI.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/vnf/controlVNFI.py</filename>.</para>
+
+      <para><emphasis role="bold">Precondition:</emphasis> A VNF is
+      instantiated on a uCPE device.</para>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>controlVNFI.yml</filename> Ansible Playbook with the
+      <literal>&lt;Device-name&gt;</literal>,
+      <literal>&lt;VNFI-name&gt;</literal> and the
+      <literal>&lt;Command&gt;</literal> as extra-vars: <programlisting>ansible-playbook playbooks/controlVNFI.yml -e "device=&lt;Device-name&gt; \
+vnfi=&lt;VNFI-name&gt; status=&lt;Command&gt;"</programlisting>Where Command =
+      { pause | resume | stop | start }</para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># Change VNFI Status task result
+&lt;VNFI-name&gt; status was set to &lt;Command&gt;</programlisting><emphasis
+      role="bold">Note:</emphasis> The test will not fail if the VNF instance
+      does not exist or when the specified command is not valid. Depending on
+      the case, the output will contain: <programlisting># debug
+&lt;VNFI-name&gt; was not found!</programlisting><programlisting># debug
+Invalid VNF Instance control command specified - &lt;Command&gt;</programlisting></para>
+    </section>
+
+    <section id="destroy_vnfi">
+      <title>Destroy_VNFI</title>
+
+      <para><emphasis role="bold">Description:</emphasis> Destroying a VNF
+      instance from a uCPE device. For details please refer to:</para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/destroyVNFI.yml</filename></para>
+
+      <para><filename>&lt;AF-TH-install-dir&gt;/automation_framework/vnf/destroyVNFI.py</filename>.</para>
+
+      <para><emphasis role="bold">Precondition:</emphasis> A VNF is
+      instantiated on a uCPE device.</para>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>destroyVNFI.yml</filename> Ansible Playbook with the
+      <literal>&lt;Device-name&gt;</literal> and the
+      <filename>&lt;VNFI-name&gt;</filename> as extra-vars: <programlisting>ansible-playbook playbooks/destroyVNFI.yml -e "device=&lt;Device-name&gt; vnfi=&lt;VNFI-name&gt;"</programlisting><emphasis
+      role="bold">Result:</emphasis> Output of the test case run using the
+      Test Harness:<programlisting># Destroy VNFI task result
+&lt;VNFI-name&gt; was destroyed!</programlisting><emphasis
+      role="bold">Note:</emphasis> The test will not fail when the VNF
+      instance does not exist. The output will contain: <programlisting># debug
+&lt;VNFI-name&gt; was not found!</programlisting></para>
+    </section>
+  </section>
+
+  <section id="serv_creat_lifecycle">
+    <title>Service Creation and Lifecycle</title>
+
+    <para>This test suite contains more complex test cases designed to verify
+    service creation and service lifecycle management. These test cases also
+    serve as examples of how different services can be deployed using the
+    Automation Framework (AF) and the Test Harness (TH).</para>
+
+    <section id="fortigate_firewall">
+      <title>Fortigate_VNF_as_a_Firewall</title>
+
+      <para>This test case was implemented in 2 different ways to exemplify
+      both methods supported by the AF and TH to deploy such services.</para>
+
+      <para>Prerequisites needed in order to deploy the FortiGate VNF as a
+      Firewall:</para>
+
+      <orderedlist>
+        <listitem>
+          <para>Onboard the FortiGate VNF Image.</para>
+        </listitem>
+
+        <listitem>
+          <para>Add a device.</para>
+        </listitem>
+
+        <listitem>
+          <para>Bind 2 physical interfaces, <literal>wan_nic</literal> (this
+          physical interface has to be connected to Lab Network) and
+          <literal>lan_nic</literal>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Create 2 bridges, <literal>wan_br</literal> (using
+          <literal>wan_nic</literal> interface) and <literal>lan_br</literal>
+          (using <literal>lan_nic</literal> interface).</para>
+        </listitem>
+
+        <listitem>
+          <para>Instantiate the FortiGate VNF using the basic Firewall
+          configuration and the FortiGate License.</para>
+        </listitem>
+      </orderedlist>
+
+      <para>For more information please refer to "FortiGate VNF as a Firewall"
+      chapter from the "Enea NFV Access Example Use-cases" manual.<note>
+          <para>The license and configuration files for the FortiGate VNF are
+          not included in the TH and should be obtained from the user's Enea
+          Portal account.</para>
+        </note></para>
+
+      <section id="fortigate_fw_instance">
+        <title>FortigateFWInstance Test</title>
+
+        <para><emphasis role="bold">Description:</emphasis> Instantiate the
+        FortiGate VNF as a Firewall and test it using isolated network
+        namespace.</para>
+
+        <para>This example was implemented with the "Test Harness" method,
+        based on Ansible Playbooks. For details please refer to:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/fortigateFWService/instantiateFortigateFW.yml</filename></para>
+          </listitem>
+
+          <listitem>
+            <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/fortigateFWService/testFortigateFWInstance.yml</filename></para>
+          </listitem>
+
+          <listitem>
+            <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/fortigateFWService/cleanupTestFortigateFWInstance.yml</filename></para>
+          </listitem>
+
+          <listitem>
+            <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/fortigateFWService/cleanupFortigateFWInstance.yml</filename></para>
+          </listitem>
+        </itemizedlist>
+
+        <para><emphasis role="bold">Preconditions:</emphasis></para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Add the Fortigate VNF Image
+            (<filename>fortios.qcow2</filename>) to the
+            <literal>vnf_image</literal> folder.</para>
+          </listitem>
+
+          <listitem>
+            <para>Device JSON configuration file is created:
+            <filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/&lt;Device-name&gt;.json</filename>.</para>
+          </listitem>
+
+          <listitem>
+            <para>Add device settings in the <literal>hosts</literal> Ansible
+            inventory file under <literal>[fortigateFW]</literal> and remove
+            the <filename>intelc3850-2</filename> example.</para>
+
+            <para><emphasis role="bold">Example:</emphasis> <programlisting>intelc3850-2 ansible_host=172.24.12.114 ansible_port=22 \
+ansible_user=root ansible_pass=root</programlisting></para>
+          </listitem>
+
+          <listitem>
+            <para>NIC JSON configuration files are created:</para>
+
+            <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/wan_nic.json</filename></para>
+
+            <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/lan_nic.json</filename></para>
+          </listitem>
+
+          <listitem>
+            <para>Bridge JSON configuration files are created:</para>
+
+            <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/wan_br.json</filename></para>
+
+            <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/lan_br.json</filename></para>
+          </listitem>
+
+          <listitem>
+            <para>Download the FortiGate VNF Firewall basic configuration from
+            the Enea Portal, copy it into the
+            <filename>&lt;AF-TH-install-dir&gt;/vnf_config/fortigateImage</filename>
+            directory and rename it to<filename>
+            fortigateFW.conf</filename>.</para>
+          </listitem>
+
+          <listitem>
+            <para>Retrieve the FortiGate VNF license from Fortinet or the Enea
+            Portal, copy it into the
+            <literal>&lt;AF-TH-install-dir&gt;/vnf_config/fortigateImage</literal>
+            directory and rename it to
+            <filename>fortigateLicense.lic</filename>.</para>
+
+            <para>Please refer to "FortiGate VNF as a Firewall" chapter from
+            the Enea NFV Access Example Use-cases manual.</para>
+          </listitem>
+        </itemizedlist>
+
+        <para><emphasis role="bold">Action:</emphasis> Run the <emphasis
+        role="bold">instantiateFortigateFW.yml</emphasis> Ansible Playbook
+        with the <literal>&lt;Device-name&gt;</literal> as
+        extra-vars:<programlisting>ansible-playbook playbooks/fortigateFWService/instantiateFortigateFW.yml \
+-e "device=&lt;Device-name&gt;"</programlisting></para>
+
+        <para><emphasis role="bold">Result:</emphasis> Output of the test case
+        run using the Test Harness: <programlisting># Test FortigateFWInstance task result
+FortigateFWInstance tested successfully!</programlisting></para>
+
+        <para><emphasis role="bold">Cleanup:</emphasis> Run the
+        <literal>cleanupFortigateFWInstance.yml</literal> Ansible Playbook
+        with the <literal>&lt;Device-name&gt;</literal> as extra-vars:
+        <programlisting>ansible-playbook playbooks/fortigateFWService/cleanupFortigateFWInstance.yml \
+-e "device=&lt;Device-name&gt;"</programlisting></para>
+      </section>
+
+      <section id="deploy_fortigate_fw">
+        <title>DeployFortigateFW Scenario</title>
+
+        <para><emphasis role="bold">Description:</emphasis> Deploy the
+        Fortigate VNF as a Firewall. This example was implemented with the
+        "Automation Framework" method, based on the
+        <filename>unittestSuite.py</filename> Python module.</para>
+
+        <para>For details please refer to:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para><literal>&lt;AF-TH-install-dir&gt;/playbooks/unittestSuiteTest/deployFortigateFWScenario.yml</literal></para>
+          </listitem>
+
+          <listitem>
+            <para><literal>&lt;AF-TH-install-dir&gt;/playbooks/unittestSuiteTest/cleanupFortigateFWScenario.yml</literal></para>
+          </listitem>
+
+          <listitem>
+            <para><literal>&lt;AF-TH-install-dir&gt;/automation_framework/unittestSuite</literal>
+            directory.</para>
+          </listitem>
+        </itemizedlist>
+
+        <para><emphasis role="bold">Preconditions:</emphasis></para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Add the FortiGate VNF Image
+            (<filename>fortios.qcow2</filename>) to the
+            <literal>vnf_image</literal> folder.</para>
+          </listitem>
+
+          <listitem>
+            <para>Device JSON configuration file is created:
+            <filename></filename></para>
+
+            <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/&lt;Device-name&gt;.json</filename>.</para>
+          </listitem>
+
+          <listitem>
+            <para>NIC JSON configuration files are created:</para>
+
+            <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/wan_nic.json</filename></para>
+
+            <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/lan_nic.json</filename></para>
+          </listitem>
+
+          <listitem>
+            <para>Bridge JSON configuration files are created:</para>
+
+            <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/wan_br.json</filename></para>
+
+            <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/lan_br.json</filename></para>
+          </listitem>
+
+          <listitem>
+            <para>Download the FortiGate VNF Firewall basic configuration from
+            the Enea Portal, copy it into the
+            <literal>&lt;AF-TH-install-dir&gt;/vnf_config/fortigateImage</literal>
+            directory and rename it to
+            <filename>fortigateFW.conf</filename>.</para>
+          </listitem>
+
+          <listitem>
+            <para>Retrieve the FortiGate VNF license file from Fortinet or the
+            Enea Portal, copy it into the
+            <literal>&lt;AF-TH-install-dir&gt;/vnf_config/fortigateImage</literal>
+            directory and rename it to
+            <filename>fortigateLicense.lic</filename>.</para>
+
+            <para>For more details, please refer to:</para>
+
+            <itemizedlist>
+              <listitem>
+                <para>The "FortiGate VNF as a Firewall" chapter from the Enea
+                NFV Access Example Use-cases manual.</para>
+              </listitem>
+
+              <listitem>
+                <para>The "Python Unit-Test Suite" chapter from the Enea NFV
+                Access Automation Framework and Test Harness User
+                Guide.</para>
+              </listitem>
+            </itemizedlist>
+          </listitem>
+        </itemizedlist>
+
+        <para><emphasis role="bold">Action:</emphasis> Run the
+        <filename>deployFortigateFWScenario.yml</filename> Ansible Playbook
+        with the <literal>&lt;Device-name&gt;</literal> as extra-vars:
+        <programlisting>ansible-playbook playbooks/unittestSuiteTest/deployFortigateFWScenario.yml \
+-e "device=&lt;Device-name&gt;"</programlisting></para>
+
+        <para><emphasis role="bold">Result:</emphasis> Output of the test case
+        run using the Test Harness: <programlisting># unittestSuite Deploy Test task result
+FortigateFW Scenario deployed successfully!</programlisting></para>
+
+        <para><emphasis role="bold">Cleanup:</emphasis> Run the
+        <filename>cleanupFortigateFWScenario.yml</filename> Ansible Playbook
+        with the <literal>&lt;Device-name&gt;</literal> as extra-vars:
+        <programlisting>ansible-playbook playbooks/unittestSuiteTest/cleanupFortigateFWScenario.yml \
+-e "device=&lt;Device-name&gt;"</programlisting></para>
+      </section>
+    </section>
+
+    <section id="chained_vnf">
+      <title>chainedVNFsService</title>
+
+      <para><emphasis role="bold">Description:</emphasis> This sample test
+      case corresponds to the "VNF Chaining Example Use-case" from the Enea
+      NFV Access Example Use-cases manual.</para>
+
+      <para>For details please refer to:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/chainedVNFsService/chainedVNFsService.yml</filename></para>
+        </listitem>
+
+        <listitem>
+          <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/chainedVNFsService/testChainedVNFsService.yml</filename></para>
+        </listitem>
+
+        <listitem>
+          <para><filename>&lt;AF-TH-install-dir&gt;/playbooks/chainedVNFsService/cleanupChainedVNFsService.yml</filename></para>
+        </listitem>
+      </itemizedlist>
+
+      <para><emphasis role="bold">Preconditions:</emphasis></para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Add the Fortigate VNF Image
+          (<filename>fortios.qcow2</filename>) to the
+          <literal>vnf_image</literal> folder.</para>
+        </listitem>
+
+        <listitem>
+          <para>Add the Juniper vSRX VNF Image
+          (<filename>juniper.qcow2</filename>) to the
+          <literal>vnf_image</literal> folder.</para>
+        </listitem>
+
+        <listitem>
+          <para>Devices JSON configuration files are created, e.g.:</para>
+
+          <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/&lt;Device-name&gt;.json</filename>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Add device settings in the <literal>hosts</literal> Ansible
+          inventory file under <literal>[chainedVNFs]</literal>, keeping both
+          devices, the "site1" and "site2" entries, and updating the values
+          for <literal>ansible_host</literal>,
+          <literal>ansible_port</literal>, <literal>ansible_user</literal> and
+          <literal>ansible_pass</literal>, as applicable.</para>
+
+          <para><emphasis role="bold">Example:</emphasis></para>
+
+          <para><programlisting>site1 ansible_host=172.24.14.157 ansible_port=22 ansible_user=root \
+ansible_pass=root</programlisting></para>
+
+          <para><programlisting>site2 ansible_host=172.24.14.50 ansible_port=22 ansible_user=root \
+ansible_pass=root</programlisting></para>
+        </listitem>
+
+        <listitem>
+          <para>NIC JSON configuration files are created for each of the
+          devices, where <literal>mgmt_nic</literal> is connected to the DHCP
+          from the Lab Network and <literal>wan_nic</literal> is connected
+          back to back to the other device:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/mgmt_nic.json</filename></para>
+            </listitem>
+
+            <listitem>
+              <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/wan_nic.json</filename></para>
+            </listitem>
+
+            <listitem>
+              <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/lan_nic.json</filename></para>
+            </listitem>
+          </itemizedlist>
+        </listitem>
+
+        <listitem>
+          <para>Bridge JSON configuration files are created for each of the
+          devices:</para>
+
+          <itemizedlist>
+            <listitem>
+              <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/vnf_mgmt_br.json</filename></para>
+            </listitem>
+
+            <listitem>
+              <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/sfc_br.json</filename></para>
+            </listitem>
+
+            <listitem>
+              <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/wan_br.json</filename></para>
+            </listitem>
+
+            <listitem>
+              <para><filename>&lt;AF-TH-install-dir&gt;/lab_config/&lt;Device-name&gt;/lan_br.json</filename></para>
+            </listitem>
+          </itemizedlist>
+
+          <para>Note that sample configuration files needed for devices' NICs
+          and bridges can be found in:
+          <literal>&lt;AF-TH-install-dir&gt;/lab_config/inteld1521-1</literal>
+          and
+          <literal>&lt;AF-TH-install-dir&gt;/lab_config/inteld1521-2</literal>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Download the FortiGate VNF Firewall basic configuration files
+          from the Enea Portal (<filename>FortiFW-Site1.conf</filename> and
+          <filename>FortiFW-Site2.conf</filename>), and copy them into the
+          <literal>&lt;AF-TH-install-dir&gt;/vnf_config/fortigateFWImage</literal>
+          directory.</para>
+        </listitem>
+
+        <listitem>
+          <para>Retrieve the FortiGate VNF license from Fortinet or the Enea
+          Portal, copy it into the
+          <literal>&lt;AF-TH-install-dir&gt;/vnf_config/fortigateFWImage</literal>
+          directory and rename it to
+          <filename>fortigateLicense.lic</filename>.</para>
+        </listitem>
+
+        <listitem>
+          <para>Download the Juniper vSRX basic configuration files from the
+          Enea Portal (<filename>vSRX-Site1.iso</filename> and
+          <filename>vSRX-Site2.iso</filename>), and copy them into the
+          <literal>&lt;AF-TH-install-dir&gt;/vnf_config/junipervSRXImage</literal>
+          directory.</para>
+        </listitem>
+
+        <listitem>
+          <para>Download <filename>vSRX-domain-update-script</filename> from
+          the Enea Portal and copy it into the
+          <literal>junipervSRXImage</literal> directory.</para>
+
+          <para>Please refer to the "VNF Chaining Example Use-case" chapter
+          from the Enea NFV Access Example Use-cases manual for additional
+          information about the preconditions.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para><emphasis role="bold">Action:</emphasis> Run the
+      <filename>chainedVNFsService.yml</filename> Ansible Playbook as follows:
+      <programlisting>ansible-playbook playbooks/chainedVNFsService/chainedVNFsService.yml \
+-e "site1=inteld1521-1 site2=inteld1521-2 arch=XeonD"</programlisting></para>
+
+      <para>Note that "arch" may either be { XeonD | AtomC } depending on the
+      target set chosen.</para>
+
+      <para><emphasis role="bold">Result:</emphasis> Output of the test case
+      run using the Test Harness: <programlisting># testChainedVNFsService task result
+******************************************************************************
+ * site1 - changed=False ----------------------------------------------
+----
+&lt;site1_lan-ip&gt; ---&gt; &lt;site2_lan-ip&gt;
+LAN-to-LAN connectivity (through VPN tunnel)tested successfully!</programlisting></para>
+
+      <para><emphasis role="bold">Cleanup:</emphasis> Run the
+      <filename>cleanupChainedVNFsService.yml</filename> Ansible Playbook as
+      follows: <programlisting>ansible-playbook playbooks/chainedVNFsService/cleanupChainedVNFsService.yml \
+-e "site1=inteld1521-1 site2=inteld1521-2 arch=XeonD"</programlisting></para>
+    </section>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-system-test-specification/swcomp.mk b/doc/book-enea-nfv-access-system-test-specification/swcomp.mk
new file mode 100755
index 0000000..aea86ca
--- /dev/null
+++ b/doc/book-enea-nfv-access-system-test-specification/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-system-test-specification
+BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) System Test Specification"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)