Renaming all EL7 virt profile titles to "Enea NFV Access"

LXCR-7844 LXCR-7844 Redo the chapter structure for EL Virtualization Guide

Signed-off-by: Miruna Paun <Miruna.Paun@enea.com>

38 files changed, 1180 insertions, 99 deletions

diff --git a/doc/Makefile b/doc/Makefile
index f99ff90..50830de 100644
--- a/doc/Makefile
+++ b/doc/Makefile
@@ -1,3 +1,4 @@
+#2017-06-29 Converted EL7 virtualization profile to first version of ENFV Access Platform
 #2017-04-13 Created first version of virtualization profile
 
 #Path to this subsystem's root directory
@@ -20,16 +21,16 @@ TMPCLONEROOT_MANIFEST := $(TMPCLONEROOT)/manifest
 
 
 # ******************* AutoGenerated chapters from template and target READMEs *******
-BUILDBOOT_XML       := book-enea-linux-release-info/doc/build_boot_generated.xml
-BUILDBOOT_TEMPLATE  := book-enea-linux-release-info/doc/build_boot_template.xml
+BUILDBOOT_XML       := book-enea-nfv-access-platform-release-info/doc/build_boot_generated.xml
+BUILDBOOT_TEMPLATE  := book-enea-nfv-access-platform-release-info/doc/build_boot_template.xml
 
-PKGDIFF_GEN_XML     := book-enea-linux-release-info/doc/pkgdiff_generated.xml
-JIRA_ISSUES_GEN_XML := book-enea-linux-release-info/doc/jiraissues_generated.xml
+PKGDIFF_GEN_XML     := book-enea-nfv-access-platform-release-info/doc/pkgdiff_generated.xml
+JIRA_ISSUES_GEN_XML := book-enea-nfv-access-platform-release-info/doc/jiraissues_generated.xml
 
-MACHINE_LIST_XML    := book-enea-linux-release-info/doc/machine_list_generated.xml
+MACHINE_LIST_XML    := book-enea-nfv-access-platform-release-info/doc/machine_list_generated.xml
 
-ELTF_PARAMS_TEMPLATE := book-enea-linux-release-info/doc/eltf_params_template.xml
-ELTF_PARAMS_UPDATED  := book-enea-linux-release-info/doc/eltf_params_updated.xml
+ELTF_PARAMS_TEMPLATE := book-enea-nfv-access-platform-release-info/doc/eltf_params_template.xml
+ELTF_PARAMS_UPDATED  := book-enea-nfv-access-platform-release-info/doc/eltf_params_updated.xml
 
 
 
@@ -47,7 +48,7 @@ DOCBOOK_TO_BOOKDIR ?= yes
 DOCBOOK_CLEANTMP ?= yes
 
 #Components (books) in this subsystem. Now use all books found here
-#  COMPONENTS := book-enea-linux-release-info book-enea-linux-open-source
+#  COMPONENTS := book-enea-nfv-access-platform-release-info book-enea-linux-open-source
 #  COMPONENTS += book-enea-linux-eclipse-open-source (as of 13.04.2017 this is not needed)
 COMPONENTS := $(shell ls -d book-enea* )
 
