USERDOCAP-240 updating the release info and other minor edits to the IG

8 files changed, 593 insertions, 285 deletions

diff --git a/book-enea-nfv-core-release-info/doc/about_release.xml b/book-enea-nfv-core-release-info/doc/about_release.xml
index 0acde2e..e0c6e2f 100644
--- a/book-enea-nfv-core-release-info/doc/about_release.xml
+++ b/book-enea-nfv-core-release-info/doc/about_release.xml
@@ -4,21 +4,244 @@
 <chapter id="relinfo-about-release">
   <title>About This Release</title>
 
-  <section id="relinfo-abstract">
-    <title>Abstract</title>
+  <section id="intro">
+    <title>Introduction</title>
 
-    <para>This document compiles the release notes for the 1.0 release of Enea
-    NFV Core when using Fuel as a deployment tool.</para>
-  </section>
+    <para>Enea NFV Core is based on the OPNFV <emphasis
+    role="bold">Danube</emphasis> release, and is compatible with the <ulink
+    url="http://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.02.01_60/gs_NFV002v010201p.pdf">ETSI
+    NFV reference architecture</ulink>. It leverages several OPNFV community
+    projects, including Functest, Yardstick, Doctor, Fuel, and Armband.</para>
+
+    <para>This release consists of the following components:</para>
+
+    <informaltable>
+      <tgroup cols="2">
+        <tbody>
+          <row>
+            <entry align="center"><emphasis
+            role="bold">Component</emphasis></entry>
+
+            <entry align="center"><emphasis role="bold">Version /
+            Details</emphasis></entry>
+          </row>
+
+          <row>
+            <entry>Installer</entry>
+
+            <entry>Fuel v.10</entry>
+          </row>
+
+          <row>
+            <entry>OPNFV version</entry>
+
+            <entry>Danube</entry>
+          </row>
+
+          <row>
+            <entry>OpenStack Version</entry>
+
+            <entry>OpenStack Newton</entry>
+          </row>
+
+          <row>
+            <entry>OS for Controller / Compute Nodes</entry>
+
+            <entry>Debian 9</entry>
+          </row>
+
+          <row>
+            <entry>Pacemaker</entry>
+
+            <entry>2:9.1.3-1~u16.04+mos4</entry>
+          </row>
+
+          <row>
+            <entry>HA Proxy</entry>
+
+            <entry>1.6.3-1~u16.04+mos3</entry>
+          </row>
+
+          <row>
+            <entry>Open vSwitch</entry>
+
+            <entry>2.7.0-0ubuntu3 plus other patches</entry>
+          </row>
+
+          <row>
+            <entry>DPDK</entry>
+
+            <entry>16.11.2-3 upgraded to 17.02.1 plus other patches</entry>
+          </row>
+
+          <row>
+            <entry>Qemu-KVM</entry>
+
+            <entry align="left">1:2.8+dfsg-3ubuntu1 upgraded to
+            1:2.9~rc1+dfsg-0+amos1~u16.04 plus other patches</entry>
+          </row>
+
+          <row>
+            <entry>EDK2</entry>
+
+            <entry align="left">0~20160813.de74668f-1ubuntu0.1 plus other
+            patches</entry>
+          </row>
+
+          <row>
+            <entry>Libvirt</entry>
+
+            <entry>3.5.0-1ubuntu3 plus other patches</entry>
+          </row>
+
+          <row>
+            <entry>Linux Kernel</entry>
+
+            <entry>4.10 plus other patches</entry>
+          </row>
+
+          <row>
+            <entry>Aodh</entry>
+
+            <entry>3.0.2-1~u16.04+mos0</entry>
+          </row>
+
+          <row>
+            <entry>Ceilometer</entry>
+
+            <entry>1:7.0.3-1~u16.04+mos2</entry>
+          </row>
+
+          <row>
+            <entry>Tacker</entry>
+
+            <entry>0.7.0 plus other patches</entry>
+          </row>
+
+          <row>
+            <entry>Heat</entry>
+
+            <entry>1:7.0.2-1~u16.04+mos4</entry>
+          </row>
+
+          <row>
+            <entry>TOSCA-Parser</entry>
+
+            <entry>0.8.1 plus other patches</entry>
+          </row>
+
+          <row>
+            <entry>cloud-init</entry>
+
+            <entry>0.7.9-90-g61eb03fe-0+amos1~u16.04</entry>
+          </row>
+
+          <row>
+            <entry>Ceph Object Storage</entry>
+
+            <entry>10.2.6-0ubuntu0.16.04.1</entry>
+          </row>
+
+          <row>
+            <entry>RabbitMQ Messaging</entry>
+
+            <entry>3.6.6-1+amos1~u16.04+mos1</entry>
+          </row>
+
+          <row>
+            <entry>Zabbix</entry>
+
+            <entry>1:2.4.8-1+trusty plus other patches</entry>
+          </row>
+
+          <row>
+            <entry>Vitrage</entry>
+
+            <entry>1.0.2.dev5</entry>
+          </row>
+
+          <row>
+            <entry>Erlang</entry>
+
+            <entry>1:18.3.4+dfsg-1~u16.04+mos1</entry>
+          </row>
+
+          <row>
+            <entry>Percona XtraBackup</entry>
+
+            <entry>2.4.5-1+amos1~u16.04 plus other patches</entry>
+          </row>
+
+          <row>
+            <entry>MongoDB</entry>
+
+            <entry>1:2.6.10-0+amos1~u16.04</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+
+    <para>Galera cluster for MySQL consists of:</para>
+
+    <informaltable>
+      <tgroup cols="2">
+        <tbody>
+          <row>
+            <entry align="center"><emphasis
+            role="bold">Component</emphasis></entry>
+
+            <entry align="center"><emphasis role="bold">Version /
+            Details</emphasis></entry>
+          </row>
+
+          <row>
+            <entry>MySQL-wsrep</entry>
+
+            <entry>5.6.36</entry>
+          </row>
+
+          <row>
+            <entry>Galera</entry>
+
+            <entry>3.21</entry>
+          </row>
+
+          <row>
+            <entry>wsrep API</entry>
+
+            <entry>25</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
+
+    <para>Components that are included but not pre-integrated or verified in
+    the release testing scenarios, (not formally supported):</para>
+
+    <informaltable>
+      <tgroup cols="2">
+        <tbody>
+          <row>
+            <entry align="center"><emphasis
+            role="bold">Component</emphasis></entry>
+
+            <entry align="center"><emphasis role="bold">Version /
+            Details</emphasis></entry>
+          </row>
+
+          <row>
+            <entry>OpenDaylight</entry>
+
+            <entry>Boron</entry>
+          </row>
 
