diff options
author | Marian Tanase <mata@enea.se> | 2018-10-12 15:51:50 +0300 |
---|---|---|
committer | Marian Tanase <mata@enea.se> | 2018-11-09 15:58:31 +0200 |
commit | fd61d2d34342da67f4710d06b4638d61095d816b (patch) | |
tree | 8f2e3d0ae4faa7ef78ee08ac451e81aa72e78eea | |
parent | 41a8e44553ec0e25d93c9f581fd293954d44d102 (diff) | |
download | doc-enea-nfv-fd61d2d34342da67f4710d06b4638d61095d816b.tar.gz |
ENEA NFV Core 1.1 Release Notes & Installation Guide Updates
-rw-r--r-- | book-enea-nfv-core-installation-guide/doc/book.xml | 3 | ||||
-rw-r--r-- | book-enea-nfv-core-installation-guide/doc/high_availability.xml | 5 | ||||
-rw-r--r-- | book-enea-nfv-core-installation-guide/doc/images/net_setup_1_edit.png | bin | 0 -> 13989 bytes | |||
-rw-r--r-- | book-enea-nfv-core-installation-guide/doc/images/net_setup_2_edit.png | bin | 0 -> 13717 bytes | |||
-rw-r--r-- | book-enea-nfv-core-installation-guide/doc/installation_instructions.xml | 73 | ||||
-rw-r--r-- | book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml | 37 | ||||
-rw-r--r-- | book-enea-nfv-core-installation-guide/doc/tacker.xml | 2 | ||||
-rw-r--r-- | book-enea-nfv-core-release-info/doc/about_release.xml | 77 | ||||
-rw-r--r-- | book-enea-nfv-core-release-info/doc/known_bugs_and_limitations.xml | 233 | ||||
-rw-r--r-- | book-enea-nfv-core-release-info/doc/main_changes.xml | 54 | ||||
-rw-r--r-- | book-enea-nfv-core-release-info/doc/new_in_this_release.xml | 12 |
11 files changed, 215 insertions, 281 deletions
diff --git a/book-enea-nfv-core-installation-guide/doc/book.xml b/book-enea-nfv-core-installation-guide/doc/book.xml index e161886..de090ae 100644 --- a/book-enea-nfv-core-installation-guide/doc/book.xml +++ b/book-enea-nfv-core-installation-guide/doc/book.xml | |||
@@ -1,7 +1,6 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | 1 | <?xml version="1.0" encoding="ISO-8859-1"?> |
2 | <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" | 2 | <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.2//EN" |
3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" [ | 3 | "http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" > |
4 | ]> | ||
5 | <book id="book_enea_nfv_core_installation_guide"> | 4 | <book id="book_enea_nfv_core_installation_guide"> |
6 | <title><trademark class="registered">Enea</trademark> NFV Core Installation Guide</title> | 5 | <title><trademark class="registered">Enea</trademark> NFV Core Installation Guide</title> |
7 | <!-- OLINKDBPATH_USED_BY_XMLMIND ../../s_docbuild/olinkdb --> | 6 | <!-- OLINKDBPATH_USED_BY_XMLMIND ../../s_docbuild/olinkdb --> |
diff --git a/book-enea-nfv-core-installation-guide/doc/high_availability.xml b/book-enea-nfv-core-installation-guide/doc/high_availability.xml index 4fd4c28..a0c0eb3 100644 --- a/book-enea-nfv-core-installation-guide/doc/high_availability.xml +++ b/book-enea-nfv-core-installation-guide/doc/high_availability.xml | |||
@@ -642,10 +642,7 @@ lastchange={EVENT.DATE} {EVENT.TIME}</programlisting> | |||
642 | </listitem> | 642 | </listitem> |
643 | 643 | ||
644 | <listitem> | 644 | <listitem> |
645 | <para>In <literal>Hosts</literal> under the | 645 | <para>In the <literal>Configuration</literal> tab, under <literal>Templates</literal>, look for and select the template named <filename>Template App Zabbix Agent</filename> and click on <literal>Items</literal>.</para> |
646 | <literal>Configuration</literal> tab, select the template named | ||
647 | <literal>Template App Zabbix Agent</literal> and click on | ||
648 | <literal>Items</literal>.</para> | ||
649 | </listitem> | 646 | </listitem> |
650 | 647 | ||
651 | <listitem> | 648 | <listitem> |
diff --git a/book-enea-nfv-core-installation-guide/doc/images/net_setup_1_edit.png b/book-enea-nfv-core-installation-guide/doc/images/net_setup_1_edit.png new file mode 100644 index 0000000..616bbdc --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/images/net_setup_1_edit.png | |||
Binary files differ | |||
diff --git a/book-enea-nfv-core-installation-guide/doc/images/net_setup_2_edit.png b/book-enea-nfv-core-installation-guide/doc/images/net_setup_2_edit.png new file mode 100644 index 0000000..60f3551 --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/images/net_setup_2_edit.png | |||
Binary files differ | |||
diff --git a/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml b/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml index a094351..0fbdc1b 100644 --- a/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml +++ b/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml | |||
@@ -7,10 +7,10 @@ | |||
7 | <para>Enea NFV Core <xi:include | 7 | <para>Enea NFV Core <xi:include |
8 | href="../../s_docsrc_common/pardoc-distro.xml" | 8 | href="../../s_docsrc_common/pardoc-distro.xml" |
9 | xmlns:xi="http://www.w3.org/2001/XInclude" | 9 | xmlns:xi="http://www.w3.org/2001/XInclude" |
10 | xpointer="element(EneaNFV_REL_VER/1)" /> leverages the work in the OPNFV | 10 | xpointer="element(EneaNFV_REL_VER/1)" /> leverages the work in the Open |
11 | Project, delivering selected Installer DVD images together with instructions | 11 | Platform for NFV (OPNFV) Project, delivering selected Installer DVD images |
12 | on how to setup the Installers and deploy OPNFV releases on a Pharos | 12 | together with instructions on how to setup the Installers and deploy OPNFV |
13 | compliant test lab.</para> | 13 | releases on a Pharos compliant test lab.</para> |
14 | 14 | ||
15 | <para>Enea NFV Core uses the Fuel@OPNFV Installer as a deployment facility, | 15 | <para>Enea NFV Core uses the Fuel@OPNFV Installer as a deployment facility, |
16 | hereafter referred to as <emphasis role="bold">Fuel</emphasis>. Fuel is an | 16 | hereafter referred to as <emphasis role="bold">Fuel</emphasis>. Fuel is an |
@@ -20,12 +20,11 @@ | |||
20 | <para>Enea NFV Core <xi:include | 20 | <para>Enea NFV Core <xi:include |
21 | href="../../s_docsrc_common/pardoc-distro.xml" | 21 | href="../../s_docsrc_common/pardoc-distro.xml" |
22 | xmlns:xi="http://www.w3.org/2001/XInclude" | 22 | xmlns:xi="http://www.w3.org/2001/XInclude" |
23 | xpointer="element(EneaNFV_REL_VER/1)" /> is based on the OPNFV <emphasis | 23 | xpointer="element(EneaNFV_REL_VER/1)" /> is OPNFV compliant. The <ulink |
24 | role="bold">Danube </emphasis>release. The <ulink | 24 | url="https://www.opnfv.org/software/downloads/release-archives">OPNFV |
25 | url="https://www.opnfv.org/software/downloads">OPNFV download page</ulink> | 25 | download page</ulink> provides general instructions for building and |
26 | provides general instructions for building and installing the Fuel Installer | 26 | installing the Fuel Installer ISO and also on how to deploy an OPNFV release |
27 | ISO and also on how to deploy OPNFV Danube using Fuel on a Pharos compliant | 27 | using Fuel on a Pharos compliant test lab.</para> |
28 | test lab.</para> | ||
29 | 28 | ||
30 | <note> | 29 | <note> |
31 | <para>Covering chapters 1-6 of the Fuel Installation Guide is useful for | 30 | <para>Covering chapters 1-6 of the Fuel Installation Guide is useful for |
@@ -71,8 +70,9 @@ | |||
71 | 70 | ||
72 | <listitem> | 71 | <listitem> |
73 | <para><ulink | 72 | <para><ulink |
74 | url="http://docs.openstack.org/developer/fueldocs/plugindocs/fuel-plugin-sdk-guide.html">Fuel | 73 | url="https://docs.openstack.org/fuel-docs/latest/plugindocs/fuel-plugin-sdk-guide.html" |
75 | Plugin Developers Guide</ulink> (optional)</para> | 74 | userlevel="" vendor="">Fuel Plugin Developers Guide</ulink> |
75 | (optional)</para> | ||
76 | </listitem> | 76 | </listitem> |
77 | 77 | ||
78 | <listitem> | 78 | <listitem> |
@@ -150,9 +150,13 @@ | |||
150 | successful.</para> | 150 | successful.</para> |
151 | 151 | ||
152 | <note> | 152 | <note> |
153 | <para>Enea NFV Core 1.1 can also be installed on a cluster consisting of | 153 | <para>Enea NFV Core <xi:include |
154 | servers with mixed CPU architectures. The user can deploy x86 | 154 | href="../../s_docsrc_common/pardoc-distro.xml" |
155 | Controllers and a combination of x86 and aarch64 Compute nodes.</para> | 155 | xmlns:xi="http://www.w3.org/2001/XInclude" |
156 | xpointer="element(EneaNFV_REL_VER/1)" /> can also be installed on a | ||
157 | cluster consisting of servers with mixed CPU architectures. The user can | ||
158 | deploy x86 Controllers and a combination of x86 and aarch64 Compute | ||
159 | nodes.</para> | ||
156 | </note> | 160 | </note> |
157 | 161 | ||
158 | <para><emphasis role="bold">Hardware Requirements for | 162 | <para><emphasis role="bold">Hardware Requirements for |
@@ -429,26 +433,16 @@ | |||
429 | configured for eth1.</para> | 433 | configured for eth1.</para> |
430 | 434 | ||
431 | <mediaobject> | 435 | <mediaobject> |
432 | <imageobject role="fo"> | 436 | <imageobject> |
433 | <imagedata align="center" contentwidth="600" | 437 | <imagedata align="center" fileref="images/net_setup_1_edit.png" /> |
434 | fileref="images/net_setup_1.svg" /> | ||
435 | </imageobject> | ||
436 | |||
437 | <imageobject role="html"> | ||
438 | <imagedata align="center" fileref="images/net_setup_1.png" /> | ||
439 | </imageobject> | 438 | </imageobject> |
440 | </mediaobject> | 439 | </mediaobject> |
441 | 440 | ||
442 | <para></para> | 441 | <para></para> |
443 | 442 | ||
444 | <mediaobject> | 443 | <mediaobject> |
445 | <imageobject role="fo"> | 444 | <imageobject> |
446 | <imagedata align="center" contentwidth="600" | 445 | <imagedata align="center" fileref="images/net_setup_2_edit.png" /> |
447 | fileref="images/net_setup_2.svg" /> | ||
448 | </imageobject> | ||
449 | |||
450 | <imageobject role="html"> | ||
451 | <imagedata align="center" fileref="images/net_setup_2.png" /> | ||
452 | </imageobject> | 446 | </imageobject> |
453 | </mediaobject> | 447 | </mediaobject> |
454 | </listitem> | 448 | </listitem> |
@@ -590,10 +584,12 @@ | |||
590 | <section id="add_feat_fuel"> | 584 | <section id="add_feat_fuel"> |
591 | <title>Installing additional Plugins/Features on FUEL</title> | 585 | <title>Installing additional Plugins/Features on FUEL</title> |
592 | 586 | ||
593 | <para>In order to obtain the extra features used by Enea NFV Core 1.0, a | 587 | <para>In order to obtain the extra features used by Enea NFV Core |
594 | few added Fuel plugins have to be installed at this stage. Supplementary | 588 | <xi:include href="../../s_docsrc_common/pardoc-distro.xml" |
595 | configuration will also need to be performed after the installation is | 589 | xmlns:xi="http://www.w3.org/2001/XInclude" |
596 | complete.</para> | 590 | xpointer="element(EneaNFV_REL_VER/1)" /> a few added Fuel plugins have to |
591 | be installed at this stage. Supplementary configuration will also need to | ||
592 | be performed after the installation is complete.</para> | ||
597 | 593 | ||
598 | <para>The following plugins will need to be installed:</para> | 594 | <para>The following plugins will need to be installed:</para> |
599 | 595 | ||
@@ -627,7 +623,7 @@ | |||
627 | 623 | ||
628 | <programlisting>$ fuel plugins --install /opt/opnfv/vitrage-1.0-1.0.4-1.noarch.rpm | 624 | <programlisting>$ fuel plugins --install /opt/opnfv/vitrage-1.0-1.0.4-1.noarch.rpm |
629 | $ fuel plugins --install /opt/opnfv/zabbix_monitoring-2.5-2.5.3-1.noarch.rpm | 625 | $ fuel plugins --install /opt/opnfv/zabbix_monitoring-2.5-2.5.3-1.noarch.rpm |
630 | $ fuel plugins --install /opt/opnfv/tacker-1.0-1.0.0-1.noarch.rpm | 626 | $ fuel plugins --install /opt/opnfv/tacker-1.1-1.1.0-1.noarch.rpm |
631 | $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm</programlisting> | 627 | $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm</programlisting> |
632 | 628 | ||
633 | <para>Expected output: <programlisting>Plugin ....... was successfully installed.</programlisting></para> | 629 | <para>Expected output: <programlisting>Plugin ....... was successfully installed.</programlisting></para> |
@@ -1456,9 +1452,12 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization | |||
1456 | <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml" | 1452 | <xi:include href="../../s_docbuild/olinkdb/pardoc-names.xml" |
1457 | xmlns:xi="http://www.w3.org/2001/XInclude" | 1453 | xmlns:xi="http://www.w3.org/2001/XInclude" |
1458 | xpointer="element(book_enea_nfv_core_release_info/1)" /></olink> for | 1454 | xpointer="element(book_enea_nfv_core_release_info/1)" /></olink> for |
1459 | the <phrase>1.1</phrase> release, for an updated and comprehensive | 1455 | the <xi:include href="../../s_docsrc_common/pardoc-distro.xml" |
1460 | list of known issues and limitations, including the "Offloading Modes" | 1456 | xmlns:xi="http://www.w3.org/2001/XInclude" |
1461 | not being applied during the "Verify Networks" step.</para> | 1457 | xpointer="element(EneaNFV_REL_VER/1)" /> release, for an updated and |
1458 | comprehensive list of known issues and limitations, including the | ||
1459 | "Offloading Modes" not being applied during the "Verify Networks" | ||
1460 | step.</para> | ||
1462 | 1461 | ||
1463 | <para>Setting custom "Offloading Modes" in the Fuel GUI will only | 1462 | <para>Setting custom "Offloading Modes" in the Fuel GUI will only |
1464 | apply during provisioning, not during "Verify Networks". If your | 1463 | apply during provisioning, not during "Verify Networks". If your |
diff --git a/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml b/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml index c4668e4..19a05d9 100644 --- a/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml +++ b/book-enea-nfv-core-installation-guide/doc/post_deploy_scripts.xml | |||
@@ -5,8 +5,8 @@ | |||
5 | <title>Post Deploy Scripts</title> | 5 | <title>Post Deploy Scripts</title> |
6 | 6 | ||
7 | <para>The Post Deploy Scripts is a collection of ENEA specific software that | 7 | <para>The Post Deploy Scripts is a collection of ENEA specific software that |
8 | can be used to easily modify existing environments. These projects can be | 8 | can be used to easily modify existing environments. These scripts can be |
9 | used in many situations, from installing new components to configuring | 9 | used in various situations, from installing new components to configuring |
10 | existing ones in a fast and efficient way. They are located on the Fuel | 10 | existing ones in a fast and efficient way. They are located on the Fuel |
11 | Master in <literal>/opt/enea/postdeployscripts/</literal>.</para> | 11 | Master in <literal>/opt/enea/postdeployscripts/</literal>.</para> |
12 | 12 | ||
@@ -28,7 +28,7 @@ | |||
28 | <para>Provider networks only handle layer-2 connectivity for instances, | 28 | <para>Provider networks only handle layer-2 connectivity for instances, |
29 | lacking support for features such as routers and floating IP addresses. | 29 | lacking support for features such as routers and floating IP addresses. |
30 | Please refer to the <ulink | 30 | Please refer to the <ulink |
31 | url="https://docs.openstack.org/ocata/install-guide-ubuntu/launch-instance-networks-provider.html">Openstack | 31 | url="https://docs.openstack.org/ocata/install-guide-ubuntu/launch-instance-networks-provider.html">OpenStack |
32 | documentation</ulink> for examples on using provider networks.</para> | 32 | documentation</ulink> for examples on using provider networks.</para> |
33 | </note> | 33 | </note> |
34 | 34 | ||
@@ -82,7 +82,7 @@ | |||
82 | ./init.sh</programlisting></para> | 82 | ./init.sh</programlisting></para> |
83 | 83 | ||
84 | <para>This will create a hosts file that will be used by Ansible to | 84 | <para>This will create a hosts file that will be used by Ansible to |
85 | associate the nodes into groups and to access them. </para> | 85 | associate the nodes into groups and to access them.</para> |
86 | 86 | ||
87 | <para>It will also create a file named | 87 | <para>It will also create a file named |
88 | <filename>samplenetworks.json</filename>, which will contain a single | 88 | <filename>samplenetworks.json</filename>, which will contain a single |
@@ -125,31 +125,36 @@ | |||
125 | some interfaces included:<programlisting> { | 125 | some interfaces included:<programlisting> { |
126 | "networks":[ | 126 | "networks":[ |
127 | { | 127 | { |
128 | "name":"prov-net", | 128 | "allocation-pool": { |
129 | "nodes":[ | 129 | "end": "192.168.200.100", |
130 | "start": "192.168.200.20" | ||
131 | }, | ||
132 | "enable-dhcp": "True", | ||
133 | "gateway": "192.168.200.1", | ||
134 | "name": "prov-net1", | ||
135 | "network-type": "vlan", | ||
136 | "nodes":[ | ||
130 | { | 137 | { |
131 | "name":"node-4", | 138 | "interfaces": ["em5p144s0"], |
132 | "interfaces":[ | 139 | "name": "node-4" |
133 | "em2p1s0f5" | ||
134 | ] | 140 | ] |
135 | }, | 141 | }, |
136 | { | 142 | { |
137 | "name":"node-5", | 143 | "interfaces": ["em5p144s0"], |
138 | "interfaces":[ | 144 | "name": "node-5" |
139 | "em2p1s0f5" | ||
140 | ] | ||
141 | } | 145 | } |
142 | ] | 146 | ], |
147 | "provider-segment": "2251", | ||
148 | "range": "192.168.200.0/24" | ||
143 | } | 149 | } |
144 | ] | 150 | ] |
145 | } | 151 | } |
146 | |||
147 | cp samplenetworks.json /opt/enea/postdeployscripts/provider-net/files/networks.json</programlisting>The | 152 | cp samplenetworks.json /opt/enea/postdeployscripts/provider-net/files/networks.json</programlisting>The |
148 | snippet shown above infers the following:</para> | 153 | snippet shown above infers the following:</para> |
149 | 154 | ||
150 | <itemizedlist> | 155 | <itemizedlist> |
151 | <listitem> | 156 | <listitem> |
152 | <para>An Openstack provider network called | 157 | <para>An OpenStack provider network called |
153 | <filename>prov-net</filename> will be created.</para> | 158 | <filename>prov-net</filename> will be created.</para> |
154 | </listitem> | 159 | </listitem> |
155 | 160 | ||
diff --git a/book-enea-nfv-core-installation-guide/doc/tacker.xml b/book-enea-nfv-core-installation-guide/doc/tacker.xml index 55cf18c..00ab0ec 100644 --- a/book-enea-nfv-core-installation-guide/doc/tacker.xml +++ b/book-enea-nfv-core-installation-guide/doc/tacker.xml | |||
@@ -16,7 +16,7 @@ | |||
16 | 16 | ||
17 | <orderedlist> | 17 | <orderedlist> |
18 | <listitem> | 18 | <listitem> |
19 | <para>Go to the tacker plugin directory:<programlisting>cd /var/www/nailgun/plugins/tacker-1.0/repositories/tacker</programlisting></para> | 19 | <para>Go to the tacker plugin directory:<programlisting>cd /var/www/nailgun/plugins/tacker-1.1/repositories/tacker</programlisting></para> |
20 | </listitem> | 20 | </listitem> |
21 | 21 | ||
22 | <listitem> | 22 | <listitem> |
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 5347e33..bd4fa95 100644 --- a/book-enea-nfv-core-release-info/doc/about_release.xml +++ b/book-enea-nfv-core-release-info/doc/about_release.xml | |||
@@ -7,11 +7,11 @@ | |||
7 | <section id="intro"> | 7 | <section id="intro"> |
8 | <title>Introduction</title> | 8 | <title>Introduction</title> |
9 | 9 | ||
10 | <para>Enea NFV Core is based on the OPNFV <emphasis | 10 | <para>Enea NFV Core is Open Platform for NFV (OPNFV) compliant and it is |
11 | role="bold">Danube</emphasis> release, and is compatible with the <ulink | 11 | compatible with the <ulink |
12 | url="http://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.02.01_60/gs_NFV002v010201p.pdf">ETSI | 12 | url="http://www.etsi.org/deliver/etsi_gs/NFV/001_099/002/01.02.01_60/gs_NFV002v010201p.pdf">ETSI |
13 | NFV reference architecture</ulink>. It leverages several OPNFV community | 13 | NFV reference architecture</ulink>. It leverages several OPNFV community |
14 | projects, including Functest, Yardstick, Doctor, Fuel, and Armband.</para> | 14 | projects, including Functest, Yardstick, Doctor, Fuel and Armband.</para> |
15 | 15 | ||
16 | <para>This release consists of the following components:</para> | 16 | <para>This release consists of the following components:</para> |
17 | 17 | ||
@@ -29,19 +29,13 @@ | |||
29 | <row> | 29 | <row> |
30 | <entry>Installer</entry> | 30 | <entry>Installer</entry> |
31 | 31 | ||
32 | <entry>Fuel v.10</entry> | 32 | <entry>Fuel v.11</entry> |
33 | </row> | ||
34 | |||
35 | <row> | ||
36 | <entry>OPNFV version</entry> | ||
37 | |||
38 | <entry>Danube</entry> | ||
39 | </row> | 33 | </row> |
40 | 34 | ||
41 | <row> | 35 | <row> |
42 | <entry>OpenStack Version</entry> | 36 | <entry>OpenStack Version</entry> |
43 | 37 | ||
44 | <entry>OpenStack Newton</entry> | 38 | <entry>OpenStack Ocata</entry> |
45 | </row> | 39 | </row> |
46 | 40 | ||
47 | <row> | 41 | <row> |
@@ -53,7 +47,7 @@ | |||
53 | <row> | 47 | <row> |
54 | <entry>Pacemaker</entry> | 48 | <entry>Pacemaker</entry> |
55 | 49 | ||
56 | <entry>2:9.1.3-1~u16.04+mos4</entry> | 50 | <entry>1.1.14-2+enc1~u16.04+mos1</entry> |
57 | </row> | 51 | </row> |
58 | 52 | ||
59 | <row> | 53 | <row> |
@@ -65,33 +59,31 @@ | |||
65 | <row> | 59 | <row> |
66 | <entry>Open vSwitch</entry> | 60 | <entry>Open vSwitch</entry> |
67 | 61 | ||
68 | <entry>2.7.0-0ubuntu3 plus other patches</entry> | 62 | <entry>2.9.0-1+enc1~ubuntu1</entry> |
69 | </row> | 63 | </row> |
70 | 64 | ||
71 | <row> | 65 | <row> |
72 | <entry>DPDK</entry> | 66 | <entry>DPDK</entry> |
73 | 67 | ||
74 | <entry>16.11.2-3 upgraded to 17.02.1 plus other patches</entry> | 68 | <entry>17.11.2-1+enc1~ubuntu0.1</entry> |
75 | </row> | 69 | </row> |
76 | 70 | ||
77 | <row> | 71 | <row> |
78 | <entry>Qemu-KVM</entry> | 72 | <entry>Qemu-KVM</entry> |
79 | 73 | ||
80 | <entry align="left">1:2.8+dfsg-3ubuntu1 upgraded to | 74 | <entry align="left">2.9+dfsg-0+enc5~u16.04</entry> |
81 | 1:2.9~rc1+dfsg-0+amos1~u16.04 plus other patches</entry> | ||
82 | </row> | 75 | </row> |
83 | 76 | ||
84 | <row> | 77 | <row> |
85 | <entry>EDK2</entry> | 78 | <entry>EDK2</entry> |
86 | 79 | ||
87 | <entry align="left">0~20160813.de74668f-1ubuntu0.1 plus other | 80 | <entry align="left">20160813.de74668f-1+enc1~u16.04</entry> |
88 | patches</entry> | ||
89 | </row> | 81 | </row> |
90 | 82 | ||
91 | <row> | 83 | <row> |
92 | <entry>Libvirt</entry> | 84 | <entry>Libvirt</entry> |
93 | 85 | ||
94 | <entry>3.5.0-1ubuntu3 plus other patches</entry> | 86 | <entry>3.5.0-1+enc3~u16.04</entry> |
95 | </row> | 87 | </row> |
96 | 88 | ||
97 | <row> | 89 | <row> |
@@ -103,13 +95,13 @@ | |||
103 | <row> | 95 | <row> |
104 | <entry>Aodh</entry> | 96 | <entry>Aodh</entry> |
105 | 97 | ||
106 | <entry>3.0.2-1~u16.04+mos0</entry> | 98 | <entry>4.0.3-2+enc1~u16.04</entry> |
107 | </row> | 99 | </row> |
108 | 100 | ||
109 | <row> | 101 | <row> |
110 | <entry>Ceilometer</entry> | 102 | <entry>Ceilometer</entry> |
111 | 103 | ||
112 | <entry>1:7.0.3-1~u16.04+mos2</entry> | 104 | <entry>8.1.4-2+enc1~u16.04</entry> |
113 | </row> | 105 | </row> |
114 | 106 | ||
115 | <row> | 107 | <row> |
@@ -121,7 +113,7 @@ | |||
121 | <row> | 113 | <row> |
122 | <entry>Heat</entry> | 114 | <entry>Heat</entry> |
123 | 115 | ||
124 | <entry>1:7.0.2-1~u16.04+mos4</entry> | 116 | <entry>8.0.6-1+enc2~u16.04.</entry> |
125 | </row> | 117 | </row> |
126 | 118 | ||
127 | <row> | 119 | <row> |
@@ -131,51 +123,51 @@ | |||
131 | </row> | 123 | </row> |
132 | 124 | ||
133 | <row> | 125 | <row> |
134 | <entry>cloud-init</entry> | 126 | <entry>Cloud-init</entry> |
135 | 127 | ||
136 | <entry>0.7.9-90-g61eb03fe-0+amos1~u16.04</entry> | 128 | <entry>0.7.9-90-g61eb03fe-0+enc1~u16.04</entry> |
137 | </row> | 129 | </row> |
138 | 130 | ||
139 | <row> | 131 | <row> |
140 | <entry>Ceph Object Storage</entry> | 132 | <entry>Ceph Object Storage</entry> |
141 | 133 | ||
142 | <entry>10.2.6-0ubuntu0.16.04.1</entry> | 134 | <entry>10.2.6-0+enc2~u16.04</entry> |
143 | </row> | 135 | </row> |
144 | 136 | ||
145 | <row> | 137 | <row> |
146 | <entry>RabbitMQ Messaging</entry> | 138 | <entry>RabbitMQ Messaging</entry> |
147 | 139 | ||
148 | <entry>3.6.6-1+amos1~u16.04+mos1</entry> | 140 | <entry>3.6.6-1+enc1~u16.04+mos1</entry> |
149 | </row> | 141 | </row> |
150 | 142 | ||
151 | <row> | 143 | <row> |
152 | <entry>Zabbix</entry> | 144 | <entry>Zabbix</entry> |
153 | 145 | ||
154 | <entry>1:2.4.8-1+trusty plus other patches</entry> | 146 | <entry>2.4.8-1+enc2~u16.04</entry> |
155 | </row> | 147 | </row> |
156 | 148 | ||
157 | <row> | 149 | <row> |
158 | <entry>Vitrage</entry> | 150 | <entry>Vitrage / Fuel plugin Vitrage</entry> |
159 | 151 | ||
160 | <entry>1.0.2.dev5</entry> | 152 | <entry>1.7.0 / 1.0.1-rc4</entry> |
161 | </row> | 153 | </row> |
162 | 154 | ||
163 | <row> | 155 | <row> |
164 | <entry>Erlang</entry> | 156 | <entry>Erlang</entry> |
165 | 157 | ||
166 | <entry>1:18.3.4+dfsg-1~u16.04+mos1</entry> | 158 | <entry>18.3.4+dfsg-1+enc1~u16.04+mos1</entry> |
167 | </row> | 159 | </row> |
168 | 160 | ||
169 | <row> | 161 | <row> |
170 | <entry>Percona XtraBackup</entry> | 162 | <entry>Percona XtraBackup</entry> |
171 | 163 | ||
172 | <entry>2.4.5-1+amos1~u16.04 plus other patches</entry> | 164 | <entry>2.4.5-1+enc1~u16.04</entry> |
173 | </row> | 165 | </row> |
174 | 166 | ||
175 | <row> | 167 | <row> |
176 | <entry>MongoDB</entry> | 168 | <entry>MongoDB</entry> |
177 | 169 | ||
178 | <entry>1:2.6.10-0+amos1~u16.04</entry> | 170 | <entry>2.6.10-0+enc1~u16.04</entry> |
179 | </row> | 171 | </row> |
180 | </tbody> | 172 | </tbody> |
181 | </tgroup> | 173 | </tgroup> |
@@ -198,13 +190,13 @@ | |||
198 | <row> | 190 | <row> |
199 | <entry>MySQL-wsrep</entry> | 191 | <entry>MySQL-wsrep</entry> |
200 | 192 | ||
201 | <entry>5.6.36</entry> | 193 | <entry>5.6.35-0+enc1~u16.04+mos1</entry> |
202 | </row> | 194 | </row> |
203 | 195 | ||
204 | <row> | 196 | <row> |
205 | <entry>Galera</entry> | 197 | <entry>Galera-3</entry> |
206 | 198 | ||
207 | <entry>3.21</entry> | 199 | <entry>25.3.15-1</entry> |
208 | </row> | 200 | </row> |
209 | 201 | ||
210 | <row> | 202 | <row> |
@@ -233,13 +225,7 @@ | |||
233 | <row> | 225 | <row> |
234 | <entry>OpenDaylight</entry> | 226 | <entry>OpenDaylight</entry> |
235 | 227 | ||
236 | <entry>Boron</entry> | 228 | <entry>Oxygen</entry> |
237 | </row> | ||
238 | |||
239 | <row> | ||
240 | <entry>Congress</entry> | ||
241 | |||
242 | <entry>4.0.0 with Doctor datasource</entry> | ||
243 | </row> | 229 | </row> |
244 | </tbody> | 230 | </tbody> |
245 | </tgroup> | 231 | </tgroup> |
@@ -259,6 +245,11 @@ | |||
259 | </listitem> | 245 | </listitem> |
260 | 246 | ||
261 | <listitem> | 247 | <listitem> |
248 | <para><trademark class="registered">Enea</trademark> NFV Core Server | ||
249 | Requirement Specification</para> | ||
250 | </listitem> | ||
251 | |||
252 | <listitem> | ||
262 | <para><olink targetdoc="book_enea_nfv_core_installation_guide" | 253 | <para><olink targetdoc="book_enea_nfv_core_installation_guide" |
263 | targetptr="book_enea_nfv_core_installation_guide"><trademark | 254 | targetptr="book_enea_nfv_core_installation_guide"><trademark |
264 | class="registered">Enea</trademark> NFV Core User's Guide Installation | 255 | class="registered">Enea</trademark> NFV Core User's Guide Installation |
@@ -266,7 +257,7 @@ | |||
266 | </listitem> | 257 | </listitem> |
267 | 258 | ||
268 | <listitem condition="hidden"> | 259 | <listitem condition="hidden"> |
269 | <para> Enea Linux Open Source Report</para> | 260 | <para>Enea Linux Open Source Report</para> |
270 | </listitem> | 261 | </listitem> |
271 | 262 | ||
272 | <listitem condition="hidden"> | 263 | <listitem condition="hidden"> |
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 index bc682ab..1aa394d 100644 --- 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 | |||
@@ -44,29 +44,35 @@ | |||
44 | </listitem> | 44 | </listitem> |
45 | 45 | ||
46 | <listitem> | 46 | <listitem> |
47 | <para>Instances fail to boot when using a direct port (SR-IOV) on | 47 | <para>ThunderX integrated NICs cannot be used for SR-IOV</para> |
48 | ThunderX</para> | ||
49 | 48 | ||
50 | <itemizedlist> | 49 | <itemizedlist> |
51 | <listitem> | 50 | <listitem> |
52 | <para>Description and Impact:</para> | 51 | <para>Description and Impact:</para> |
53 | 52 | ||
54 | <para>Deployment is successful with SR-IOV enabled interfaces | 53 | <para>For the moment ENEA NFV Core is missing the support to |
55 | however, instances fail to boot when a direct bound (SR-IOV) port | 54 | configure ThunderX integrated NICs for deployment. Furthermore, |
56 | is added. This has been tested using a SR-IOV capable PCI Express | 55 | ThunderX integrated NICs cannot be used for SR-IOV even if |
57 | Network Interface. As a consequence it is impossible to | 56 | configured manually after deployment. This happens because |
58 | passthrough a SR-IOV port on ThunderX.</para> | 57 | ThunderX integrated NICs are themseleves virtual functions and are |
58 | incorrectly handled by libvirt when trying to assign them to a | ||
59 | virtual machine.</para> | ||
60 | |||
61 | <para>It is however possible to deploy with SR-IOV over add-on | ||
62 | interfaces via the PCI-E expansion slots.</para> | ||
59 | </listitem> | 63 | </listitem> |
60 | 64 | ||
61 | <listitem> | 65 | <listitem> |
62 | <para>Workaround: N/A.</para> | 66 | <para>Workaround: there is no workaround for this issue. As an |
67 | alternative, the user can configure an external PCI-E NIC for | ||
68 | SR-IOV.</para> | ||
63 | </listitem> | 69 | </listitem> |
64 | </itemizedlist> | 70 | </itemizedlist> |
65 | </listitem> | 71 | </listitem> |
66 | 72 | ||
67 | <listitem> | 73 | <listitem> |
68 | <para>Security groups are not working correctly for ICMP traffic in | 74 | <para>ThunderX integrated NICs cannot be used for PCI passthrough with |
69 | deployments with OpenDaylight.</para> | 75 | direct-physical bound Neutron ports</para> |
70 | 76 | ||
71 | <itemizedlist> | 77 | <itemizedlist> |
72 | <listitem> | 78 | <listitem> |
@@ -74,52 +80,32 @@ | |||
74 | 80 | ||
75 | <itemizedlist> | 81 | <itemizedlist> |
76 | <listitem> | 82 | <listitem> |
77 | <para>When OPNFV is deployed with OpenDaylight as an SDN | 83 | <para>PCI Passthrough using direct-physical bound ports also |
78 | controller, the Security Groups rules pertaining to ICMP do | 84 | uses the neutron-sriov-agent. Because the interfaces are |
79 | not work as expected. The OpenFlow rules describing the ICMP | 85 | represented as virtual functions, it will be impossible to use |
80 | rules are inconsistent, so VMs can be pinged even when this is | 86 | Neutron ports bound as direct-physical (the Nova driver will |
81 | not desired.</para> | 87 | identify them as type-VF, not type-PF).</para> |
82 | </listitem> | 88 | |
83 | 89 | <para>Due to this, it is not possible to claim PCI devices | |
84 | <listitem> | 90 | using direct-physical bound ports.</para> |
85 | <para>This reproduces on aarch64. On x86 the security groups | ||
86 | work correctly.</para> | ||
87 | </listitem> | 91 | </listitem> |
88 | </itemizedlist> | 92 | </itemizedlist> |
89 | </listitem> | ||
90 | |||
91 | <listitem> | ||
92 | <para>Workaround: N/A.</para> | ||
93 | </listitem> | ||
94 | </itemizedlist> | ||
95 | </listitem> | ||
96 | |||
97 | <listitem> | ||
98 | <para>Virtual instances do not get IP from DHCP in SFC scenarios with | ||
99 | ODL</para> | ||
100 | |||
101 | <itemizedlist> | ||
102 | <listitem> | ||
103 | <para>Description and Impact:</para> | ||
104 | 93 | ||
105 | <itemizedlist> | 94 | <itemizedlist> |
106 | <listitem> | 95 | <listitem> |
107 | <para>After a fresh deploy of OPNFV with OpenDaylight and the | 96 | <para>It is however possible to passthrough any device using |
108 | Service Function Chaining scenario configurations, instances | 97 | the PCI alias method, which requries configuring a whitelist |
109 | fail to get IP from DHCP, due to OpenDaylight | 98 | of PCI devices and assigning an alias which is set as metadata |
110 | malfunctioning.</para> | 99 | in the Nova flavor.</para> |
111 | </listitem> | ||
112 | |||
113 | <listitem> | ||
114 | <para>The SFC VNFs are not reachable via SSH for management | ||
115 | and configuration.</para> | ||
116 | </listitem> | 100 | </listitem> |
117 | </itemizedlist> | 101 | </itemizedlist> |
118 | </listitem> | 102 | </listitem> |
119 | 103 | ||
120 | <listitem> | 104 | <listitem> |
121 | <para>Workaround: Restarting OpenDaylight via | 105 | <para>Workaround:</para> |
122 | <literal>systemctl</literal> fixes the problem.</para> | 106 | |
107 | <para>There is no workaround for this issue. As an alternative, | ||
108 | the user can configure a PCI alias instead.</para> | ||
123 | </listitem> | 109 | </listitem> |
124 | </itemizedlist> | 110 | </itemizedlist> |
125 | </listitem> | 111 | </listitem> |
@@ -242,106 +228,6 @@ | |||
242 | </listitem> | 228 | </listitem> |
243 | 229 | ||
244 | <listitem> | 230 | <listitem> |
245 | <para>Fuel Healthcheck Stack update test fails</para> | ||
246 | |||
247 | <itemizedlist> | ||
248 | <listitem> | ||
249 | <para>Description and Impact:</para> | ||
250 | |||
251 | <para>The Platform test case number 5 (Update stack) from the Fuel | ||
252 | Healthcheck sometimes fails. This has no impact on the overal | ||
253 | cluster functionality.</para> | ||
254 | </listitem> | ||
255 | |||
256 | <listitem> | ||
257 | <para>Workaround: N/A.</para> | ||
258 | </listitem> | ||
259 | </itemizedlist> | ||
260 | </listitem> | ||
261 | |||
262 | <listitem> | ||
263 | <para>Issue #1 with Openstack Resource Agents and Compute Fencing | ||
264 | functionality</para> | ||
265 | |||
266 | <itemizedlist> | ||
267 | <listitem> | ||
268 | <para>Description and Impact:</para> | ||
269 | |||
270 | <para>In an OPNFV deployment that uses Openstack Resource Agents, | ||
271 | the neutron-openvswitch-agent is killed by Pacemaker when booting, | ||
272 | due to Pacemaker misconfiguration.</para> | ||
273 | </listitem> | ||
274 | |||
275 | <listitem> | ||
276 | <para>Workaround:</para> | ||
277 | |||
278 | <para>Starting the <literal>systemd</literal> service manually | ||
279 | makes it run successfully. Enea NFV Core 1.0.1 is shipped without | ||
280 | Openstack Resource Agents, therefore this issue should not affect | ||
281 | the user.</para> | ||
282 | </listitem> | ||
283 | </itemizedlist> | ||
284 | </listitem> | ||
285 | |||
286 | <listitem> | ||
287 | <para>Issue #2 with Openstack Resource Agents and Compute Fencing | ||
288 | functionality</para> | ||
289 | |||
290 | <itemizedlist> | ||
291 | <listitem> | ||
292 | <para>Description and Impact:</para> | ||
293 | |||
294 | <para>In an OPNFV deployment that uses Openstack Resource Agents, | ||
295 | when we configure the <literal>fence_compute</literal> as a | ||
296 | Pacemaker resource, the Controller nodes start to reboot each | ||
297 | other endlessly.</para> | ||
298 | </listitem> | ||
299 | |||
300 | <listitem> | ||
301 | <para>Workaround:</para> | ||
302 | |||
303 | <para>Enea NFV Core 1.0.1 is shipped without Openstack Resource | ||
304 | Agents, therefore this issue should not affect the user.</para> | ||
305 | </listitem> | ||
306 | </itemizedlist> | ||
307 | </listitem> | ||
308 | |||
309 | <listitem> | ||
310 | <para>Virtual instances are not affected by removing a node from the | ||
311 | Ceph Storage Cluster</para> | ||
312 | |||
313 | <itemizedlist> | ||
314 | <listitem> | ||
315 | <para>Description and Impact:</para> | ||
316 | |||
317 | <para>Engineering wanted to validate the survival of storage | ||
318 | systems when a single disk is removed, without causing data loss. | ||
319 | Without physical access to the test setup, this test is not | ||
320 | feasible.</para> | ||
321 | </listitem> | ||
322 | |||
323 | <listitem> | ||
324 | <para>Workaround:</para> | ||
325 | |||
326 | <itemizedlist> | ||
327 | <listitem> | ||
328 | <para>The chosen approach was to validate what happens to the | ||
329 | Ceph cluster, when network connectivity is lost for the | ||
330 | Storage interface of one of the nodes. No impact was observed | ||
331 | when running an instance using Ceph for volume storage.</para> | ||
332 | </listitem> | ||
333 | |||
334 | <listitem> | ||
335 | <para><ulink | ||
336 | url="http://ceph.com/geen-categorie/admin-guide-replacing-a-failed-disk-in-a-ceph-cluster/">Reference | ||
337 | information</ulink></para> | ||
338 | </listitem> | ||
339 | </itemizedlist> | ||
340 | </listitem> | ||
341 | </itemizedlist> | ||
342 | </listitem> | ||
343 | |||
344 | <listitem> | ||
345 | <para>Offline Deploy with Fuel fails at times</para> | 231 | <para>Offline Deploy with Fuel fails at times</para> |
346 | 232 | ||
347 | <itemizedlist> | 233 | <itemizedlist> |
@@ -394,44 +280,67 @@ | |||
394 | </listitem> | 280 | </listitem> |
395 | 281 | ||
396 | <listitem> | 282 | <listitem> |
397 | <para>Fuel Healthcheck Stack creation with wait condition test, | 283 | <para>On Mixed Arch Deployment, only the aarch64 TestVM Cirros image |
398 | fails</para> | 284 | will be installed by Fuel</para> |
399 | 285 | ||
400 | <itemizedlist> | 286 | <itemizedlist> |
401 | <listitem> | 287 | <listitem> |
402 | <para>Description and Impact:</para> | 288 | <para>Description and Impact:</para> |
403 | 289 | ||
404 | <para>The platform test case (create stack with wait condition) | 290 | <para>Due to the fact that Fuel will only deploy the aarch64 |
405 | from the Fuel Healthcheck, fails. This has no impact on overall | 291 | image, Yardstick, Functest, and certain Health Check tests will |
406 | cluster functionality.</para> | 292 | not work. These test suites are dependent on a single image name |
293 | at a time, and do not know on how to place instances on the | ||
294 | Compute for images that each require a different arch.</para> | ||
295 | |||
296 | <para>To have both testVM images, the user must add the x86_64 | ||
297 | image manually.</para> | ||
407 | </listitem> | 298 | </listitem> |
408 | 299 | ||
409 | <listitem> | 300 | <listitem> |
410 | <para>Workaround: N/A.</para> | 301 | <para>There is no workaround for the test suites failures.</para> |
411 | </listitem> | 302 | </listitem> |
412 | </itemizedlist> | 303 | </itemizedlist> |
413 | </listitem> | 304 | </listitem> |
414 | 305 | ||
415 | <listitem> | 306 | <listitem> |
416 | <para>On Mixed Arch Deployment, only the aarch64 TestVM Cirros image | 307 | <para>Removing QoS policies is unreliable</para> |
417 | will be installed by Fuel</para> | ||
418 | 308 | ||
419 | <itemizedlist> | 309 | <itemizedlist> |
420 | <listitem> | 310 | <listitem> |
421 | <para>Description and Impact:</para> | 311 | <para>Description and Impact:</para> |
422 | 312 | ||
423 | <para>Due to the fact that Fuel will only deploy the aarch64 | 313 | <para>When removing per port bandwidth limiting QoS policies, all |
424 | image, Yardstick, Functest, and certain Health Check tests will | 314 | traffic is suddenly dropped. On the the other hand, when removing |
425 | not work. These test suites are dependent on a single image name | 315 | QoS policies configured at Openstack network level, traffic flows |
426 | at a time, and do not know on how to place instances on the | 316 | as if the rules are still there.</para> |
427 | Compute for images that each require a different arch.</para> | 317 | </listitem> |
428 | 318 | ||
429 | <para>To have both testVM images, the user must add the x86_64 | 319 | <listitem> |
430 | image manually.</para> | 320 | <para>There is no workaround.</para> |
321 | </listitem> | ||
322 | </itemizedlist> | ||
323 | </listitem> | ||
324 | |||
325 | <listitem> | ||
326 | <para>Enabling Ceph for Glance and Nova ephemeral storage makes the | ||
327 | deployment fail on aarch64</para> | ||
328 | |||
329 | <itemizedlist> | ||
330 | <listitem> | ||
331 | <para>Description and Impact:</para> | ||
332 | |||
333 | <para>There are multiple configurable Storage Backends in Fuel | ||
334 | settings. Enabling Ceph RBD for images (Glance) and Ceph RBD for | ||
335 | ephemeral volumes (Nova), makes the deployment fail at the CEPH | ||
336 | Ready Check performed on the primary Controller node. This only | ||
337 | occurs when using aarch64 nodes; on x86_64, deployment does not | ||
338 | fail</para> | ||
431 | </listitem> | 339 | </listitem> |
432 | 340 | ||
433 | <listitem> | 341 | <listitem> |
434 | <para>There is no workaround for the test suites failures.</para> | 342 | <para>There is no workaround. The user should not enable these |
343 | options.</para> | ||
435 | </listitem> | 344 | </listitem> |
436 | </itemizedlist> | 345 | </itemizedlist> |
437 | </listitem> | 346 | </listitem> |
diff --git a/book-enea-nfv-core-release-info/doc/main_changes.xml b/book-enea-nfv-core-release-info/doc/main_changes.xml index 53c1f0f..b79237d 100644 --- a/book-enea-nfv-core-release-info/doc/main_changes.xml +++ b/book-enea-nfv-core-release-info/doc/main_changes.xml | |||
@@ -1,12 +1,58 @@ | |||
1 | <?xml version="1.0" encoding="ISO-8859-1"?> | 1 | <?xml version="1.0" encoding="ISO-8859-1"?> |
2 | <chapter id="main_changes"> | 2 | <chapter id="main_changes"> |
3 | <title>Main Changes</title> | 3 | <title>Main Changes in this Release</title> |
4 | |||
5 | <section id="sw_comps_upd"> | ||
6 | <title>Software Components Updates</title> | ||
7 | |||
8 | <itemizedlist> | ||
9 | <listitem> | ||
10 | <para>Migrated from Openstack Newton to OpenStack Ocata.</para> | ||
11 | </listitem> | ||
12 | |||
13 | <listitem> | ||
14 | <para>Installer has been upgraded from Fuel 10 to Fuel 11.</para> | ||
15 | </listitem> | ||
16 | |||
17 | <listitem> | ||
18 | <para>Upgraded OpenVSwitch from 2.7 to 2.9</para> | ||
19 | </listitem> | ||
20 | |||
21 | <listitem> | ||
22 | <para>Upgraded DPDK from 16.11 to 17.11.</para> | ||
23 | </listitem> | ||
24 | </itemizedlist> | ||
25 | </section> | ||
4 | 26 | ||
5 | <section id="mixed_arch"> | 27 | <section id="mixed_arch"> |
6 | <title>Mixed Arch Deployment</title> | 28 | <title>Mixed Arch Deployment</title> |
7 | 29 | ||
8 | <para>Enea NFV Core <phrase>1.1</phrase> can be installed on a cluster | 30 | <para>Enea NFV Core 1.1 can be installed on a cluster consisting of |
9 | consisting of servers with mixed CPU architectures. The user can deploy | 31 | servers with mixed CPU architectures. The user can deploy x86 controllers |
10 | x86 Controllers and a combination of x86 and aarch64 Compute nodes.</para> | 32 | and a combination of x86 and aarch64 compute nodes.</para> |
33 | </section> | ||
34 | |||
35 | <section id="dvr"> | ||
36 | <title>Distributed Virtual Routing</title> | ||
37 | |||
38 | <para>DVR support was validated, as it provides more efficient routing and | ||
39 | floating IP assignment directly at Compute node level.</para> | ||
40 | </section> | ||
41 | |||
42 | <section id="lacp"> | ||
43 | <title>Link Aggregation with LACP</title> | ||
44 | |||
45 | <para>Enea NFV Core 1.1 includes support for Link Aggregation Control | ||
46 | Protocol (LACP) (802.3ad) on data and control plane interfaces. I..e. - | ||
47 | specific Compute and Controller roles can now be assigned to network bonds | ||
48 | as well.</para> | ||
49 | </section> | ||
50 | |||
51 | <section id="post_dep"> | ||
52 | <title>Post-Deploy Scripts for Provider Networks</title> | ||
53 | |||
54 | <para>This is a collection of scripts allowing the user to configure | ||
55 | OpenStack Provider Networks, which offer Layer-2 connectivity to instances | ||
56 | with optional support for DHCP and metadata services.</para> | ||
11 | </section> | 57 | </section> |
12 | </chapter> \ No newline at end of file | 58 | </chapter> \ No newline at end of file |
diff --git a/book-enea-nfv-core-release-info/doc/new_in_this_release.xml b/book-enea-nfv-core-release-info/doc/new_in_this_release.xml deleted file mode 100644 index 55b9735..0000000 --- a/book-enea-nfv-core-release-info/doc/new_in_this_release.xml +++ /dev/null | |||
@@ -1,12 +0,0 @@ | |||
1 | <?xml version="1.0" encoding="UTF-8"?> | ||
2 | <chapter id="new_features"> | ||
3 | <title>New In This Release</title> | ||
4 | |||
5 | <section> | ||
6 | <title>Mixed Arch Deployment</title> | ||
7 | |||
8 | <para>Mixed-arch Deployment: NFV Core 1.1 can be installed on a cluster | ||
9 | consisting of servers with mixed CPU architectures. The user can deploy | ||
10 | x86 Controllers and a combination of x86 and aarch64 Compute nodes.</para> | ||
11 | </section> | ||
12 | </chapter> \ No newline at end of file | ||