diff --git a/doc/book-enea-linux-virtualization-guide/doc/basic_configuration_guide.xml b/doc/book-enea-linux-virtualization-guide/doc/basic_configuration_guide.xml
deleted file mode 100644
index e28f7b1..0000000
--- a/doc/book-enea-linux-virtualization-guide/doc/basic_configuration_guide.xml
+++ /dev/null
@@ -1,17 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
-"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
-<chapter id="basic-configuration">
-  <title>Basic Configuration</title>
-
-  <para>To properly make use of the all the features offered in this release,
-  a basic configuration must be done beforehand, to ensure all required
-  settings are in working order. Below you will find details on how to
-  proceed.</para>
-
-  <para>:<remark>INFO: The programlisting below is a parameters in
-  eltf_params_updated.xml with ID: "eltf-prereq-apt-get-command-host". If
-  multiple hosts are supported, store the commands for each host in the same
-  programlisting with empty lines between each - the comment with the FULL
-  HOST name and version is essential.</remark></para>
-</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-linux-virtualization-guide/doc/book.xml b/doc/book-enea-linux-virtualization-guide/doc/book.xml
deleted file mode 100644
index 226a064..0000000
--- a/doc/book-enea-linux-virtualization-guide/doc/book.xml
+++ /dev/null
@@ -1,15 +0,0 @@
-<?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" [
-]>
-<book id="book_enea_linux_virtualization_guide">
-  <title><trademark class="registered">Enea</trademark> Linux Virtualization Guide</title>
-  <subtitle>Release Version
-  <xi:include href="eltf_params_updated.xml" xpointer="element(EneaLinux_REL_VER/1)"
-         xmlns:xi="http://www.w3.org/2001/XInclude" /></subtitle>
-  <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="basic_configuration_guide.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  <xi:include href="workflow.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  <xi:include href="../../s_docbuild/template/docsrc_common/contacting_enea_enea_linux.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-</book>
diff --git a/doc/book-enea-linux-virtualization-guide/doc/overview.xml b/doc/book-enea-linux-virtualization-guide/doc/overview.xml
deleted file mode 100644
index 7fd4cdf..0000000
--- a/doc/book-enea-linux-virtualization-guide/doc/overview.xml
+++ /dev/null
@@ -1,18 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
-"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
-<chapter id="overview">
-  <title>Overview</title>
-
-  <para>The Virtualization Guide available with this release of Enea Linux,
-  seeks to provide further information that will help all intended users make
-  the most out of the virtualization features.<remark>INFO <emphasis
-  role="bold">eltf_params_updated.xml</emphasis> contains many parameters in
-  the book, also in the open source books, and MUST be created FROM <emphasis
-  role="bold">eltf_params_template.xml</emphasis>. The parameters are
-  automatically used in the books, via xi:include statements, similar to how
-  parameters from pardoc-distro.xml are included in the book. Read the file
-  <emphasis role="bold">eltf_params_updated_template_how_to_use.txt</emphasis>
-  for important details about formats and how to do! The idea is that ELTF
-  will auto-create/update it.</remark></para>
-</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-linux-virtualization-guide/doc/workflow.xml b/doc/book-enea-linux-virtualization-guide/doc/workflow.xml
deleted file mode 100644
index ece8ac8..0000000
--- a/doc/book-enea-linux-virtualization-guide/doc/workflow.xml
+++ /dev/null
@@ -1,24 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
-"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
-<chapter id="workflow">
-  <title>Workflow</title>
-
-  <para>Enea Linux is available as both pre-built binary images and source
-  code. Both serve a specific purpose and each have their advantages. However,
-  using the pre-built binary images allows for getting up and running faster.
-  Please refer to the sections below for details on how to get Enea Linux as
-  pre-built binary images or source code.</para>
-
-  <section id="relinfo-getting-pre-built-images">
-    <title>Getting Pre-built Binaries</title>
-
-    <para>Enea Linux pre-built binaries are available for download on <ulink
-    url="https://portal.enea.com/login/?redirect_to=https%3A%2F%2Fportal.enea.com%2F">Enea
-    Download Portal</ulink>. Log in using the credentials provided. Using the
-    menu, browse to the <emphasis role="bold">Linux</emphasis> section. You
-    will now have access to the <emphasis role="bold">Files</emphasis> section
-    and the <emphasis role="bold">Online Documentation</emphasis>
-    section.</para>
-  </section>
-</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-platform-guide/doc/benchmarks.xml b/doc/book-enea-nfv-access-platform-guide/doc/benchmarks.xml
new file mode 100644
index 0000000..0db4fa4
--- /dev/null
+++ b/doc/book-enea-nfv-access-platform-guide/doc/benchmarks.xml
@@ -0,0 +1,14 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="workflow">
+  <title>Benchmarks</title>
+
+  <para></para>
+
+  <section id="relinfo-getting-pre-built-images">
+    <title></title>
+
+    <para></para>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-platform-guide/doc/book.xml b/doc/book-enea-nfv-access-platform-guide/doc/book.xml
new file mode 100644
index 0000000..9b0cc4a
--- /dev/null
+++ b/doc/book-enea-nfv-access-platform-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" [
+]>
+<book id="book_enea_nfv_access_platform_guide">
+  <title><trademark class="registered">Enea</trademark> NFV Access Platform Guide</title>
+  <subtitle>Release Version
+        <xi:include href="eltf_params_updated.xml" xpointer="element(EneaLinux_REL_VER/1)"
+        xmlns:xi="http://www.w3.org/2001/XInclude" /></subtitle>
+        <xi:include href="../../s_docbuild/template/docsrc_common/bookinfo_userdoc.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="platform_overview.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="getting_started.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="hypervisor_virtualization.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="container_virtualization.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="ovs.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="dpdk.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="benchmarks.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="using_nfv_access_platform_sdks.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+        <xi:include href="../../s_docbuild/template/docsrc_common/contacting_enea_enea_linux.xml"
+                xmlns:xi="http://www.w3.org/2001/XInclude" />
+</book>
diff --git a/doc/book-enea-nfv-access-platform-guide/doc/container_virtualization.xml b/doc/book-enea-nfv-access-platform-guide/doc/container_virtualization.xml
new file mode 100644
index 0000000..6f74061
--- /dev/null
+++ b/doc/book-enea-nfv-access-platform-guide/doc/container_virtualization.xml
@@ -0,0 +1,8 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter condition="hidden" id="workflow">
+  <title>Container Virtualization</title>
+
+  <para></para>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-platform-guide/doc/dpdk.xml b/doc/book-enea-nfv-access-platform-guide/doc/dpdk.xml
new file mode 100644
index 0000000..91b36d3
--- /dev/null
+++ b/doc/book-enea-nfv-access-platform-guide/doc/dpdk.xml
@@ -0,0 +1,118 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="dpdk">
+  <title>Data Plane Development Kit</title>
+
+  <para>The Intel Data Plane Development Kit (DPDK) is a set of user-space
+  libraries and drivers that provides a programming framework for high-speed
+  packet processing applications. The DPDK includes a number of Poll Mode
+  Drivers that enable direct packet transfer between the physical NIC and
+  user-space without using interrupts, bypassing the Linux kernel network
+  stack entirely.</para>
+
+  <para>In order to take advantage of DPDK, Linux <ulink
+  url="https://www.kernel.org/doc/Documentation/vm/hugetlbpage.txt">huge
+  pages</ulink> must be enabled in the system. The allocation of huge pages
+  should preferably be done at boot time by passing parameters on the kernel
+  command line. Add the following to the kernel boot parameters:</para>
+
+  <programlisting>default_hugepagesz=1GB hugepagesz=1GB hugepages=8 hugepagesz=2M hugepages=2048</programlisting>
+
+  <para>For DPDK documentation, see <ulink
+  url="http://dpdk.org/doc/guides-17.02/index.html">http://dpdk.org/doc/guides-17.02/index.html</ulink></para>
+
+  <section id="pktgen">
+    <title>Pktgen</title>
+
+    <para>In addition to DPDK, Enea NFV Access Platform includes Pktgen, a
+    software traffic generator that is powered by the DPDK packet processing
+    framework. Pktgen can act as a transmitter or receiver and is capable of
+    generating 10Gbit wire rate traffic with 64 byte frames.</para>
+
+    <para>Pktgen is installed in <literal>/usr/share/apps/pktgen/</literal>
+    and needs to be executed from this directory.</para>
+
+    <para>For Pktgen documentation, see <ulink
+    url="http://pktgen-dpdk.readthedocs.io">http://pktgen-dpdk.readthedocs.io</ulink></para>
+  </section>
+
+  <section id="dpdk-setup">
+    <title>DPDK setup instructions</title>
+
+    <para>The following setup instructions apply to both host and
+    guest.</para>
+
+    <orderedlist>
+      <listitem>
+        <para>To make the hugepage memory available for DPDK, it must be
+        mounted:</para>
+
+        <programlisting>mkdir /mnt/huge
+mount -t hugetlbfs nodev /mnt/huge</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Load the DPDK igb_uio kernel module:</para>
+
+        <programlisting>modprobe igb_uio</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Bind the device to the igb_uio driver:</para>
+
+        <para><programlisting>dpdk-devbind --bind=igb_uio &lt;PCI device number&gt;</programlisting>The
+        DPDK provides the dpdk-devbind tool to help binding/unbinding devices
+        from specific drivers. See <ulink
+        url="http://dpdk.org/doc/guides-17.02/tools/devbind.html">http://dpdk.org/doc/guides-17.02/tools/devbind.html</ulink>
+        for more information.</para>
+      </listitem>
+    </orderedlist>
+
+    <para>To print the current status of all known network
+    interfaces:<programlisting>dpdk-devbind --status</programlisting></para>
+
+    <para>At this point the system is ready to run DPDK applications.</para>
+  </section>
+
+  <section id="dpdk-example-test-setup">
+    <title>DPDK example test setup</title>
+
+    <para>This is a simple DPDK test setup using two boards connected
+    back-to-back. One board generates traffic using the Pktgen application,
+    and the other board runs the DPDK testpmd example to forward packets back
+    on the same interface.</para>
+
+    <programlisting>Pktgen [DPDK] - Board 1 PHY &lt;--&gt; Board 2 PHY - [DPDK] testpmd</programlisting>
+
+    <orderedlist>
+      <listitem>
+        <para>Setup DPDK on both boards, following the instructions in
+        [FIXME]:</para>
+      </listitem>
+
+      <listitem>
+        <para>On board 1, start the Pktgen application:</para>
+
+        <programlisting>cd /usr/share/apps/pktgen/./pktgen -c 0x7 -n 4 --socket-mem 1024 -- -P -m "[1:2].0"</programlisting>
+
+        <para>In the Pktgen console, run:</para>
+
+        <programlisting>start 0</programlisting>
+
+        <para>The Pktgen output will display the traffic configuration and
+        statistics.</para>
+      </listitem>
+
+      <listitem>
+        <para>On board 2, start the testpmd application:</para>
+
+        <programlisting>testpmd -c 0x7 -n 4 -- --txd=512 --rxd=512  --port-topology=chained</programlisting>
+
+        <para>For more information, refer to the testpmd application user
+        guide: <ulink
+        url="http://dpdk.org/doc/guides-17.02/testpmd_app_ug/index.html">http://dpdk.org/doc/guides-17.02/testpmd_app_ug/index.html</ulink>.</para>
+      </listitem>
+    </orderedlist>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-linux-release-info/doc/eltf_params_template.xml b/doc/book-enea-nfv-access-platform-guide/doc/eltf_params_template.xml
index 278ad71..278ad71 100644
--- a/doc/book-enea-linux-release-info/doc/eltf_params_template.xml
+++ b/doc/book-enea-nfv-access-platform-guide/doc/eltf_params_template.xml
diff --git a/doc/book-enea-linux-virtualization-guide/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-platform-guide/doc/eltf_params_updated.xml
index a55234f..31a251d 100644
--- a/doc/book-enea-linux-virtualization-guide/doc/eltf_params_updated.xml
+++ b/doc/book-enea-nfv-access-platform-guide/doc/eltf_params_updated.xml
@@ -42,7 +42,7 @@ export PATH=~/bin:$PATH</programlisting></para>
     correct also compared to the "previous" REL VER in pardoc-distro.xml
     "prev_baseline".</bridgehead>
 
-    <para id="EneaLinux_REL_VER"><phrase>6</phrase></para>
+    <para id="EneaLinux_REL_VER"><phrase>1.0</phrase></para>
 
     <para id="Yocto_VER"><phrase>2.1</phrase></para>
 