-  <section id="relinfo-importantnotes">
-    <title>Important Notes</title>
+          <row>
+            <entry>Congress</entry>
 
-    <para>These notes provides release information for the use of Fuel as
-    deployment tool for the 1.0 release of ENFV Core. This Fuel-based
-    deployment process is to establish a lab ready platform accelerating
-    further development of the ENFV infrastructure. Carefully follow the
-    installation instructions detailed in Installation Guide provided with
-    this release.</para>
+            <entry>4.0.0 with Doctor datasource</entry>
+          </row>
+        </tbody>
+      </tgroup>
+    </informaltable>
   </section>
 </chapter>
\ No newline at end of file
diff --git a/book-enea-nfv-core-release-info/doc/book.xml b/book-enea-nfv-core-release-info/doc/book.xml
index 1f865b8..3a6b27d 100644
--- a/book-enea-nfv-core-release-info/doc/book.xml
+++ b/book-enea-nfv-core-release-info/doc/book.xml
@@ -8,9 +8,6 @@
 
   <xi:include href="../../s_docbuild/template/docsrc_common/bookinfo_userdoc.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
   <xi:include href="about_release.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  <xi:include href="summary.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  <xi:include href="build_boot_generated.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-<!--  <xi:include href="main_changes.xml" xmlns:xi="http://www.w3.org/2001/XInclude" />
