From fd61d2d34342da67f4710d06b4638d61095d816b Mon Sep 17 00:00:00 2001 From: Marian Tanase Date: Fri, 12 Oct 2018 15:51:50 +0300 Subject: ENEA NFV Core 1.1 Release Notes & Installation Guide Updates --- book-enea-nfv-core-installation-guide/doc/book.xml | 3 +- .../doc/high_availability.xml | 5 +- .../doc/images/net_setup_1_edit.png | Bin 0 -> 13989 bytes .../doc/images/net_setup_2_edit.png | Bin 0 -> 13717 bytes .../doc/installation_instructions.xml | 73 ++++--- .../doc/post_deploy_scripts.xml | 37 ++-- .../doc/tacker.xml | 2 +- .../doc/about_release.xml | 77 +++---- .../doc/known_bugs_and_limitations.xml | 233 +++++++-------------- .../doc/main_changes.xml | 54 ++++- .../doc/new_in_this_release.xml | 12 -- 11 files changed, 215 insertions(+), 281 deletions(-) create mode 100644 book-enea-nfv-core-installation-guide/doc/images/net_setup_1_edit.png create mode 100644 book-enea-nfv-core-installation-guide/doc/images/net_setup_2_edit.png delete mode 100644 book-enea-nfv-core-release-info/doc/new_in_this_release.xml 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 @@ +"http://www.oasis-open.org/docbook/xml/4.2/docbookx.dtd" > <trademark class="registered">Enea</trademark> NFV Core Installation Guide 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} - In Hosts under the - Configuration tab, select the template named - Template App Zabbix Agent and click on - Items. + In the Configuration tab, under Templates, look for and select the template named Template App Zabbix Agent and click on Items. 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 Binary files /dev/null and b/book-enea-nfv-core-installation-guide/doc/images/net_setup_1_edit.png 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 Binary files /dev/null and b/book-enea-nfv-core-installation-guide/doc/images/net_setup_2_edit.png 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 @@ Enea NFV Core leverages the work in the OPNFV - Project, delivering selected Installer DVD images together with instructions - on how to setup the Installers and deploy OPNFV releases on a Pharos - compliant test lab. + xpointer="element(EneaNFV_REL_VER/1)" /> leverages the work in the Open + Platform for NFV (OPNFV) Project, delivering selected Installer DVD images + together with instructions on how to setup the Installers and deploy OPNFV + releases on a Pharos compliant test lab. Enea NFV Core uses the Fuel@OPNFV Installer as a deployment facility, hereafter referred to as Fuel. Fuel is an @@ -20,12 +20,11 @@ Enea NFV Core is based on the OPNFV Danube release. The OPNFV download page - provides general instructions for building and installing the Fuel Installer - ISO and also on how to deploy OPNFV Danube using Fuel on a Pharos compliant - test lab. + xpointer="element(EneaNFV_REL_VER/1)" /> is OPNFV compliant. The OPNFV + download page provides general instructions for building and + installing the Fuel Installer ISO and also on how to deploy an OPNFV release + using Fuel on a Pharos compliant test lab. Covering chapters 1-6 of the Fuel Installation Guide is useful for @@ -71,8 +70,9 @@ Fuel - Plugin Developers Guide (optional) + url="https://docs.openstack.org/fuel-docs/latest/plugindocs/fuel-plugin-sdk-guide.html" + userlevel="" vendor="">Fuel Plugin Developers Guide + (optional) @@ -150,9 +150,13 @@ successful. - Enea NFV Core 1.1 can also be installed on a cluster consisting of - servers with mixed CPU architectures. The user can deploy x86 - Controllers and a combination of x86 and aarch64 Compute nodes. + Enea NFV Core can also be installed on a + cluster consisting of servers with mixed CPU architectures. The user can + deploy x86 Controllers and a combination of x86 and aarch64 Compute + nodes. Hardware Requirements for @@ -429,26 +433,16 @@ configured for eth1. - - - - - - + + - - - - - - + + @@ -590,10 +584,12 @@
Installing additional Plugins/Features on FUEL - In order to obtain the extra features used by Enea NFV Core 1.0, a - few added Fuel plugins have to be installed at this stage. Supplementary - configuration will also need to be performed after the installation is - complete. + In order to obtain the extra features used by Enea NFV Core + a few added Fuel plugins have to + be installed at this stage. Supplementary configuration will also need to + be performed after the installation is complete. The following plugins will need to be installed: @@ -627,7 +623,7 @@ $ fuel plugins --install /opt/opnfv/vitrage-1.0-1.0.4-1.noarch.rpm $ fuel plugins --install /opt/opnfv/zabbix_monitoring-2.5-2.5.3-1.noarch.rpm -$ fuel plugins --install /opt/opnfv/tacker-1.0-1.0.0-1.noarch.rpm +$ fuel plugins --install /opt/opnfv/tacker-1.1-1.1.0-1.noarch.rpm $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm Expected output: Plugin ....... was successfully installed. @@ -1456,9 +1452,12 @@ Actor Flags: A-Activity, T-Timeout, G-Aggregation, S-Synchronization for - the 1.1 release, for an updated and comprehensive - list of known issues and limitations, including the "Offloading Modes" - not being applied during the "Verify Networks" step. + the release, for an updated and + comprehensive list of known issues and limitations, including the + "Offloading Modes" not being applied during the "Verify Networks" + step. Setting custom "Offloading Modes" in the Fuel GUI will only 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 @@ Post Deploy Scripts The Post Deploy Scripts is a collection of ENEA specific software that - can be used to easily modify existing environments. These projects can be - used in many situations, from installing new components to configuring + can be used to easily modify existing environments. These scripts can be + used in various situations, from installing new components to configuring existing ones in a fast and efficient way. They are located on the Fuel Master in /opt/enea/postdeployscripts/. @@ -28,7 +28,7 @@ Provider networks only handle layer-2 connectivity for instances, lacking support for features such as routers and floating IP addresses. Please refer to the Openstack + url="https://docs.openstack.org/ocata/install-guide-ubuntu/launch-instance-networks-provider.html">OpenStack documentation for examples on using provider networks. @@ -82,7 +82,7 @@ ./init.sh This will create a hosts file that will be used by Ansible to - associate the nodes into groups and to access them. + associate the nodes into groups and to access them. It will also create a file named samplenetworks.json, which will contain a single @@ -125,31 +125,36 @@ some interfaces included: { "networks":[ { - "name":"prov-net", - "nodes":[ + "allocation-pool": { + "end": "192.168.200.100", + "start": "192.168.200.20" + }, + "enable-dhcp": "True", + "gateway": "192.168.200.1", + "name": "prov-net1", + "network-type": "vlan", + "nodes":[ { - "name":"node-4", - "interfaces":[ - "em2p1s0f5" + "interfaces": ["em5p144s0"], + "name": "node-4" ] }, { - "name":"node-5", - "interfaces":[ - "em2p1s0f5" - ] + "interfaces": ["em5p144s0"], + "name": "node-5" } - ] + ], + "provider-segment": "2251", + "range": "192.168.200.0/24" } ] } - cp samplenetworks.json /opt/enea/postdeployscripts/provider-net/files/networks.jsonThe snippet shown above infers the following: - An Openstack provider network called + An OpenStack provider network called prov-net will be created. 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 @@ - Go to the tacker plugin directory:cd /var/www/nailgun/plugins/tacker-1.0/repositories/tacker + Go to the tacker plugin directory:cd /var/www/nailgun/plugins/tacker-1.1/repositories/tacker 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 @@
Introduction - Enea NFV Core is based on the OPNFV Danube release, and is compatible with the Enea NFV Core is Open Platform for NFV (OPNFV) compliant and it is + compatible with the ETSI NFV reference architecture. It leverages several OPNFV community - projects, including Functest, Yardstick, Doctor, Fuel, and Armband. + projects, including Functest, Yardstick, Doctor, Fuel and Armband. This release consists of the following components: @@ -29,19 +29,13 @@ Installer - Fuel v.10 - - - - OPNFV version - - Danube + Fuel v.11 OpenStack Version - OpenStack Newton + OpenStack Ocata @@ -53,7 +47,7 @@ Pacemaker - 2:9.1.3-1~u16.04+mos4 + 1.1.14-2+enc1~u16.04+mos1 @@ -65,33 +59,31 @@ Open vSwitch - 2.7.0-0ubuntu3 plus other patches + 2.9.0-1+enc1~ubuntu1 DPDK - 16.11.2-3 upgraded to 17.02.1 plus other patches + 17.11.2-1+enc1~ubuntu0.1 Qemu-KVM - 1:2.8+dfsg-3ubuntu1 upgraded to - 1:2.9~rc1+dfsg-0+amos1~u16.04 plus other patches + 2.9+dfsg-0+enc5~u16.04 EDK2 - 0~20160813.de74668f-1ubuntu0.1 plus other - patches + 20160813.de74668f-1+enc1~u16.04 Libvirt - 3.5.0-1ubuntu3 plus other patches + 3.5.0-1+enc3~u16.04 @@ -103,13 +95,13 @@ Aodh - 3.0.2-1~u16.04+mos0 + 4.0.3-2+enc1~u16.04 Ceilometer - 1:7.0.3-1~u16.04+mos2 + 8.1.4-2+enc1~u16.04 @@ -121,7 +113,7 @@ Heat - 1:7.0.2-1~u16.04+mos4 + 8.0.6-1+enc2~u16.04. @@ -131,51 +123,51 @@ - cloud-init + Cloud-init - 0.7.9-90-g61eb03fe-0+amos1~u16.04 + 0.7.9-90-g61eb03fe-0+enc1~u16.04 Ceph Object Storage - 10.2.6-0ubuntu0.16.04.1 + 10.2.6-0+enc2~u16.04 RabbitMQ Messaging - 3.6.6-1+amos1~u16.04+mos1 + 3.6.6-1+enc1~u16.04+mos1 Zabbix - 1:2.4.8-1+trusty plus other patches + 2.4.8-1+enc2~u16.04 - Vitrage + Vitrage / Fuel plugin Vitrage - 1.0.2.dev5 + 1.7.0 / 1.0.1-rc4 Erlang - 1:18.3.4+dfsg-1~u16.04+mos1 + 18.3.4+dfsg-1+enc1~u16.04+mos1 Percona XtraBackup - 2.4.5-1+amos1~u16.04 plus other patches + 2.4.5-1+enc1~u16.04 MongoDB - 1:2.6.10-0+amos1~u16.04 + 2.6.10-0+enc1~u16.04 @@ -198,13 +190,13 @@ MySQL-wsrep - 5.6.36 + 5.6.35-0+enc1~u16.04+mos1 - Galera + Galera-3 - 3.21 + 25.3.15-1 @@ -233,13 +225,7 @@ OpenDaylight - Boron - - - - Congress - - 4.0.0 with Doctor datasource + Oxygen @@ -258,6 +244,11 @@ Information (this document) + + Enea NFV Core Server + Requirement Specification + + - Enea Linux Open Source Report + Enea Linux Open Source Report 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 @@ - Instances fail to boot when using a direct port (SR-IOV) on - ThunderX + ThunderX integrated NICs cannot be used for SR-IOV Description and Impact: - Deployment is successful with SR-IOV enabled interfaces - however, instances fail to boot when a direct bound (SR-IOV) port - is added. This has been tested using a SR-IOV capable PCI Express - Network Interface. As a consequence it is impossible to - passthrough a SR-IOV port on ThunderX. + For the moment ENEA NFV Core is missing the support to + configure ThunderX integrated NICs for deployment. Furthermore, + ThunderX integrated NICs cannot be used for SR-IOV even if + configured manually after deployment. This happens because + ThunderX integrated NICs are themseleves virtual functions and are + incorrectly handled by libvirt when trying to assign them to a + virtual machine. + + It is however possible to deploy with SR-IOV over add-on + interfaces via the PCI-E expansion slots. - Workaround: N/A. + Workaround: there is no workaround for this issue. As an + alternative, the user can configure an external PCI-E NIC for + SR-IOV. - Security groups are not working correctly for ICMP traffic in - deployments with OpenDaylight. + ThunderX integrated NICs cannot be used for PCI passthrough with + direct-physical bound Neutron ports @@ -74,52 +80,32 @@ - 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. - - - - This reproduces on aarch64. On x86 the security groups - work correctly. + PCI Passthrough using direct-physical bound ports also + uses the neutron-sriov-agent. Because the interfaces are + represented as virtual functions, it will be impossible to use + Neutron ports bound as direct-physical (the Nova driver will + identify them as type-VF, not type-PF). + + Due to this, it is not possible to claim PCI devices + using direct-physical bound ports. - - - - Workaround: N/A. - - - - - - Virtual instances do not get IP from DHCP in SFC scenarios with - ODL - - - - Description and Impact: - 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. - - - - The SFC VNFs are not reachable via SSH for management - and configuration. + It is however possible to passthrough any device using + the PCI alias method, which requries configuring a whitelist + of PCI devices and assigning an alias which is set as metadata + in the Nova flavor. - Workaround: Restarting OpenDaylight via - systemctl fixes the problem. + Workaround: + + There is no workaround for this issue. As an alternative, + the user can configure a PCI alias instead. @@ -241,106 +227,6 @@ - - Fuel Healthcheck Stack update test fails - - - - Description and Impact: - - The Platform test case number 5 (Update stack) from the Fuel - Healthcheck sometimes fails. This has no impact on the overal - cluster functionality. - - - - Workaround: N/A. - - - - - - Issue #1 with Openstack Resource Agents and Compute Fencing - functionality - - - - Description and Impact: - - In an OPNFV deployment that uses Openstack Resource Agents, - the neutron-openvswitch-agent is killed by Pacemaker when booting, - due to Pacemaker misconfiguration. - - - - Workaround: - - Starting the systemd service manually - makes it run successfully. Enea NFV Core 1.0.1 is shipped without - Openstack Resource Agents, therefore this issue should not affect - the user. - - - - - - Issue #2 with Openstack Resource Agents and Compute Fencing - functionality - - - - Description and Impact: - - In an OPNFV deployment that uses Openstack Resource Agents, - when we configure the fence_compute as a - Pacemaker resource, the Controller nodes start to reboot each - other endlessly. - - - - Workaround: - - Enea NFV Core 1.0.1 is shipped without Openstack Resource - Agents, therefore this issue should not affect the user. - - - - - - Virtual instances are not affected by removing a node from the - Ceph Storage Cluster - - - - Description and Impact: - - Engineering wanted to validate the survival of storage - systems when a single disk is removed, without causing data loss. - Without physical access to the test setup, this test is not - feasible. - - - - Workaround: - - - - 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. No impact was observed - when running an instance using Ceph for volume storage. - - - - Reference - information - - - - - - Offline Deploy with Fuel fails at times @@ -394,44 +280,67 @@ - Fuel Healthcheck Stack creation with wait condition test, - fails + On Mixed Arch Deployment, only the aarch64 TestVM Cirros image + will be installed by Fuel Description and Impact: - The platform test case (create stack with wait condition) - from the Fuel Healthcheck, fails. This has no impact on overall - cluster functionality. + Due to the fact that Fuel will only deploy the aarch64 + image, Yardstick, Functest, and certain Health Check tests will + not work. These test suites are dependent on a single image name + at a time, and do not know on how to place instances on the + Compute for images that each require a different arch. + + To have both testVM images, the user must add the x86_64 + image manually. - Workaround: N/A. + There is no workaround for the test suites failures. - On Mixed Arch Deployment, only the aarch64 TestVM Cirros image - will be installed by Fuel + Removing QoS policies is unreliable Description and Impact: - Due to the fact that Fuel will only deploy the aarch64 - image, Yardstick, Functest, and certain Health Check tests will - not work. These test suites are dependent on a single image name - at a time, and do not know on how to place instances on the - Compute for images that each require a different arch. + When removing per port bandwidth limiting QoS policies, all + traffic is suddenly dropped. On the the other hand, when removing + QoS policies configured at Openstack network level, traffic flows + as if the rules are still there. + - To have both testVM images, the user must add the x86_64 - image manually. + + There is no workaround. + + + + + + Enabling Ceph for Glance and Nova ephemeral storage makes the + deployment fail on aarch64 + + + + Description and Impact: + + There are multiple configurable Storage Backends in Fuel + settings. Enabling Ceph RBD for images (Glance) and Ceph RBD for + ephemeral volumes (Nova), makes the deployment fail at the CEPH + Ready Check performed on the primary Controller node. This only + occurs when using aarch64 nodes; on x86_64, deployment does not + fail - There is no workaround for the test suites failures. + There is no workaround. The user should not enable these + options. 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 @@ - Main Changes + Main Changes in this Release + +
+ Software Components Updates + + + + Migrated from Openstack Newton to OpenStack Ocata. + + + + Installer has been upgraded from Fuel 10 to Fuel 11. + + + + Upgraded OpenVSwitch from 2.7 to 2.9 + + + + Upgraded DPDK from 16.11 to 17.11. + + +
Mixed Arch Deployment - Enea NFV Core 1.1 can be installed on a cluster - consisting of servers with mixed CPU architectures. The user can deploy - x86 Controllers and a combination of x86 and aarch64 Compute nodes. + Enea NFV Core 1.1 can be installed on a cluster consisting of + servers with mixed CPU architectures. The user can deploy x86 controllers + and a combination of x86 and aarch64 compute nodes. +
+ +
+ Distributed Virtual Routing + + DVR support was validated, as it provides more efficient routing and + floating IP assignment directly at Compute node level. +
+ +
+ Link Aggregation with LACP + + Enea NFV Core 1.1 includes support for Link Aggregation Control + Protocol (LACP) (802.3ad) on data and control plane interfaces. I..e. - + specific Compute and Controller roles can now be assigned to network bonds + as well. +
+ +
+ Post-Deploy Scripts for Provider Networks + + This is a collection of scripts allowing the user to configure + OpenStack Provider Networks, which offer Layer-2 connectivity to instances + with optional support for DHCP and metadata services.
\ 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 @@ - - - New In This Release - -
- Mixed Arch Deployment - - Mixed-arch Deployment: NFV Core 1.1 can be installed on a cluster - consisting of servers with mixed CPU architectures. The user can deploy - x86 Controllers and a combination of x86 and aarch64 Compute nodes. -
- \ No newline at end of file -- cgit v1.2.3-54-g00ecf