diff --git a/doc/book-enea-linux-virtualization-guide/doc/eltf_params_updated_template_how_to_use.txt b/doc/book-enea-nfv-access-platform-guide/doc/eltf_params_updated_template_how_to_use.txt
index 7f1d3cb..7f1d3cb 100644
--- a/doc/book-enea-linux-virtualization-guide/doc/eltf_params_updated_template_how_to_use.txt
+++ b/doc/book-enea-nfv-access-platform-guide/doc/eltf_params_updated_template_how_to_use.txt
diff --git a/doc/book-enea-nfv-access-platform-guide/doc/getting_started.xml b/doc/book-enea-nfv-access-platform-guide/doc/getting_started.xml
new file mode 100644
index 0000000..b534e20
--- /dev/null
+++ b/doc/book-enea-nfv-access-platform-guide/doc/getting_started.xml
@@ -0,0 +1,127 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="plat-release-content">
+  <title>Getting Started with ENFV Access Platform</title>
+
+  <section id="release-content">
+    <title>NFV Access Platform Release content</title>
+
+    <para>The NFV Access Platform 1.0 Release contains along with other items,
+    documentation, pre-built kernels and images, a bootloader and a
+    SDK.</para>
+
+    <para>The directories structure is detailed below:</para>
+
+    <programlisting>-- documentation/
+   /* NFV Access Platform documentation */
+-- inteld1521/
+   /* artifacts for the host side */
+        -- deb/
+           /* deb packages */
+        -- images/
+            -- enea-image-virtualization-host
+               /* precompiled artifacts for the Host release image */
+                -- various artifacts
+            -- enea-image-virtualization-host-sdk
+               /* precompiled artifacts for the Host SDK image.
+               The SDK image contains userspace tools and kernel
+               configurations necessary for developing, debugging
+               and profiling applications and kernel modules */
+                -- various artifacts
+        -- sdk
+           /* NFV Access Platform SDK for the host */
+                -- enea-glibc-x86_64-enea-image-virtualization-host-sdk /
+                   -corei7-64-toolchain-7.0.sh
+                   /* self-extracting archive installing
+                   cross-compilation toolchain for the host */
+-- qemux86-64
+   /* artifacts for the guest side */
+        -- deb/
+           /* deb packages */
+        -- images/
+            -- enea-image-virtualization-guest
+               /* precompiled artifacts for the Guest image */
+                -- various artifacts
+        -- sdk
+           /* NFV Access Platform SDK for the guest */
+                -- enea-glibc-x86_64-enea-image-virtualization-guest-sdk /
+                   -core2-64-toolchain-7.0.sh
+                   /* self-extracting archive installing cross-compilation
+                   toolchain for the guest (QEMU x86-64) */
+</programlisting>
+
+    <para>For each combination of image and target, the following set of
+    artifacts is available:</para>
+
+    <programlisting>-- bzImage
+   /* kernel image */
+-- bzImage-&lt;target&gt;.bin
+   /* kernel image, same as above */
+-- config-&lt;target&gt;.config
+   /* kernel configuration file */
+-- core-image-minimal-initramfs-&lt;target&gt;.cpio.gz
+   /* cpio archive of the initramfs */
+-- core-image-minimal-initramfs-&lt;target&gt;.qemuboot.conf
+   /* qemu config file for the initramfs image */
+-- &lt;image-name&gt;-&lt;target&gt;.ext4
+   /* EXT4 image of the rootfs */
+-- &lt;image-name&gt;-&lt;target&gt;.hddimg
+   /* msdos filesystem containing syslinux, kernel, initrd and rootfs image */
+-- &lt;image-name&gt;-&lt;target&gt;.iso
+   /* CD .iso image */
+-- &lt;image-name&gt;-&lt;target&gt;.qemuboot.conf
+   /* qemu config file for the image */
+-- &lt;image-name&gt;-&lt;target&gt;.tar.gz
+   /* tar archive of the image */
+-- &lt;image-name&gt;-&lt;target&gt;.wic
+   /* Wic image */
+-- microcode.cpio
+   /* kernel microcode data */
+-- modules-&lt;target&gt;.tgz
+   /* external kernel modules */
+-- ovmf.*.qcow2
+   /* ovmf firmware for uefi support in qemu */
+-- rmc.db
+   /* Central RMC Database */
+-- systemd-bootx64.efi
+   /* systemd-boot EFI file */</programlisting>
+  </section>
+
+  <section id="docs">
+    <title>Included Documention</title>
+
+    <para>Enea NFV Access is provided with the following set of
+    documents:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Enea NFV Access Guide &ndash; A document describing the Enea NFV
+        Access release content and how to use it, as well as benchmark
+        results.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enea NFV Access Open Source Report &ndash; A document containing
+        the open source and license information pertaining to packages
+        provided with Enea NFV Access 1.0.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enea NFV Access Test Report &ndash; The document that summarizes
+        the test results for the Enea NFV Access release.</para>
+      </listitem>
+
+      <listitem>
+        <para>Enea NFV Access Security Report &ndash; The document that lists
+        all security fixes included in the Enea NFV Access 1.0 release.</para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section id="prebuilt-artifacts">
+    <title>How to use Prebuilt Artifacts</title>
+
+    <para></para>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-platform-guide/doc/hypervisor_virtualization.xml b/doc/book-enea-nfv-access-platform-guide/doc/hypervisor_virtualization.xml
new file mode 100644
index 0000000..092b52f
--- /dev/null
+++ b/doc/book-enea-nfv-access-platform-guide/doc/hypervisor_virtualization.xml
@@ -0,0 +1,328 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="hypervisor_virt">
+  <title>Hypervisor Virtualization</title>
+
+  <para>The KVM, Kernel-based Virtual Machine, is a virtualization
+  infrastructure for the Linux kernel which turns it into a hypervisor. KVM
+  requires a processor with a hardware virtualization extension.</para>
+
+  <para>KVM uses QEMU, an open source machine emulator and virtualizer, to
+  virtualize a complete system. With KVM it is possible to run multiple guests
+  of a variety of operating systems, each with a complete set of virtualized
+  hardware.</para>
+
+  <section id="launch_virt_machine">
+    <title>Launching a Virtual Machine</title>
+
+    <para>QEMU can make use of KVM when running a target architecture that is
+    the same as the host architecture. For instance, when running
+    qemu-system-x86_64 on an x86-64 compatible processor (containing
+    virtualization extensions Intel VT or AMD-V), you can take advantage of
+    the KVM acceleration, giving you benefit for your host and your guest
+    system.</para>
+
+    <para>Enea Linux includes an optimizied version of QEMU with KVM-only
+    support. To use KVM pass<command> --enable-kvm</command> to QEMU.</para>
+
+    <para>The following is an example of starting a guest:</para>
+
+    <programlisting>taskset -c 0,1 qemu-system-x86_64 \
+-cpu host -M q35 -smp cores=2,sockets=1 \
+-vcpu 0,affinity=0 -vcpu 1,affinity=1  \
+-enable-kvm -nographic \
+-kernel bzImage \
+-drive file=enea-image-virtualization-guest-qemux86-64.ext4,if=virtio,format=raw \
+-append 'root=/dev/vda console=ttyS0,115200' \
+-m 4096 \
+-object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on \
+-numa node,memdev=mem -mem-prealloc</programlisting>
+  </section>
+
+  <section id="qemu_boot">
+    <title>Main QEMU boot options</title>
+
+    <para>Below are detailed all the pertinent boot options for the QEMU
+    emulator:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>SMP - at least 2 cores should be enabled in order to isolate
+        application(s) running in virtual machine(s) on specific cores for
+        better performance.</para>
+
+        <programlisting>-smp cores=2,threads=1,sockets=1 \</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>CPU affinity - associate virtual CPUs with physical CPUs and
+        optionally assign a default real time priority to the virtual CPU
+        process in the host kernel. This option allows you to start qemu vCPUs
+        on isolated physical CPUs.</para>
+
+        <programlisting>-vcpu 0,affinity=0   \</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Hugepages - KVM guests can be deployed with huge page memory
+        support in order to reduce memory consumption and improve performance,
+        by reducing CPU cache usage. By using huge pages for a KVM guest, less
+        memory is used for page tables and TLB (Translation Lookaside Buffer)
+        misses are reduced, thereby significantly increasing performance,
+        especially for memory-intensive situations.</para>
+
+        <programlisting>-object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on \</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Memory preallocation - preallocate huge pages at startup time
+        can improve performance but it may affect the qemu boot time.</para>
+
+        <programlisting>-mem-prealloc \</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Enable realtime characteristics - run qemu with realtime
+        features. While that mildly implies that "-realtime" alone might do
+        something, it's just an identifier for options that are partially
+        realtime. If you're running in a realtime or low latency environment,
+        you don't want your pages to be swapped out and mlock does that, thus
+        mlock=on. If you want VM density, then you may want swappable VMs,
+        thus mlock=off.</para>
+
+        <programlisting>-realtime mlock=on \</programlisting>
+      </listitem>
+    </itemizedlist>
+
+    <para>If the hardware does not have an IOMMU (known as "Intel VT-d" on
+    Intel-based machines and "AMD I/O Virtualization Technology" on AMD-based
+    machines), it will not be possible to assign devices in KVM.
+    Virtualization Technology features (VT-d, VT-x, etc.) must be enabled from
+    BIOS on the host target before starting a virtual machine.</para>
+  </section>
+
+  <section id="net_in_guest">
+    <title>Networking in guest</title>
+
+    <section id="vhost-user-support">
+      <title>Using vhost-user support</title>
+
+      <para>The goal of vhost-user is to implement a Virtio transport, staying
+      as close as possible to the vhost paradigm of using shared memory,
+      ioeventfds and irqfds. A UNIX domain socket based mechanism allows the
+      set up of resources used by a number of Vrings shared between two
+      userspace processes, which will be placed in shared memory.</para>
+
+      <para>To run QEMU with the vhost-user backend, you have to provide the
+      named UNIX domain socket which needs to be already opened by the
+      backend:</para>
+
+      <programlisting>-object memory-backend-file,id=mem,size=4096M,mem-path=/dev/hugepages,share=on \
+-chardev socket,id=char0,path=/var/run/openvswitch/vhost-user1 \
+-netdev type=vhost-user,id=mynet1,chardev=char0,vhostforce \
+-device virtio-net-pci,netdev=mynet1,mac=52:54:00:00:00:01  \</programlisting>
+
+      <para>The vHost User standard uses a client-server model. The server
+      creates and manages the vHost User sockets and the client connects to
+      the sockets created by the server. It is recommended to use QEMU as
+      server so the vhost-user client can be restarted without affecting the
+      server, otherwise if the server side dies all clients need to be
+      restarted.</para>
+
+      <para>Using vhost-user in QEMU as server will offer the flexibility to
+      stop and start the virtual machine with no impact on virtual switch from
+      the host (vhost-user-client).</para>
+
+      <programlisting>-chardev socket,id=char0,path=/var/run/openvswitch/vhost-user1,server \</programlisting>
+    </section>
+
+    <section id="tap-interface">
+      <title>Using TAP Interfaces</title>
+
+      <para>QEMU can use TAP interfaces to provide full networking capability
+      for the guest OS:</para>
+
+      <programlisting>-netdev tap,id=net0,ifname=tap0,script=no,downscript=no \
+-device virtio-net-pci,netdev=net0,mac=22:EA:FB:A8:25:AE \</programlisting>
+    </section>
+
+    <section id="vfio-passthrough">
+      <title>VFIO passthrough VF (SR-IOV) to guest</title>
+
+      <para>KVM hypervisor support for attaching PCI devices on the host
+      system to guests. PCI passthrough allows guests to have exclusive access
+      to PCI devices for a range of tasks. PCI passthrough allows PCI devices
+      to appear and behave as if they were physically attached to the guest
+      operating system.</para>
+
+      <para>Preparing an Intel system for PCI passthrough:</para>
+
+      <itemizedlist>
+        <listitem>
+          <para>Enable the Intel VT-d extensions in BIOS</para>
+        </listitem>
+
+        <listitem>
+          <para>Activate Intel VT-d in the kernel by using
+          <literal>intel_iommu=on</literal> as a kernel boot parameter</para>
+        </listitem>
+
+        <listitem>
+          <para>Allow unsafe interrupts in case the system doesn't support
+          interrupt remapping. This can be done using
+          <literal>vfio_iommu_type1.allow_unsafe_interrupts=1</literal> as a
+          boot kernel parameter.</para>
+        </listitem>
+      </itemizedlist>
+
+      <para>Create guest with direct passthrough via VFIO framework like
+      so:</para>
+
+      <programlisting>-device vfio-pci,host=0000:03:10.2 \</programlisting>
+
+      <para>On the host, one or more VirtualFunctions (VFs) must be created in
+      order to be allocated for a guest network to access, before starting
+      QEMU:</para>
+
+      <programlisting>$ echo 2 &gt; /sys/class/net/eno3/device/sriov_numvfs
+$ modprobe vfio_pci
+$ dpdk-devbind.py --bind=vfio-pci 0000:03:10.2</programlisting>
+    </section>
+
+    <section id="multiqueue">
+      <title>Multi-queue</title>
+
+      <section id="qemu-multiqueue-support">
+        <title>QEMU multi queue support configuration</title>
+
+        <programlisting>-chardev socket,id=char0,path=/var/run/openvswitch/vhost-user1 \
+-netdev type=vhost-user,id=net0,chardev=char0,queues=2 \
+-device virtio-net-pci,netdev=net0,mac=22:EA:FB:A8:25:AE,mq=on,vectors=6
+where vectors is calculated as: 2 + 2 * queues number.</programlisting>
+      </section>
+
+      <section id="inside-guest">
+        <title>Inside guest</title>
+
+        <para>Linux kernel virtio-net driver (one queue is enabled by
+        default):</para>
+
+        <programlisting>$ ethtool -L combined 2 eth0
+DPDK Virtio PMD
+$ testpmd -c 0x7 -- -i --rxq=2 --txq=2 --nb-cores=2 ...</programlisting>
+
+        <para>For QEMU documentation please see: <ulink
+        url="https://qemu.weilnetz.de/doc/qemu-doc.html">https://qemu.weilnetz.de/doc/qemu-doc.html</ulink>.</para>
+      </section>
+    </section>
+  </section>
+
+  <section id="libvirt">
+    <title>Libvirt</title>
+
+    <para>One way to manage guests in Enea NFV Access is by using
+    <literal>libvirt</literal>. Libvirt is used in conjunction with a daemon
+    (<literal>libvirtd</literal>) and a command line utility (virsh) to manage
+    virtualized environments.</para>
+
+    <para>The libvirt library is a hypervisor-independent virtualization API
+    and toolkit that is able to interact with the virtualization capabilities
+    of a range of operating systems. Libvirt provides a common, generic and
+    stable layer to securely manage domains on a node. As nodes may be
+    remotely located, libvirt provides all methods required to provision,
+    create, modify, monitor, control, migrate and stop the domains, within the
+    limits of hypervisor support for these operations.</para>
+
+    <para>The libvirt daemon runs on the Enea NFV Access host. All tools built
+    on libvirt API connect to the daemon to request the desired operation, and
+    to collect information about the configuration and resources of the host
+    system and guests. <literal>virsh</literal> is a command line interface
+    tool for managing guests and the hypervisor. The virsh tool is built on
+    the libvirt management API.</para>
+
+    <para><emphasis role="bold">Major functionality provided by
+    libvirt</emphasis></para>
+
+    <para>The following is a summary from the libvirt <ulink
+    url="http://wiki.libvirt.org/page/FAQ#What_is_libvirt.3F">home
+    page</ulink> describing the major libvirt features:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para><emphasis role="bold">VM management:</emphasis> Various domain
+        lifecycle operations such as start, stop, pause, save, restore, and
+        migrate. Hotplug operations for many device types including disk and
+        network interfaces, memory, and cpus.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Remote machine support:</emphasis> All
+        libvirt functionality is accessible on any machine running the libvirt
+        daemon, including remote machines. A variety of network transports are
+        supported for connecting remotely, with the simplest being
+        <literal>SSH</literal>, which requires no extra explicit
+        configuration. For more information, see: <ulink
+        url="http://libvirt.org/remote.html">http://libvirt.org/remote.html</ulink>.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Network interface management:</emphasis>
+        Any host running the libvirt daemon can be used to manage physical and
+        logical network interfaces. Enumerate existing interfaces, as well as
+        configure (and create) interfaces, bridges, vlans, and bond devices.
+        For more details see: <ulink
+        url="https://fedorahosted.org/netcf/">https://fedorahosted.org/netcf/</ulink>.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Virtual NAT and Route based
+        networking:</emphasis> Any host running the libvirt daemon can manage
+        and create virtual networks. Libvirt virtual networks use firewall
+        rules to act as a router, providing VMs transparent access to the host
+        machines network. For more information, see: <ulink
+        url="http://libvirt.org/archnetwork.html">http://libvirt.org/archnetwork.html</ulink>.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Storage management:</emphasis> Any host
+        running the libvirt daemon can be used to manage various types of
+        storage: create file images of various formats (raw, qcow2, etc.),
+        mount NFS shares, enumerate existing LVM volume groups, create new LVM
+        volume groups and logical volumes, partition raw disk devices, mount
+        iSCSI shares, and much more. For more details, see: <ulink
+        url="http://libvirt.org/storage.html">http://libvirt.org/storage.html</ulink>.</para>
+      </listitem>
+
+      <listitem>
+        <para><emphasis role="bold">Libvirt Configuration:</emphasis> A
+        properly running libvirt requires that the following elements be in
+        place:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Configuration files, located in the directory
+            <literal>/etc/libvirt</literal>. They include the daemon's
+            configuration file <literal>libvirtd.conf</literal>, and
+            hypervisor-specific configuration files, like
+            <literal>qemu.conf</literal> for the QEMU.</para>
+          </listitem>
+
+          <listitem>
+            <para>A running libvirtd daemon. The daemon is started
+            automatically in Enea NFV Access host.</para>
+          </listitem>
+
+          <listitem>
+            <para>Configuration files for the libvirt domains, or guests, to
+            be managed by the KVM host. The specifics for guest domains shall
+            be defined in an XML file of a format specified at <ulink
+            url="http://libvirt.org/formatdomain.html">http://libvirt.org/formatdomain.html</ulink>.
+            XML formats for other structures are specified at <ulink type=""
+            url="http://libvirt.org/format.html">http://libvirt.org/format.html</ulink>.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+    </itemizedlist>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-platform-guide/doc/images/virtual_network_functions.png b/doc/book-enea-nfv-access-platform-guide/doc/images/virtual_network_functions.png
new file mode 100644
index 0000000..4011de8
--- /dev/null
+++ b/doc/book-enea-nfv-access-platform-guide/doc/images/virtual_network_functions.png
diff --git a/doc/book-enea-nfv-access-platform-guide/doc/ovs.xml b/doc/book-enea-nfv-access-platform-guide/doc/ovs.xml
new file mode 100644
index 0000000..3400975
--- /dev/null
+++ b/doc/book-enea-nfv-access-platform-guide/doc/ovs.xml
@@ -0,0 +1,161 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="ovs">
+  <title>Open Virtual Switch</title>
+
+  <para>Open vSwitch (OVS) is an open-source multilayer virtual switch
+  designed to be used in virtualized environments to forward traffic between
+  different VMs on the same host, and also between VMs and the physical
+  network.</para>
+
+  <para>Native OVS forwarding is handled by two major components: a user-space
+  daemon called <literal>ovs-vswitchd</literal> and a
+  <literal>fastpath</literal> kernel module used to accelerate the data path.
+  The fastpath kernel module will handle packets received on the NIC by simply
+  consulting a flow table with corresponding action rules (e.g to forward the
+  packet or modify its headers). If no matching entry is found in the flow
+  table, the packet is copied to the user-space and sent to the ovs-vswitchd
+  deamon which determines how it should be handled ("slowpath").</para>
+
+  <para>The packet is then passed back to the kernel module together with the
+  desired action and the flow table is updated, so that subsequent packets in
+  the same flow can be handled in fastpath without any user-space interaction.
+  In this way, OVS eliminates a lot of the context switching between
+  kernel-space and user-space, but the throughput is still limited by the
+  capacity of the Linux kernel stack.</para>
+
+  <section id="ovs-dpdk">
+    <title>OVS-DPDK</title>
+
+    <para>To improve performance, OVS supports integration with Intel DPDK
+    libraries to operate entirely in user-space (OVS-DPDK). DPDK Poll Mode
+    Drivers (PMDs) enable direct transfers of packets between the physical NIC
+    and user-space, thereby eliminating the overhead of interrupt handling and
+    Linux kernel network stack processing. OVS-DPDK provides DPDK-backed
+    vhost-user ports as the primary way to connect guests to this datapath.
+    The vhost-user interfaces are transparent to the guest.</para>
+  </section>
+
+  <section id="ovs-commands">
+    <title>OVS commands</title>
+
+    <para>OVS provides a rich set of command line management tools, most
+    importantly:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>ovs-vsctl: Used to manage and inspect switch configurations,
+        e.g. to create bridges and to add/remove ports.</para>
+      </listitem>
+
+      <listitem>
+        <para>ovs-ofctl: Used to configure and monitor flows.</para>
+      </listitem>
+    </itemizedlist>
+
+    <para>For more information about Open vSwitch, see <ulink
+    url="http://openvswitch.org">http://openvswitch.org</ulink>.</para>
+  </section>
+
+  <section id="config-ovs-dpdk">
+    <title>Configuring OVS-DPDK for improved performance</title>
+
+    <section id="dpdk-lcore-mask">
+      <title>dpdk-lcore-mask</title>
+
+      <para>Specifies the CPU core affinity for DPDK lcore threads. The lcore
+      threads are used for DPDK library tasks. For performance it is best to
+      set this to a single core on the system, and it should not overlap the
+      pmd-cpu-mask, as seen in the example below.</para>
+
+      <para>Example: To use core 1:</para>
+
+      <programlisting>ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x1</programlisting>
+    </section>
+
+    <section id="pmd-cpu-mask">
+      <title>pmd-cpu-mask</title>
+
+      <para>The DPDK PMD threads polling for incoming packets are CPU bound
+      and should be pinned to isolated cores for optimal performance.</para>
+
+      <para>If OVS-DPDK receives traffic on multiple ports, for example when
+      DPDK and vhost-user ports are used for bi-directional traffic, the
+      performance can be significantly improved by creating multiple PMD
+      threads and affinitizing them to separate cores in order to share the
+      workload, by each being responsible for an individual port. The cores
+      should not be hyperthreads on the same CPU.</para>
+
+      <para>The PMD core affinity is specified by setting an appropriate core
+      mask. Example: using cores 2 and 3:</para>
+
+      <programlisting>ovs-vsctl --no-wait set Open_vSwitch . other_config:pmd-cpu-mask=0xc</programlisting>
+    </section>
+  </section>
+
+  <section id="setup-ovs-dpdk">
+    <title>How to set up OVS-DPDK</title>
+
+    <para>The DPDK must be configured prior to setting up OVS-DPDK. See
+    [FIXME] for DPDK setup instructions, then follow these steps:</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Clean up the environment:</para>
+
+        <programlisting>killall ovsdb-server ovs-vswitchd
+rm -f /var/run/openvswitch/vhost-user*
+rm -f /etc/openvswitch/conf.db</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Start the ovsdb-server:</para>
+
+        <programlisting>export DB_SOCK=/var/run/openvswitch/db.sock
+ovsdb-tool create /etc/openvswitch/conf.db /usr/share/openvswitch/vswitch.ovsschema
+ovsdb-server --remote=punix:$DB_SOCK /
+--remote=db:Open_vSwitch,Open_vSwitch,manager_options --pidfile --detach</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Start ovs-vswitchd with DPDK support enabled:</para>
+
+        <programlisting>ovs-vsctl --no-wait init
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-lcore-mask=0x1
+ovs-vsctl --no-wait set Open_vSwitch . other_config:pmd-cpu-mask=0xc
+ovs-vsctl --no-wait set Open_vSwitch . other_config:dpdk-init=true
+ovs-vswitchd unix:$DB_SOCK --pidfile --detach /
+--log-file=/var/log/openvswitch/ovs-vswitchd.log</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Create the OVS bridge and attach ports:</para>
+
+        <programlisting>ovs-vsctl add-br ovsbr0 -- set bridge ovsbr0 datapath_type=netdev
+ovs-vsctl add-port ovsbr0 dpdk0 -- set Interface dpdk0 type=dpdk /
+:dpdk-devargs=&lt;PCI device&gt;</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Add DPDK vhost-user ports:</para>
+
+        <programlisting>ovs-vsctl add-port ovsbr0 vhost-user1 -- set Interface vhost-user1 type=dpdkvhostuser</programlisting>
+
+        <para>This command creates a socket at
+        <literal>/var/run/openvswitch/vhost-user1</literal>, which can be
+        provided to the VM on the QEMU command line. See [FIXME] for
+        details.</para>
+      </listitem>
+
+      <listitem>
+        <para>Define flows:</para>
+
+        <programlisting>ovs-ofctl del-flows ovsbr0
+ovs-ofctl show ovsbr0
+ovs-ofctl add-flow ovsbr0 in_port=1,action=output:2
+ovs-ofctl add-flow ovsbr0 in_port=2,action=output:1</programlisting>
+      </listitem>
+    </orderedlist>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-platform-guide/doc/platform_overview.xml b/doc/book-enea-nfv-access-platform-guide/doc/platform_overview.xml
new file mode 100644
index 0000000..945e25b
--- /dev/null
+++ b/doc/book-enea-nfv-access-platform-guide/doc/platform_overview.xml
@@ -0,0 +1,165 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="platform_overview">
+  <title>Platform Overview</title>
+
+  <para>The NFV Access Platform Guide available with this release of Enea
+  Linux, seeks to provide further information that will help all intended
+  users make the most out of the virtualization features.</para>
+
+  <section id="description">
+    <title>NFV Access Platform Description</title>
+
+    <para>Enea NFV Access is a lightweight virtualization software platform
+    designed for deployment on edge devices at customer premises. Streamlined
+    for high networking performance and minimal footprints for both platform
+    and VNFs, it enables very high compute density.</para>
+
+    <para>ENFV Access also provides a foundation for vCPE agility and
+    innovation, reducing cost and complexity for computing at the network
+    edge. It supports multiple architectures and scales from small white box
+    edge devices up to high-end network servers. Thanks to the streamlined
+    footprint, Enea NFV Access can be deployed on systems as small as single
+    2-core ARM devices. It scales up to clustered 24 core x86 Xeon servers and
+    beyond, allowing multiple VNFs on the same machine, and eliminating the
+    need to use different virtualization software for different hardware
+    platforms, saving costs through single source provisioning.</para>
+
+    <para>Optimized virtual networking performance provides low virtualized
+    networking latency, high virtualized networking throughput (10 Gb wire
+    speed), and low processing overhead. It allows high compute density on
+    white box hardware, maintaining performance when moving functionality from
+    application specific appliances to software on standard hardware. The
+    optimized boot speed minimizes the time from reboot to active services,
+    improving availability.</para>
+
+    <para>Enea NFV Access provides virtualization using both containers and
+    virtual machines. Containers provide lightweight virtualization for a
+    smaller VNF footprint and a very short time interval from start to enabled
+    network services. VMs provide virtualization with secure VNF sandboxing
+    and is the preferred virtualization method for OPNFV compliance. Enea NFV
+    Access allows combinations of containers and VMs for highest possible user
+    adaptability.</para>
+
+    <para>Flexible interfaces for VNF lifecycle management and service
+    function chaining, are important to allow a smooth transition from
+    traditional network appliances to virtualized network functions in
+    existing networks, as they plug into a variety of interfaces. Enea NFV
+    Access supports VNF lifecycle management and service function chaining
+    through OpenStack, NETCONF, REST, CLI and Docker. It integrates a powerful
+    device management framework that enables full FCAPS functionality for
+    powerful management of the platform.</para>
+
+    <para>Building on open source, Enea NFV Access prevents vendor lock-in
+    thanks to its completely open standards and interfaces. Unlike proprietary
+    platforms that either do not allow decoupling of software from hardware,
+    or prevent NVF portability, Enea NFV Access includes optimized components
+    with open interfaces to allow full portability and
+    interoperability.</para>
+  </section>
+
+  <section id="platform_components">
+    <title>NFV Access Platform Components</title>
+
+    <para>Enea NFV Access is built on highly optimized open source and
+    value-adding components that provide standard interfaces but with boosted
+    performance.</para>
+
+    <mediaobject>
+      <imageobject>
+        <imagedata align="center"
+                   fileref="images/virtual_network_functions.png" />
+      </imageobject>
+    </mediaobject>
+
+    <para>The Access Platform includes the following key components:</para>
+
+    <itemizedlist>
+      <listitem>
+        <para>Linux Kernel &ndash; Optimized Linux kernel with the focus on
+        vCPE systems characteristics.</para>
+      </listitem>
+
+      <listitem>
+        <para>KVM &ndash; Virtualization with virtual machines. KVM is the
+        standard virtualization engine for Linux based systems.</para>
+      </listitem>
+
+      <listitem>
+        <para>Docker &ndash; Docker provides a lightweight configuration using
+        containers. Docker is the standard platform for container
+        virtualization.</para>
+      </listitem>
+
+      <listitem>
+        <para>Virtual switching &ndash; Optimized OVS-DPDK provides high
+        throughput and low latency.</para>
+      </listitem>
+
+      <listitem>
+        <para>Edge Link &ndash; Edge Link provides interfaces to orchestration
+        for centralized VNF lifecycle management and service function
+        chaining:</para>
+
+        <orderedlist>
+          <listitem>
+            <para>NETCONF</para>
+          </listitem>
+
+          <listitem>
+            <para>OpenStack</para>
+          </listitem>
+
+          <listitem>
+            <para>Docker</para>
+          </listitem>
+
+          <listitem>
+            <para>REST</para>
+          </listitem>
+
+          <listitem>
+            <para>CLI</para>
+          </listitem>
+        </orderedlist>
+      </listitem>
+
+      <listitem>
+        <para>APT packet management &ndash; Feature rich repository of
+        prebuilt open source packages for extending and adapting the platform
+        using APT Package Management.</para>
+      </listitem>
+
+      <listitem>
+        <para>CLI based VNF management &ndash; CLI access over virsh and
+        libvirt.</para>
+      </listitem>
+
+      <listitem>
+        <para>FCAPS framework &ndash; The device management framework for
+        managing the platform is capable of providing full FCAPS functionality
+        to orchestration or network management systems.</para>
+      </listitem>
+
+      <listitem>
+        <para>Data plane &ndash; High performance data plane that includes the
+        following optimized data plane drivers:</para>
+
+        <orderedlist>
+          <listitem>
+            <para>DPDK</para>
+          </listitem>
+
+          <listitem>
+            <para>OpenFastPath (OFP)</para>
+          </listitem>
+
+          <listitem>
+            <para>ODP</para>
+          </listitem>
+        </orderedlist>
+      </listitem>
+    </itemizedlist>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-nfv-access-platform-guide/doc/using_nfv_access_platform_sdks.xml b/doc/book-enea-nfv-access-platform-guide/doc/using_nfv_access_platform_sdks.xml
new file mode 100644
index 0000000..9f0f3f5
--- /dev/null
+++ b/doc/book-enea-nfv-access-platform-guide/doc/using_nfv_access_platform_sdks.xml
@@ -0,0 +1,203 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE chapter PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
+"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
+<chapter id="workflow">
+  <title>Using NFV Access Platform SDKs</title>
+
+  <para>Enea NFV Access Platform comes with two different toolchains, one for
+  developing applications for the host and one for applications running in the
+  guest VM. Each is wrapped together with an environment-setup script into a
+  shell archive and is available under the Download section on
+  portal.enea.com. They have self explanatory names.</para>
+
+  <itemizedlist>
+    <listitem>
+      <para><literal>inteld1521/sdk/enea-glibc-x86_64-enea-image-virtualization-host-sdk-corei7-64-toolchain-7.0.sh</literal>
+      - for host applications.</para>
+    </listitem>
+
+    <listitem>
+      <para><literal>qemux86-64/sdk/enea-glibc-x86_64-enea-image-virtualization-guest-sdk-core2-64-toolchain-7.0.sh</literal>
+      - for guest applications.</para>
+    </listitem>
+  </itemizedlist>
+
+  <section id="install-crosscomp">
+    <title>Installing the Cross-Compilation Toolchain</title>
+
+    <para>Before cross-compiling applications for your target, you need to
+    install the corresponding toolchain on your workstation. To do that,
+    simply run the installer and follow the steps included with it:</para>
+
+    <orderedlist>
+      <listitem>
+        <para><programlisting>$ ./enea-glibc-x86_64-enea-image-virtualization-guest-sdk-core2-64-toolchain-7.0.sh</programlisting>When
+        prompted, select to install the toolchain in the desired directory,
+        referred to as <literal>&lt;sdkdir&gt;</literal>. </para>
+
+        <para>A default path where the toolchain will be installed will be
+        shown in the prompt. The installer unpacks the environment setup
+        script in <literal>&lt;sdkdir&gt;</literal> and the toolchain under
+        <literal>&lt;sdkdir&gt;/sysroots</literal>.</para>
+
+        <note>
+          <para>Choose a unique directory for each toolchain. Installing a
+          second toolchain of any type in the same directory as a previously
+          installed one will break the <literal>$PATH</literal> variable of
+          the first one.</para>
+        </note>
+      </listitem>
+
+      <listitem>
+        <para>Setup the toolchain environment for your target by sourcing the
+        environment-setup script. Example: <programlisting>$ source &lt;sdkdir&gt;/environment-setup-core2-64-enea-linux</programlisting></para>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section id="crosscomp-apps">
+    <title>Cross-Compiling Applications from Command Line</title>
+
+    <para>Once the environment-setup script is sourced, you can make your
+    applications as per usual and get them compiled for your target. Below you
+    see how to cross-compile from command line.</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Create a Makefile for your application. Example: a simple
+        Makefile and application:</para>
+
+        <programlisting>helloworld:helloworld.o
+        $(CC) -o helloworld helloworld.o
+clean:
+        rm -f *.o helloworld
+#include &lt;stdio.h&gt;
+int main(void) {
+        printf("Hello World\n");
+        return 0;
+}</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Run <command>make</command> to cross-compile your application
+        according to the environment set up:</para>
+
+        <programlisting>$ make</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Deploy the helloworld program to your target and run it:</para>
+
+        <programlisting># ./helloworld
+hello world</programlisting>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section id="crosscomp-kern-mod">
+    <title>Cross-Compiling Kernel Modules</title>
+
+    <para>Before cross-compiling kernle modules, you need to make sure the
+    installed toolchain includes the kernel source tree, which should be
+    available at:
+    <literal>&lt;sdkdir&gt;/sysroots/&lt;targetarch&gt;-enea-linux/usr/src/kernel</literal>.</para>
+
+    <para>Once the environment-setup script is sourced, you can make your
+    kernel modules as usual and get them compiled for your target. Below you
+    see how to cross-compile a kernel module.</para>
+
+    <orderedlist>
+      <listitem>
+        <para>Create a Makefile for the kernel module. Example: a simple
+        Makefile and kernel module:</para>
+
+        <programlisting>obj-m := hello.o
+PWD := $(shell pwd)
+
+KERNEL_SRC := &lt;full path to kernel source tree&gt;
+
+all: scripts
+    $(MAKE) -C $(KERNEL_SRC) M=$(PWD) LDFLAGS="" modules
+scripts:
+    $(MAKE) -C $(KERNEL_SRC) scripts
+clean:
+    $(MAKE) -C $(KERNEL_SRC) M=$(PWD) LDFLAGS="" clean
+#include &lt;linux/module.h&gt;      /* Needed by all modules */
+#include &lt;linux/kernel.h&gt;      /* Needed for KERN_INFO */
+#include &lt;linux/init.h&gt;        /* Needed for the macros */
+
+static int __init hello_start(void)
+{
+    printk(KERN_INFO "Loading hello module...\n");
+    printk(KERN_INFO "Hello, world\n");
+    return 0;
+}
+
+static void __exit hello_end(void)
+{
+    printk(KERN_INFO "Goodbye, world\n");
+}
+
+module_init(hello_start);
+module_exit(hello_end);
+
+MODULE_LICENSE("GPL");</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Run <command>make</command> to cross-compile your kernel module
+        according to the environment set up:</para>
+
+        <programlisting>$ make</programlisting>
+      </listitem>
+
+      <listitem>
+        <para>Deploy the kernel module <literal>hello.ko</literal> to your
+        target and install/remove it:</para>
+
+        <programlisting># insmod hello.ko
+# rmmod hello.ko
+# dmesg
+[...] Loading hello module...
+[...] Hello, world
+[...] Goodbye, world</programlisting>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section id="deploy-artifacts">
+    <title>Deploying your artifacts</title>
+
+    <orderedlist>
+      <listitem>
+        <para>Deploying on host</para>
+
+        <para>You can use <literal>ssh</literal> to deploy your artifacts on
+        the host target. For this you will need a network connection to the
+        target and to use <literal>scp</literal> to copy to the desired
+        location.</para>
+      </listitem>
+
+      <listitem>
+        <para>Deploying on guest</para>
+
+        <para>You can deploy your artifacts onto the guest VM running on the
+        target in two steps:</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Deploy the artifacts onto the target by using the method
+            described above or any other method.</para>
+          </listitem>
+
+          <listitem>
+            <para>On the target, copy the artifacts to the guest rootfs. For
+            this, you will need to shut down the guest VM, mount the file
+            system on the target, copy your files onto it, unmount it and then
+            restart the guest VM as usual.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+    </orderedlist>
+  </section>
+</chapter>
\ No newline at end of file
diff --git a/doc/book-enea-linux-release-info/swcomp.mk b/doc/book-enea-nfv-access-platform-guide/swcomp.mk
index 6e86ff1..4572144 100644
--- a/doc/book-enea-linux-release-info/swcomp.mk
+++ b/doc/book-enea-nfv-access-platform-guide/swcomp.mk
@@ -5,6 +5,6 @@ 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-linux-release-info
-BOOKDESC_$(BOOKPACKAGES) := "Enea Linux $(PROD_VER) Release Information"
+BOOKPACKAGES := book-enea-nfv-access-platform-guide
+BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access Platform $(PROD_VER) Guide"
 BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-linux-open-source/doc/README b/doc/book-enea-nfv-access-platform-open-source/doc/README