-  <xi:include href="known_bugs_and_limitations.xml" xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+  <xi:include href="known_bugs_and_limitations.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>
\ No newline at end of file
diff --git a/book-enea-nfv-core-release-info/doc/build_boot_generated.xml b/book-enea-nfv-core-release-info/doc/build_boot_generated.xml
deleted file mode 100644
index 7affc4e..0000000
--- a/book-enea-nfv-core-release-info/doc/build_boot_generated.xml
+++ /dev/null
@@ -1,55 +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="relinfo-build-boot">
-  <title>Target Specific Instructions</title>
-
-  <para>If the source has been fetched there will be a target specific README
-  file containing the build and boot instructions. To make it easier for the
-  reader, the contents of this file(s) have been extracted into the following
-  sections.</para>
-
-  <note>
-    <para>The build process duration may vary and be longer than expected in
-    some cases, depending on the individual build resources and parameters of
-    each target/machine supported in this release.</para>
-  </note>
-
-  <para><remark>NOTE: Only EDIT THE TEMPLATE build_boot_template.xml file here
-  and also only edit the manifest template ".README" (name starting by a dot)!
-  A new build_boot_generated.xml file is created from the template and
-  sections are added below automatically from the README files for each target
-  when building the book! Only in the template file you see a line below with
-  SCRIPT_...._HERE and the text telling that this is a template
-  file.</remark></para>
-
-  <section id="target_inteld1521">
-    <title>Target inteld1521</title>
-
-    <remark>NOTE: DO NOT EDIT THIS GENERATED FILE! Only edit the template
-    file.</remark>
-
-    <section>
-      <title>Build Instructions for inteld1521</title>
-    </section>
-
-    <section>
-      <title>Boot Instructions for inteld1521</title>
-    </section>
-  </section>
-
-  <section id="target_qemux86-64">
-    <title>Target qemux86-64</title>
-
-    <remark>NOTE: DO NOT EDIT THIS GENERATED FILE! Only edit the template
-    file.</remark>
-
-    <section>
-      <title>Build Instructions for qemux86-64</title>
-    </section>
-
-    <section>
-      <title>Boot Instructions for qemux86-64</title>
-    </section>
-  </section>
-</chapter>
\ No newline at end of file
diff --git a/book-enea-nfv-core-release-info/doc/build_boot_template.xml b/book-enea-nfv-core-release-info/doc/build_boot_template.xml
deleted file mode 100644
index e39dd81..0000000
--- a/book-enea-nfv-core-release-info/doc/build_boot_template.xml
+++ /dev/null
@@ -1,34 +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="relinfo-build-boot">
-  <title>Target Specific Instructions</title>
-
-  <para>If the source has been fetched (<xref
-  linkend="relinfo-getting-source" />), there will be a target specific README
-  file containing the build and boot instructions. To make it easier for the
-  reader, the contents of this file(s) have been extracted into the following
-  sections.</para>
-
-  <note>
-    <para>The build process duration may vary and be longer than expected in
-    some cases, depending on the individual build resources and parameters of
-    each target/machine supported in this release.</para>
-  </note>
-
-  <para><remark>NOTE: Only EDIT THE TEMPLATE build_boot_template.xml file here
-  and also only edit the manifest template ".README" (name starting by a dot)!
-  A new build_boot_generated.xml file is created from the template and
-  sections are added below automatically from the README files for each target
-  when building the book! Only in the template file you see a line below with
-  SCRIPT_...._HERE and the text telling that this is a template
-  file.</remark></para>
-
-  <para>SCRIPT_INCLUDES_BUILD_BOOT_SECTIONS_HERE</para>
-
-  <para><emphasis role="bold">This is a template file which you can edit. When
-  the book is built, a new XML chapter file is created where the above part of
-  this file is copied to the new XML file and all from the line above is
-  replaced automatically by build and boot sections from the README
-  files!</emphasis></para>
-</chapter>
\ No newline at end of file
diff --git a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
new file mode 100644
index 0000000..039fae9
--- /dev/null
+++ b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml
@@ -0,0 +1,356 @@
+<?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="bugs-limitations">
+  <title>Known Issues and Limitations</title>
+
+  <para>Problems and limitations relevant to the current release are detailed
+  in this chapter. Corrections to bugs detected by Enea are submitted
+  upstream, and remaining issues are listed below.<remark>INFO: The <emphasis
+  role="bold">Release-Specific Problems</emphasis> section further down is
+  generated from JIRA with gen_known_issues.py, but that script is HARDCODED
+  with affectedversion "Enea NFV 1.0" and needs to be adapted when a release
+  info for another ENFV version changes.</remark></para>
+
+  <section id="bugs-limitations-gen">
+    <title>Release Specific Issues</title>
+
+    <orderedlist>
+      <listitem>
+        <para>Security groups are not working correctly for ICMP traffic in
+        deployments with OpenDaylight.</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <orderedlist>
+              <listitem>
+                <para>When OPNFV is deployed with OpenDaylight as an SDN
+                controller, the Security Groups rules pertaining to ICMP do
+                not work as expected. The OpenFlow rules describing the ICMP
+                rules are inconsistent, so VMs can be pinged even when this is
+                not desired.</para>
+              </listitem>
+
+              <listitem>
+                <para>This reproduces on aarch64. On x86 the security groups
+                work correctly.</para>
+              </listitem>
+            </orderedlist>
+          </listitem>
+
+          <listitem>
+            <para>Workaround: N/A.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Virtual instances do not get IP from DHCP in SFC scenarios with
+        ODL</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <orderedlist>
+              <listitem>
+                <para>After a fresh deploy of OPNFV with OpenDaylight and the
+                Service Function Chaining scenario configurations, instances
+                fail to get IP from DHCP, due to OpenDaylight
+                malfunctioning.</para>
+              </listitem>
+
+              <listitem>
+                <para>The SFC VNFs are not reachable via SSH for management
+                and configuration.</para>
+              </listitem>
+            </orderedlist>
+          </listitem>
+
+          <listitem>
+            <para>Workaround: Restarting OpenDaylight via
+            <literal>systemctl</literal> fixes the problem.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Scale-in and Scale-out operations are not supported</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <orderedlist>
+              <listitem>
+                <para>When adding or removing nodes via Fuel installer on an
+                OPNFV deployment that uses OpenDaylight, flows in
+                <filename>ovs</filename> tables on the existing and new nodes
+                are not updated properly. Similarly, OpenvSwitch ports
+                interfaces are not removed when deleting nodes.</para>
+              </listitem>
+
+              <listitem>
+                <para>As a consequence, when adding a compute node to an
+                existing OPNFV deployment, the instances running on the new
+                compute node cannot be reached by floating IP. Scale-out and
+                scale-in operations are flawed.</para>
+              </listitem>
+            </orderedlist>
+          </listitem>
+
+          <listitem>
+            <para>Workaround: The rules can be manually configured, but this
+            is not scalable.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Hot-plugging network interfaces does not work in aarch64
+        guests</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <orderedlist>
+              <listitem>
+                <para>When the user tries to hot-plug a network port to a
+                running instance, this fails due to virtio negotiation failure
+                between the host and guest. This happens when the VM is using
+                a Linux Kernel version prior to 4.10. Port addition or
+                deletion is not possible.</para>
+              </listitem>
+
+              <listitem>
+                <para>This reproduces on aarch64.</para>
+              </listitem>
+            </orderedlist>
+          </listitem>
+
+          <listitem>
+            <para>Workaround: The user needs to upgrade the guest Linux Kernel
+            to 4.10 or later. In case of port addition, the user also needs to
+            manually set the link up and trigger the
+            <literal>dhclient</literal> request.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Fuel Healthcheck Configuration tests fail when default
+        credentials are used</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <orderedlist>
+              <listitem>
+                <para>The Configuration tests from the Fuel Healthcheck fail
+                when the OPNFV cluster operates with the default credentials.
+                This has no impact on the overall cluster
+                functionality.</para>
+              </listitem>
+
+              <listitem>
+                <para>This is architecture independent.</para>
+              </listitem>
+            </orderedlist>
+          </listitem>
+
+          <listitem>
+            <para>Workaround: In order to make these 3 test cases pass, the
+            user needs to:</para>
+
+            <orderedlist>
+              <listitem>
+                <para>Change the credentials for the root user on the Fuel
+                Master node: after logging on as root on the master node,
+                issue command <command>passwd</command> and provide the new
+                password.</para>
+              </listitem>
+
+              <listitem>
+                <para>Change the default credentials for the OpenStack
+                cluster: in Fuel Dashboard, for an Environment, change
+                Settings|General|OpenStack Access &gt; Password to something
+                other than the default.</para>
+              </listitem>
+
+              <listitem>
+                <para>Change the default credentials for Keystone on the
+                master node: in Fuel Dashboard, click on the user avatar and
+                select <literal>Change Password</literal>. This should be done
+                before deploy or you will need to redeploy to have the changes
+                applied.</para>
+              </listitem>
+            </orderedlist>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Fuel Healthcheck Stack update test fails</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <para>The Platform test case number 5 (Update stack) from the Fuel
+            Healthcheck fails. This has no impact on the overal cluster
+            functionality.</para>
+          </listitem>
+
+          <listitem>
+            <para>Workaround: N/A.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Issue #1 with Openstack Resource Agents and Compute Fencing
+        functionality</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <para>In an OPNFV deployment that uses Openstack Resource Agents,
+            the neutron-openvswitch-agent is killed by Pacemaker when booting,
+            due to Pacemaker misconfiguration.</para>
+          </listitem>
+
+          <listitem>
+            <para>Workaround:</para>
+
+            <para>Starting the <literal>systemd</literal> service manually
+            makes it run successfully. Enea NFV Core 1.0 will be shipped
+            without Openstack Resource Agents, therefore this issue should not
+            affect the user.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Virtual instances are not affected by removing a node from Ceph
+        Storage Cluster</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <para>Engineering wanted to validate the survival of the storage
+            systems when a single disk is removed without causing data loss.
+            Without physical access to the test setup, this test is not
+            feasible.</para>
+          </listitem>
+
+          <listitem>
+            <para>Workaround:</para>
+
+            <itemizedlist>
+              <listitem>
+                <para>The chosen approach was to validate what happens to the
+                Ceph cluster when network connectivity is lost for the Storage
+                interface of one of the nodes. The observed behavior: no
+                impact on a running instance using Ceph for volume
+                storage.</para>
+              </listitem>
+
+              <listitem>
+                <para><ulink
+                url="http://ceph.com/geen-categorie/admin-guide-replacing-a-failed-disk-in-a-ceph-cluster/">Reference
+                information</ulink></para>
+              </listitem>
+            </itemizedlist>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Issue #2 with Openstack Resource Agents and Compute Fencing
+        functionality</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <para>In an OPNFV deployment that uses Openstack Resource Agents,
+            when we configure the <literal>fence_compute</literal> as a
+            Pacemaker resource, the Controller nodes start to reboot each
+            other endlessly.</para>
+          </listitem>
+
+          <listitem>
+            <para>Workaround:</para>
+
+            <para>Enea NFV Core 1.0 will be shipped without Openstack Resource
+            Agents, therefore this issue should not affect the user.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+
+      <listitem>
+        <para>Offline Deploy with Fuel fails at times</para>
+
+        <itemizedlist>
+          <listitem>
+            <para>Description and Impact:</para>
+
+            <para>The Postfix installation and post-install configuration
+            sometimes take longer when the Fuel deployment is performed
+            without Internet connectivity. The <emphasis
+            role="bold">tools</emphasis> Puppet task has a 5 minute completion
+            timeout, causing there to not be enough time left for the other
+            components of the tools task to be executed.</para>
+          </listitem>
+
+          <listitem>
+            <para>Workaround:</para>
+
+            <para>Simply press <literal>Deploy changes</literal> again. Since
+            by now Postfix is installed, it will skip the installation and
+            finish in time.</para>
+          </listitem>
+        </itemizedlist>
+      </listitem>
+    </orderedlist>
+  </section>
+
+  <section condition="hidden" id="bugs-limitations-doc">
+    <title>Documentation</title>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para><emphasis role="bold">PDF navigation</emphasis>: When using
+        links to open other PDFs, or jump to another place in the same PDF,
+        jumping back sometimes fails. This has been observed when opening a
+        PDF in Adobe Reader, inside a browser with PDF add-on, as well as when
+        the browser is configured to open PDF files in an external PDF reader.
+        As a workaround, open the HTML version of the
+        document.<remark>LXCR-3283</remark></para>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <section condition="hidden" id="bugs-limitations-other">
+    <title>Miscellaneous</title>
+
+    <itemizedlist spacing="compact">
+      <listitem>
+        <para></para>
+
+        <remark>list all misc problems here.</remark>
+      </listitem>
+    </itemizedlist>
+  </section>
+
+  <!-- The file with a section below is autocreated by make init
+
+  <xi:include href="jiraissues_generated.xml"
+              xmlns:xi="http://www.w3.org/2001/XInclude" /> -->
+</chapter>
\ No newline at end of file
diff --git a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml-FIX b/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml-FIX
deleted file mode 100644
index fad85a5..0000000
--- a/book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml-FIX
+++ /dev/null
@@ -1,59 +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="bugs-limitations">
-  <title>Known Problems in This Release</title>
-
-  <para>Problems and limitations relevant to the current release are detailed
-  in this chapter. Corrections to bugs detected by Enea are submitted
-  upstream, and remaining issues are listed below.<remark>INFO: The <emphasis
-  role="bold">Release-Specific Problems</emphasis> section further down is
-  generated from JIRA with gen_known_issues.py, but that script is HARDCODED
-  with affectedversion "Enea NFV 1.0" and needs to be adapted when a release
-  info for another ENFV version changes.</remark></para>
-
-  <section condition="hidden" id="bugs-limitations-gen">
-    <title>Release Specific Issues</title>
-
-    <itemizedlist spacing="compact">
-      <listitem>
-        <para><emphasis role="bold">Issue</emphasis>: <remark>Insert all
-        issues specific to this release, along with their relevant
-        CRs</remark></para>
-      </listitem>
-    </itemizedlist>
-  </section>
-
-  <section condition="hidden" id="bugs-limitations-doc">
-    <title>Documentation</title>
-
-    <itemizedlist spacing="compact">
-      <listitem>
-        <para><emphasis role="bold">PDF navigation</emphasis>: When using
-        links to open other PDFs, or jump to another place in the same PDF,
-        jumping back sometimes fails. This has been observed when opening a
-        PDF in Adobe Reader, inside a browser with PDF add-on, as well as when
-        the browser is configured to open PDF files in an external PDF reader.
-        As a workaround, open the HTML version of the
-        document.<remark>LXCR-3283</remark></para>
-      </listitem>
-    </itemizedlist>
-  </section>
-
-  <section condition="hidden" id="bugs-limitations-other">
-    <title>Miscellaneous</title>
-
-    <itemizedlist spacing="compact">
-      <listitem>
-        <para />
-
-        <remark>list all misc problems here.</remark>
-      </listitem>
-    </itemizedlist>
-  </section>
-
-  <!-- The file with a section below is autocreated by make init  -->
-
-  <xi:include href="jiraissues_generated.xml"
-              xmlns:xi="http://www.w3.org/2001/XInclude" />
-</chapter>
\ No newline at end of file
diff --git a/book-enea-nfv-core-release-info/doc/machine_list_generated.xml b/book-enea-nfv-core-release-info/doc/machine_list_generated.xml
deleted file mode 100644
index 2b9d17f..0000000
--- a/book-enea-nfv-core-release-info/doc/machine_list_generated.xml
+++ /dev/null
@@ -1,8 +0,0 @@
-<?xml version="1.0" encoding="ISO-8859-1"?>
-<!DOCTYPE para PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN"
-"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd">
-<para id="machine-list">
-<programlisting># Set MACHINE to ONE of the targets in this release!
-# export MACHINE=inteld1521
-# export MACHINE=qemux86-64</programlisting>
-</para>
diff --git a/book-enea-nfv-core-release-info/doc/summary.xml b/book-enea-nfv-core-release-info/doc/summary.xml
deleted file mode 100644
index 3059386..0000000
--- a/book-enea-nfv-core-release-info/doc/summary.xml
+++ /dev/null
@@ -1,112 +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="relinfo-summary">
-  <title>Summary</title>
-
-  <section id="relinfo-overview">
-    <title>Brief Overview</title>
-
-    <para>For the 1.0 release, the typical use of Fuel as an OpenStack
-    installer is supplemented with ENFV Core unique components, such
-    as:</para>
-
-    <para><itemizedlist>
-        <listitem>
-          <para><ulink url="http://www.opendaylight.org/software">OpenDaylight
-          version: Boron</ulink></para>
-        </listitem>
-
-        <listitem>
-          <para><ulink url="http://onosproject.org/">ONOS version:
-          Drake</ulink></para>
-        </listitem>
-
-        <listitem>
-          <para><ulink
-          url="https://wiki.opnfv.org/service_function_chaining">Service
-          function chaining</ulink></para>
-        </listitem>
-
-        <listitem>
-          <para><ulink url="https://wiki.opnfv.org/sdnvpn">SDN distributed
-          routing and VPN</ulink></para>
-        </listitem>
-
-        <listitem>
-          <para><ulink url="https://wiki.opnfv.org/nfv-kvm">NFV
-          Hypervisors-KVM</ulink></para>
-        </listitem>
-
-        <listitem>
-          <para><ulink url="https://wiki.opnfv.org/ovsnfv">Open vSwitch for
-          NFV</ulink></para>
-        </listitem>
-
-        <listitem>
-          <para><ulink
-          url="https://wiki.opnfv.org/characterize_vswitch_performance_for_telco_nfv_use_cases">VSPERF</ulink></para>
-        </listitem>
-
-        <listitem>
-          <para><ulink
-          url="https://wiki.opnfv.org/display/promise">Promise</ulink></para>
-        </listitem>
-
-        <listitem>
-          <para><ulink
-          url="https://wiki.opnfv.org/display/parser">Parser</ulink></para>
-        </listitem>
-
-        <listitem>
-          <para><ulink
-          url="https://wiki.opnfv.org/display/doctor">Doctor</ulink></para>
-
-          <remark>Change these links and titles accordingly to the appropriate
-          ones for our product.</remark>
-        </listitem>
-      </itemizedlist>This release also includes ENFV-unique configurations of
-    the Hardware and Software stack, provides Fuel as the deployment stage
-    tool in the ENFV CI pipeline, and includes the following:</para>
-
-    <itemizedlist>
-      <listitem>
-        <para>Documentation built by Jenkins</para>
-
-        <itemizedlist>
-          <listitem>
-            <para>Overall ENFV Core documentation</para>
-          </listitem>
-
-          <listitem>
-            <para>This document (release notes)</para>
-          </listitem>
-
-          <listitem>
-            <para>Installation instructions</para>
-          </listitem>
-
-          <listitem>
-            <para>Build-instructions</para>
-          </listitem>
-        </itemizedlist>
-      </listitem>
-
-      <listitem>
-        <para>The Fuel installer image (.iso) built by Jenkins</para>
-      </listitem>
-
-      <listitem>
-        <para>Automated deployment of Fuel with running on bare metal or a
-        nested hypervisor environment (KVM)</para>
-
-        <remark>Is this applicable to us? If not remove this bullet point or
-        change the text to a relevant option</remark>
-      </listitem>
-
-      <listitem>
-        <para>Automated validation of current release deployment</para>
-      </listitem>
-    </itemizedlist>
-  </section>
-</chapter>
\ No newline at end of file