24 files changed, 1567 insertions, 2 deletions

diff --git a/doc/Makefile b/doc/Makefile
index 0514408..befba1e 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -50,14 +50,15 @@ 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-reference-guide-intel book-enea-nfv-access-release-info
+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
 #  COMPONENTS += 
-#book-enea-linux-eclipse-open-source (as of 13.04.2017 this is not needed) 
+#book-enea-linux-eclipse-open-source 
 #book-enea-nfv-access-dev-hardening-guide
 #book-enea-nfv-access-esdk-open-source
 #book-enea-nfv-access-guide
 #book-enea-nfv-access-sdk-open-source
 #book-enea-nfv-access-user-hardening-guide 
+#book-enea-nfv-access-reference-guide-intel
 
 #COMPONENTS := $(shell ls -d book-enea* )
 
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/book.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/book.xml
new file mode 100644
index 0000000..7fbbadb
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/book.xml
@@ -0,0 +1,30 @@
+<?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_vnf_onboarding_guide">
+  <title><trademark class="registered">Enea</trademark> NFV Access VNF Onboarding 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="introduction.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />                               
+
+  <xi:include href="vnf_onboarding.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />
+
+  <xi:include href="instantiation.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+                          
+  <xi:include href="vnf_configurations.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" />                               
+
+</book>
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/eltf_params_template.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/eltf_params_template.xml
new file mode 100644
index 0000000..eaa7ebd
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-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-vnf-onboarding-guide/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/eltf_params_updated.xml
new file mode 100644
index 0000000..feabc9f
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-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-vnf-onboarding-guide/doc/eltf_params_updated_template_how_to_use.txt b/doc/book-enea-nfv-access-vnf-onboarding-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-vnf-onboarding-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-vnf-onboarding-guide/doc/images/6wind_cloudinit.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/6wind_cloudinit.png
new file mode 100755
index 0000000..36264e1
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/6wind_cloudinit.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/add_output.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/add_output.png
new file mode 100755
index 0000000..e814d3d
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/add_output.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/coss_vnf_inst.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/coss_vnf_inst.png
new file mode 100755
index 0000000..862b408
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/coss_vnf_inst.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/cosstream_cloudinit.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/cosstream_cloudinit.png
new file mode 100755
index 0000000..2a31213
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/cosstream_cloudinit.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/create_interface.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/create_interface.png
new file mode 100755
index 0000000..5344a9a
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/create_interface.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/create_ovs_bridge.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/create_ovs_bridge.png
new file mode 100755
index 0000000..ec8882f
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/create_ovs_bridge.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_cloudinit.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_cloudinit.png
new file mode 100755
index 0000000..7ce7821
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_cloudinit.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_port1.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_port1.png
new file mode 100755
index 0000000..9eee61c
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_port1.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_port2.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_port2.png
new file mode 100755
index 0000000..9d97543
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_port2.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_port3.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_port3.png
new file mode 100755
index 0000000..1f33ea7
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/fortios_port3.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/main_net_int.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/main_net_int.png
new file mode 100755
index 0000000..97e5de6
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/main_net_int.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/onboard_6wind.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/onboard_6wind.png
new file mode 100755
index 0000000..a0d8210
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/onboard_6wind.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/onboard_clav_coss.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/onboard_clav_coss.png
new file mode 100755
index 0000000..5704d6a
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/onboard_clav_coss.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/onboard_fortios.png b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/onboard_fortios.png
new file mode 100755
index 0000000..3c6b2de
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/images/onboard_fortios.png
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml
new file mode 100644
index 0000000..bb0e28b
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/instantiation.xml
@@ -0,0 +1,126 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="instantiation">
+  <title>Instantiation</title>
+
+  <para>When a VNF is onboarded and available in the VNF catalog, it can be
+  instantiated (deployed) on connected uCPEs. The instantiation wizard uses
+  the configurations provided when the VNF is onboarded, as a template for
+  instantiation. Before the instantiation, however, the uCPE needs to be
+  prepared:</para>
+
+  <orderedlist>
+    <listitem>
+      <para>Physical NICs used with the VNF directly (through SR-IOV or PCI
+      Passthrough) or indirectly (through bridges) need to be configured
+      (Device-&gt;Configuration-&gt;OpenVSwitch-&gt;Host Interfaces).</para>
+
+      <note>
+        <para>Before configuring any physical NICs determine which is used for
+        managing the device. Altering the configuration of a NIC may cause
+        connectivity issues.</para>
+      </note>
+    </listitem>
+
+    <listitem>
+      <para>Add any needed bridges, connecting them to the physical NICs
+      previously configured or making them integration bridges (without
+      physical NIC) for service chaining.</para>
+    </listitem>
+  </orderedlist>
+
+  <para>Once the physical NICs and bridges are configured, the VNF can be
+  instantiated using the Instantiation Wizard.</para>
+
+  <section id="using_wiz">
+    <title>Using the Instantiation Wizard</title>
+
+    <orderedlist>
+      <listitem>
+        <para>Enter the Instantiation Wizard by accessing VNF-&gt;Instances
+        and hitting <literal>Add</literal>.</para>
+      </listitem>
+
+      <listitem>
+        <para>Fill out the following mandatory fields:</para>
+
+        <itemizedlist spacing="compact">
+          <listitem>
+            <para>Name (a descriptive name).</para>
+          </listitem>
+
+          <listitem>
+            <para>Target (the uCPE device to instantiate the VNF on).</para>
+          </listitem>
+
+          <listitem>
+            <para>Networking Configuration:</para>
+
+            <itemizedlist spacing="compact">
+              <listitem>
+                <para>Connect each configured NIC with a bridge, SR-IOV or PCI
+                Passthrough.</para>
+              </listitem>
+
+              <listitem>
+                <para>Set up each NIC with a driver method (DPDK or
+                e1000).</para>
+              </listitem>
+            </itemizedlist>
+
+            <note>
+              <para>All configured NICs must be set up before instantiating a
+              VNF. Failure to do so will end in a failed instantiation.</para>
+            </note>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Add VNF specific configuration by uploading a Cloud-Init file
+        (when the Cloud-Init is used).</para>
+      </listitem>
+
+      <listitem>
+        <para>Add any VNF specific files (e.g license files).</para>
+      </listitem>
+
+      <listitem>
+        <para>Hit the instantiation button to deploy the VNF.</para>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section id="enter_console">
+    <title>Entering the VNF Console</title>
+
+    <para>Once the VNF is deployed, the VNF console can be entered using SSH
+    and virsh commands. The VNF Console is a typical starting point for
+    determining a successful deployment and configuring a VNF beyond Day
+    Zero.</para>
+
+    <orderedlist spacing="compact">
+      <listitem>
+        <para>SSH to the uCPE device from the Enea uCPE Manager
+        (Device-&gt;SSH) with default user and password:
+        <literal>root</literal>.</para>
+      </listitem>
+
+      <listitem>
+        <para>In SSH:</para>
+
+        <orderedlist>
+          <listitem>
+            <para>Use the <command>virsh list</command> command to list all
+            running VNFs and to determine the VNF's instance number.</para>
+          </listitem>
+
+          <listitem>
+            <para>Use the <command>virsh console &lt;instance
+            number&gt;</command> command to enter the VNF specific
+            console.</para>
+          </listitem>
+        </orderedlist>
+      </listitem>
+    </orderedlist>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/introduction.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/introduction.xml
new file mode 100644
index 0000000..cee9fcb
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/introduction.xml
@@ -0,0 +1,90 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="intro">
+  <title>Introduction</title>
+
+  <para>This document describes the process of onboarding a new VNF onto the
+  Enea uCPE Manager so that it can subsequently instantiate and run the VNF on
+  one or more uCPEs.</para>
+
+  <section id="prereq">
+    <title>Prerequisites</title>
+
+    <para>In order to onboard a new VNF into the Enea uCPE Manager VNF
+    catalog, specific prerequisites must be known and met:</para>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para>Access to the VNF QCOW2 image.</para>
+      </listitem>
+
+      <listitem>
+        <para>VNF Flavor information:</para>
+
+        <itemizedlist spacing="compact">
+          <listitem>
+            <para>Amount of RAM required.</para>
+          </listitem>
+
+          <listitem>
+            <para>Number of vCPUs needed.</para>
+          </listitem>
+
+          <listitem>
+            <para>Size of disk required.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Network configuration:</para>
+
+        <itemizedlist spacing="compact">
+          <listitem>
+            <para>Number of Network Interfaces to be used for the VNF.</para>
+          </listitem>
+
+          <listitem>
+            <para>The roles of each network interface (MGMT, WAN, LAN).</para>
+          </listitem>
+
+          <listitem>
+            <para>Driver access for each Network Interface (DPDK, SR-IOV or
+            PCI Passthrough).</para>
+          </listitem>
+
+          <listitem>
+            <para>IP Configuration for each Network Interface (DHCP, Static
+            IP).</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Day zero configuration method for the VNF:</para>
+
+        <itemizedlist spacing="compact">
+          <listitem>
+            <para>Cloud-Init, ConfigDrive, NoCloud, raw ISO or none.</para>
+          </listitem>
+
+          <listitem>
+            <para>Cloud-Init mount method (CDROM or disk).</para>
+          </listitem>
+
+          <listitem>
+            <para>Cloud-Init file structure to be used.</para>
+          </listitem>
+
+          <listitem>
+            <para>Availability of a VNF specific day-zero configuration for
+            setting up the VNFs day zero settings.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+    </itemizedlist>
+
+    <para>All this information is provided with each VNF's Getting Started
+    Guide, with configurations typically specific to the intended use case of
+    the VNF.</para>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/vnf_configurations.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/vnf_configurations.xml
new file mode 100644
index 0000000..3b37328
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/vnf_configurations.xml
@@ -0,0 +1,378 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="vnf_configs">
+  <title>Detailed VNF Configurations</title>
+
+  <para><remark>Perhaps an introduction is needed</remark></para>
+
+  <section id="wind_turbo_router">
+    <title>6Wind Turbo Router</title>
+
+    <remark>Perhaps an introduction is needed</remark>
+
+    <section id="onboard_turbo">
+      <title>Onboarding</title>
+
+      <para>The required fields and their specifications, need to be filled
+      with the following information in order onboard the VNF:</para>
+
+      <table>
+        <title>Main Fields Data</title>
+
+        <tgroup cols="2">
+          <colspec align="center" />
+
+          <thead>
+            <row>
+              <entry align="center">Field</entry>
+
+              <entry align="center">Specification</entry>
+            </row>
+          </thead>
+
+          <tbody>
+            <row>
+              <entry>VM Image File</entry>
+
+              <entry>Choose the 6Wind Turbo Router QCOW image file.</entry>
+            </row>
+
+            <row>
+              <entry>Image Format</entry>
+
+              <entry>QCOW2</entry>
+            </row>
+
+            <row>
+              <entry>VNF Type Name</entry>
+
+              <entry>Turbo_Router</entry>
+            </row>
+
+            <row>
+              <entry>Description</entry>
+
+              <entry>6Winds Turbo Router</entry>
+            </row>
+
+            <row>
+              <entry>Version</entry>
+
+              <entry>1.0</entry>
+            </row>
+
+            <row>
+              <entry>Memory in MB</entry>
+
+              <entry>6244</entry>
+            </row>
+
+            <row>
+              <entry>Nr. of CPUs</entry>
+
+              <entry>3</entry>
+            </row>
+
+            <row>
+              <entry>Storage in GB</entry>
+
+              <entry>10</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+
+      <figure>
+        <title>Onboarding the 6wind VNF</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/onboard_6wind.png" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <para>Interfaces: Create 1 interface, it will instantiate the
+      DPDK.</para>
+
+      <para>Cloud Init:</para>
+
+      <figure>
+        <title>6wind Cloud-Init</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/6wind_cloudinit.png" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <para>Properties: There are no specific configurations needed.</para>
+    </section>
+
+    <section id="instant_turbo">
+      <title>Instantiation</title>
+
+      <para>You can use a random text file as the Cloud-Init file if you do
+      not wish to set any specific details during the setup stage.
+      Alternatively, you can create a Cloud-Init configuration file according
+      to 6wind documentation, to change the root password:<programlisting>#cloud-config
+chpasswd:
+list: |
+root:karm</programlisting>Interfaces: Set up 1 interface (the DPDK with the
+      preconfigured bridge).</para>
+    </section>
+  </section>
+
+  <section id="clav_cosstream">
+    <title>Clavister CosStream</title>
+
+    <remark>Perhaps an introduction is needed</remark>
+
+    <section id="costream_onbr">
+      <title>Onboarding</title>
+
+      <para>The required fields and their specifications, need to be filled
+      with the following information in order onboard the VNF:</para>
+
+      <table>
+        <title>Main Fields Data</title>
+
+        <tgroup cols="2">
+          <colspec align="center" />
+
+          <thead>
+            <row>
+              <entry align="center">Field</entry>
+
+              <entry align="center">Specification</entry>
+            </row>
+          </thead>
+
+          <tbody>
+            <row>
+              <entry>VM Image File</entry>
+
+              <entry>clavister-cos-stream-3.20.00.25-virtual-x64-generic.qcow2</entry>
+            </row>
+
+            <row>
+              <entry>Image Format</entry>
+
+              <entry>QCOW2</entry>
+            </row>
+
+            <row>
+              <entry>VNF Type Name</entry>
+
+              <entry>CosStream</entry>
+            </row>
+
+            <row>
+              <entry>Description</entry>
+
+              <entry>Clavister CosStream</entry>
+            </row>
+
+            <row>
+              <entry>Version</entry>
+
+              <entry>1.0</entry>
+            </row>
+
+            <row>
+              <entry>Memory in MB</entry>
+
+              <entry>1024</entry>
+            </row>
+
+            <row>
+              <entry>Nr. of CPUs</entry>
+
+              <entry>4</entry>
+            </row>
+
+            <row>
+              <entry>Storage in GB</entry>
+
+              <entry>20</entry>
+            </row>
+          </tbody>
+        </tgroup>
+      </table>
+
+      <para><figure>
+          <title>Onboarding the CosStream VNF - Infertaces
+          Configuration</title>
+
+          <mediaobject>
+            <imageobject>
+              <imagedata align="center" fileref="images/onboard_clav_coss.png"
+                         scale="60" />
+            </imageobject>
+          </mediaobject>
+        </figure><figure>
+          <title>Cloud-Init Configuration</title>
+
+          <mediaobject>
+            <imageobject>
+              <imagedata align="center"
+                         fileref="images/cosstream_cloudinit.png" />
+            </imageobject>
+          </mediaobject>
+        </figure>Properties: There are no specific configurations
+      needed.</para>
+    </section>
+
+    <section id="costream_inst">
+      <title>Instantiation</title>
+
+      <para>Networking Support: In order to run Clavister CosStream, you must
+      do the following on the Clavister host:<programlisting>create if 0000:07:00.1 igb_uio
+create bridge ovsbr0 0000:07:00.1</programlisting>Alternatively, use the uCPE
+      Manager to create the interface and bridge prior to instantiating the
+      VNF:</para>
+
+      <figure>
+        <title>Create an interface</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/create_interface.png" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <figure>
+        <title>Create an OVS Bridge</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/create_ovs_bridge.png"
+                       scale="70" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <figure>
+        <title>Instantiate the VNF</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/coss_vnf_inst.png"
+                       scale="70" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <figure>
+        <title>Adding a main Network Interface</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/main_net_int.png"
+                       scale="70" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <figure>
+        <title>Adding Output</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/add_output.png"
+                       scale="70" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+    </section>
+  </section>
+
+  <section id="fortios">
+    <title>Fortios</title>
+
+    <remark>Perhaps an introduction is needed</remark>
+
+    <section id="fortios_onbr">
+      <title>Onboarding</title>
+
+      <para>To onboard this VNF three interfaces need to be created:</para>
+
+      <figure>
+        <title>Onboarding Fortios - Interface Creation</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/onboard_fortios.png"
+                       scale="60" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <para>Cloud Init: Fortios requires a license file in addition to a user
+      data Cloud-Init configuration file:</para>
+
+      <figure>
+        <title>Adding the License file</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/fortios_cloudinit.png"
+                       scale="60" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+    </section>
+
+    <section id="fortios_inst">
+      <title>Instantiation</title>
+
+      <para>This VNF requires two Cloud-Init files to be specified:</para>
+
+      <itemizedlist spacing="compact">
+        <listitem>
+          <para>Cloud-init.txt</para>
+        </listitem>
+
+        <listitem>
+          <para>License.txt</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>Three ports also need to be created:</para>
+
+      <figure>
+        <title>Port 1</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/fortios_port1.png"
+                       scale="60" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <figure>
+        <title>Port 2</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/fortios_port2.png"
+                       scale="60" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+
+      <figure>
+        <title>Port 3</title>
+
+        <mediaobject>
+          <imageobject>
+            <imagedata align="center" fileref="images/fortios_port3.png"
+                       scale="60" />
+          </imageobject>
+        </mediaobject>
+      </figure>
+    </section>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/vnf_onboarding.xml b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/vnf_onboarding.xml
new file mode 100644
index 0000000..5759f7b
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-guide/doc/vnf_onboarding.xml
@@ -0,0 +1,173 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<chapter id="vnf_onboard">
+  <title>VNF Onboarding</title>
+
+  <para>The onboarding of a VNF means adding it to the Enea uCPE Manager VNF
+  Catalog and preparing it for instantiation (deployment on connected uCPEs).
+  This is accomplished using the Enea uCPE Manager Onboarding Wizard, a
+  graphical user interface specifically designed to make VNF onboarding simple
+  and fast.</para>
+
+  <para>Typically, the VNF's Getting Started Guide contains all necessary
+  information needed to onboard a VNF using the Onboarding Wizard. This
+  present guide however, provides a number of examples of how to onboard
+  specific commercial VNFs.</para>
+
+  <para>The following sections detail the basic steps needed to successfully
+  onboard a VNF in the Enea uCPE Manager.</para>
+
+  <section id="retrieve_art">
+    <title>Retrieving Artifacts</title>
+
+    <para>The user must first retrieve the necessary artifacts from the VNF
+    vendor:</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Download the VNF from the commercial vendor.</para>
+      </listitem>
+
+      <listitem>
+        <para>Get any VNF specific license from the VNF vendor.</para>
+
+        <note>
+          <para>There are no standard ways of managing VNF licenses, therefore
+          no general guidelines can be provided. One example of license
+          handling that can be employed in the uCPE Manager is the adding of a
+          license during the Cloud-Init setup. The ConfigDrive value is
+          provided in the Fortios specific guidelines.</para>
+        </note>
+      </listitem>
+
+      <listitem>
+        <para>Get access to the VNF specific VNF Manager for day 1 and 2
+        configuration (in cloud or for local deployment).</para>
+      </listitem>
+
+      <listitem>
+        <para>Procure the Getting Started Guide from the VNF vendor,
+        preferably for KVM deployment for VNF specific configuration
+        information.</para>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section id="onboard_prep">
+    <title>Preparation</title>
+
+    <para>Once all needed downloadables, documentation and more have been
+    attained, preparation for onboarding must be completed:</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Determine the use-case and performance requirements of the VNF
+        you wish to deploy.</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>This decides what resources the VNF is configured for, along
+            with networking and day zero configurations.</para>
+
+            <para>Generally, the Getting Started Guide for the VNF provides
+            guidelines for resource allocation, but since performance is
+            dependent on hardware capacity, the right resource allocation for
+            deployment is typically determined through benchmarking.</para>
+          </listitem>
+
+          <listitem>
+            <para>Determine the amount of hardware resources needed for the
+            VNF (RAM, CPUs and Disk size).</para>
+          </listitem>
+
+          <listitem>
+            <para>Determine how many Network Interfaces the VNF shall
+            use.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Determine the day zero configuration method from the VNF Getting
+        Started guidelines.</para>
+
+        <note>
+          <para>For many VNFs, day zero configuration can be skipped in early
+          onboarding efforts when automation is not of importance.</para>
+        </note>
+      </listitem>
+
+      <listitem>
+        <para>Determine any requirements needed by the Cloud-Init file
+        structure and the content needed for the VNF when Cloud-Init is
+        used.</para>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section id="onboarding">
+    <title>Onboarding the VNF</title>
+
+    <orderedlist>
+      <listitem>
+        <para>Enter the Enea uCPE Manager and choose VNF-&gt;Descriptors in
+        the GUI.</para>
+      </listitem>
+
+      <listitem>
+        <para>Click <literal>Onboard</literal> to start the onboarding
+        procedure.</para>
+      </listitem>
+
+      <listitem>
+        <para>Fill in all mandatory fields in the popup menu: Name, Image,
+        RAM, CPUs, Disk.</para>
+      </listitem>
+
+      <listitem>
+        <para>Define the VNF's Network Interfaces and give them descriptive
+        names.</para>
+      </listitem>
+
+      <listitem>
+        <para>Configure the Cloud-Init settings, starting with the
+        Datasource:</para>
+
+        <itemizedlist spacing="compact">
+          <listitem>
+            <para>Choose <literal>None</literal> if Cloud-Init is not
+            used.</para>
+          </listitem>
+
+          <listitem>
+            <para>Choose <literal>ConfigDrive</literal>,
+            <literal>NoCloud</literal> or <literal>ISO</literal> depending on
+            the VNF specific Cloud-Init implementation.</para>
+          </listitem>
+
+          <listitem>
+            <para>Choose the Cloud-Init mount method based on the VNF specific
+            Cloud-Init implementation.</para>
+          </listitem>
+
+          <listitem>
+            <para>Configure any VNF specific Cloud-Init files according to VNF
+            specific documentation.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Additional Properties (in the Properties Tab) are typically not
+        needed and can be ignored.</para>
+      </listitem>
+
+      <listitem>
+        <para>Click <literal>Onboard</literal> to add the VNF to the Enea uCPE
+        Manager VNF Catalog.</para>
+      </listitem>
+    </orderedlist>
+
+    <para>When the onboarding is complete, the VNF will appear in the VNF
+    Catalog and can be used for deploying services on the uCPEs.</para>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-vnf-onboarding-guide/swcomp.mk b/doc/book-enea-nfv-access-vnf-onboarding-guide/swcomp.mk
new file mode 100755
index 0000000..2e66101
--- /dev/null
+++ b/doc/book-enea-nfv-access-vnf-onboarding-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-vnf-onboarding-guide
+BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access $(PROD_VER) VNF Onboarding Guide"
+BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)