index c40a2d9..c40a2d9 100644
--- a/doc/book-enea-linux-open-source/doc/README
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/README
diff --git a/doc/book-enea-linux-open-source/doc/about.xml b/doc/book-enea-nfv-access-platform-open-source/doc/about.xml
index d4b6437..79c8375 100644
--- a/doc/book-enea-linux-open-source/doc/about.xml
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/about.xml
@@ -5,8 +5,8 @@
   <title>About this Report</title>
 
   <para>This document contains the open source and license information
-  pertaining to packages provided with Enea Linux <xi:include
-  href="../../book-enea-linux-release-info/doc/eltf_params_updated.xml"
+  pertaining to packages provided with Enea NFV Access Platform <xi:include
+  href="../../book-enea-nfv-access-platform-release-info/doc/eltf_params_updated.xml"
   xmlns:xi="http://www.w3.org/2001/XInclude"
   xpointer="element(EneaLinux_REL_VER/1)" />.</para>
 </chapter>
\ No newline at end of file
diff --git a/doc/book-enea-linux-open-source/doc/book.xml b/doc/book-enea-nfv-access-platform-open-source/doc/book.xml
index 1fd8217..460e242 100644
--- a/doc/book-enea-linux-open-source/doc/book.xml
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/book.xml
@@ -3,10 +3,10 @@
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
 <!ENTITY % local.common.attrib "xml:base CDATA #IMPLIED">
 ]>
