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 +- 7 files changed, 60 insertions(+), 60 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 (limited to 'book-enea-nfv-core-installation-guide') 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 -- cgit v1.2.3-54-g00ecf