-<book id="book_enea_linux_open_source">
-  <title><trademark class="registered">Enea</trademark> Linux Open Source Report</title>
+<book id="book-enea-nfv-access-platform-open-source">
+  <title><trademark class="registered">Enea</trademark> NFV Access Platform Open Source Report</title>
   <subtitle>Release Version
-         <xi:include href="../../book-enea-linux-release-info/doc/eltf_params_updated.xml" xpointer="element(EneaLinux_REL_VER/1)"
+         <xi:include href="../../book-enea-nfv-access-platform-release-info/doc/eltf_params_updated.xml" xpointer="element(EneaLinux_REL_VER/1)"
          xmlns:xi="http://www.w3.org/2001/XInclude" /></subtitle>
   <xi:include href="../../s_docbuild/template/docsrc_common/bookinfo_userdoc.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
   <xi:include href="about.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
diff --git a/doc/book-enea-linux-open-source/doc/licenses.xml b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
index 07d0809..07d0809 100644
--- a/doc/book-enea-linux-open-source/doc/licenses.xml
+++ b/doc/book-enea-nfv-access-platform-open-source/doc/licenses.xml
diff --git a/doc/book-enea-linux-virtualization-guide/swcomp.mk b/doc/book-enea-nfv-access-platform-open-source/swcomp.mk
index 8206490..6324da1 100644
--- a/doc/book-enea-linux-virtualization-guide/swcomp.mk
+++ b/doc/book-enea-nfv-access-platform-open-source/swcomp.mk
@@ -5,6 +5,6 @@ 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-linux-virtualization-guide
-BOOKDESC_$(BOOKPACKAGES) := "Enea Linux $(PROD_VER) Virtualization Guide"
+BOOKPACKAGES := book-enea-nfv-access-platform-open-source
+BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access Platform Open Source Report"
 BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/book-enea-linux-release-info/doc/about_release.xml b/doc/book-enea-nfv-access-platform-release-info/doc/about_release.xml
index 01679f8..01679f8 100644
--- a/doc/book-enea-linux-release-info/doc/about_release.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/about_release.xml
diff --git a/doc/book-enea-linux-release-info/doc/book.xml b/doc/book-enea-nfv-access-platform-release-info/doc/book.xml
index 91af443..a0adf73 100644
--- a/doc/book-enea-linux-release-info/doc/book.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/book.xml
@@ -2,8 +2,8 @@
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
 "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [
 ]>
-<book id="book_enea_linux_release_info">
-  <title><trademark class="registered">Enea</trademark> Linux Release Information</title>
+<book id="book_enea_nfv_access_platform_release_info">
+  <title><trademark class="registered">Enea</trademark> NFV Access Platform Release Information</title>
   <subtitle>Release Version
          <xi:include href="eltf_params_updated.xml" xpointer="element(EneaLinux_REL_VER/1)"
          xmlns:xi="http://www.w3.org/2001/XInclude" /></subtitle>
diff --git a/doc/book-enea-linux-release-info/doc/build_boot_template.xml b/doc/book-enea-nfv-access-platform-release-info/doc/build_boot_template.xml
index e39dd81..e39dd81 100644
--- a/doc/book-enea-linux-release-info/doc/build_boot_template.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/build_boot_template.xml
diff --git a/doc/book-enea-linux-virtualization-guide/doc/eltf_params_template.xml b/doc/book-enea-nfv-access-platform-release-info/doc/eltf_params_template.xml
index 278ad71..278ad71 100644
--- a/doc/book-enea-linux-virtualization-guide/doc/eltf_params_template.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/eltf_params_template.xml
diff --git a/doc/book-enea-linux-release-info/doc/eltf_params_updated.xml b/doc/book-enea-nfv-access-platform-release-info/doc/eltf_params_updated.xml
index 294e6c4..40507bb 100644
--- a/doc/book-enea-linux-release-info/doc/eltf_params_updated.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/eltf_params_updated.xml
@@ -42,7 +42,7 @@ export PATH=~/bin:$PATH</programlisting></para>
     correct also compared to the "previous" REL VER in pardoc-distro.xml
     "prev_baseline".</bridgehead>
 
-    <para id="EneaLinux_REL_VER"><phrase>6</phrase></para>
+    <para id="EneaLinux_REL_VER"><phrase>1.0</phrase></para>
 
     <para id="Yocto_VER"><phrase>2.1</phrase></para>
 
diff --git a/doc/book-enea-linux-release-info/doc/eltf_params_updated_template_how_to_use.txt b/doc/book-enea-nfv-access-platform-release-info/doc/eltf_params_updated_template_how_to_use.txt
index a75acfc..a75acfc 100644
--- a/doc/book-enea-linux-release-info/doc/eltf_params_updated_template_how_to_use.txt
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/eltf_params_updated_template_how_to_use.txt
diff --git a/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml b/doc/book-enea-nfv-access-platform-release-info/doc/getting_enea_linux.xml
index 075ade5..075ade5 100644
--- a/doc/book-enea-linux-release-info/doc/getting_enea_linux.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/getting_enea_linux.xml
diff --git a/doc/book-enea-linux-release-info/doc/jiraissues_override.xml b/doc/book-enea-nfv-access-platform-release-info/doc/jiraissues_override.xml
index 7282d0f..7282d0f 100644
--- a/doc/book-enea-linux-release-info/doc/jiraissues_override.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/jiraissues_override.xml
diff --git a/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml b/doc/book-enea-nfv-access-platform-release-info/doc/known_bugs_and_limitations.xml
index 173046b..173046b 100644
--- a/doc/book-enea-linux-release-info/doc/known_bugs_and_limitations.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/known_bugs_and_limitations.xml
diff --git a/doc/book-enea-linux-release-info/doc/main_changes.xml b/doc/book-enea-nfv-access-platform-release-info/doc/main_changes.xml
index 115acb5..115acb5 100644
--- a/doc/book-enea-linux-release-info/doc/main_changes.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/main_changes.xml
diff --git a/doc/book-enea-linux-release-info/doc/prerequisites.xml b/doc/book-enea-nfv-access-platform-release-info/doc/prerequisites.xml
index 9c5aa95..9c5aa95 100644
--- a/doc/book-enea-linux-release-info/doc/prerequisites.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/prerequisites.xml
diff --git a/doc/book-enea-linux-release-info/doc/system_requirements.xml b/doc/book-enea-nfv-access-platform-release-info/doc/system_requirements.xml
index e94d012..e94d012 100644
--- a/doc/book-enea-linux-release-info/doc/system_requirements.xml
+++ b/doc/book-enea-nfv-access-platform-release-info/doc/system_requirements.xml
diff --git a/doc/book-enea-linux-open-source/swcomp.mk b/doc/book-enea-nfv-access-platform-release-info/swcomp.mk
index d978b48..c246cb2 100644
--- a/doc/book-enea-linux-open-source/swcomp.mk
+++ b/doc/book-enea-nfv-access-platform-release-info/swcomp.mk
@@ -5,6 +5,6 @@ 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-linux-open-source
-BOOKDESC_$(BOOKPACKAGES) := "Enea Linux Open Source Report"
+BOOKPACKAGES := book-enea-nfv-access-platform-release-info
+BOOKDESC_$(BOOKPACKAGES) := "Enea NFV Access Platform $(PROD_VER) Release Information"
 BOOKDEFAULTCONDITION := $(DEFAULTCONDITIONS)
diff --git a/doc/manifest_conf.mk b/doc/manifest_conf.mk
index 2da4a7a..92e395c 100644
--- a/doc/manifest_conf.mk
+++ b/doc/manifest_conf.mk
@@ -3,6 +3,6 @@
 #       The values are shown in the release info
 #       The manifest is used to fetch information into the release info from the distro files
 #MANIFESTHASH      ?= 0d0f06384afa65eaae4b170e234ee5a813edf44d
-#change the above value later to refs/tags/ELnnn (?)
+        #change the above value later to refs/tags/ELnnn (?)
 MANIFESTURL       := git@git.enea.com:linux/manifests/el_manifests-virtualization.git
-PROFILE_NAME      := Virtualization
+PROFILE_NAME      := Enea NFV Access Platform