From 467269e04948e00ef12eb8c18affa6b0d4dd67e6 Mon Sep 17 00:00:00 2001 From: Miruna Paun Date: Mon, 20 Nov 2017 19:00:03 +0100 Subject: COSNOSCR-576 final corrections made to the install. guide and rel info. ver update. --- .../doc/about_release.xml | 8 +- .../doc/high_availability.xml | 133 +++++++++++++-------- .../doc/hw_features.xml | 7 +- .../doc/installation_instructions.xml | 50 +++++--- .../doc/tacker.xml | 2 +- 5 files changed, 131 insertions(+), 69 deletions(-) (limited to 'book-enea-nfv-core-installation-guide') diff --git a/book-enea-nfv-core-installation-guide/doc/about_release.xml b/book-enea-nfv-core-installation-guide/doc/about_release.xml index 184a67a..1a74169 100644 --- a/book-enea-nfv-core-installation-guide/doc/about_release.xml +++ b/book-enea-nfv-core-installation-guide/doc/about_release.xml @@ -5,9 +5,11 @@ About This Release This document provides guidelines on how to install and configure the - 1.0 release of Enea NFV Core when using Fuel as a deployment tool, including - the required software and hardware configurations, resulting in an Enea NFV - compliant deployment. + release of Enea NFV Core when using + Fuel as a deployment tool, including the required software and hardware + configurations, resulting in an Enea NFV compliant deployment. The available installation options give a high degree of freedom in how the system is set-up, including architecture, services and features, 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 e6dc825..6d27b00 100644 --- a/book-enea-nfv-core-installation-guide/doc/high_availability.xml +++ b/book-enea-nfv-core-installation-guide/doc/high_availability.xml @@ -2,18 +2,25 @@ High Availability Guide - Enea NFV Core 1.0 has been designed to provide high availability - characteristics that are needed for developing and deploying telco-grade NFV - solutions on top of our OPNFV based platform. The High Availability subject - in general is very wide and still an important focus in both opensource - communities and the independent/proprietary solutions market. - - Enea NFV Core 1.0 aims to initially leverage the efforts in the - upstream OPNFV and OpenStack opensource projects, combining solutions from - both worlds in an effort to provide flexibility and use-case coverage. Enea - has long term expertise and proprietary solutions addressing High - Availability for telco applications, which are subject to integration with - the NFV based solutions. + Enea NFV Core has been designed to provide high + availability characteristics that are needed for developing and deploying + telco-grade NFV solutions on top of our OPNFV based platform. The High + Availability subject in general is very wide and still an important focus in + both opensource communities and the independent/proprietary solutions + market. + + Enea NFV Core aims to initially leverage the + efforts in the upstream OPNFV and OpenStack opensource projects, combining + solutions from both worlds in an effort to provide flexibility and use-case + coverage. Enea has long term expertise and proprietary solutions addressing + High Availability for telco applications, which are subject to integration + with the NFV based solutions.
High Availability Levels @@ -94,7 +101,10 @@ communicate with Controllers in order to update the states of the virtual and physical resources. - For this component Enea NFV Core 1.0 makes use of Vitrage, an + For this component Enea NFV Core makes use of Vitrage, an OpenStack related project used for Root Cause Analysis. The integration into the platform is done with the help of a Fuel Plugin which has been developed internally by Enea. @@ -130,13 +140,16 @@ can be accessed from one of the servers that act as OpenStack Controller nodes. - In Enea NFV Core 1.0 the Administrator can also access the - Zabbix dashboard to perform supplementary configurations. The same - applies for the Vitrage tool, which comes with its own Horizon - dashboard, enabling the user to visually inspect the faults reported - by the monitoring tools through visual representations of the virtual - and physical resources, the relationships between them and the fault - correlation. + In Enea NFV Core the Administrator can also + access the Zabbix dashboard to perform supplementary configurations. + The same applies for the Vitrage tool, which comes with its own + Horizon dashboard, enabling the user to visually inspect the faults + reported by the monitoring tools through visual representations of the + virtual and physical resources, the relationships between them and the + fault correlation. For Vitrage, users will usually want to configure additional use-cases and describe relationships between components via template @@ -152,10 +165,13 @@ the VNFs. The role of the Consumer thus falls to that of a VNF Manager and Orchestrator. - Enea NFV Core 1.0 provides VNF management capabilities using - Tacker, which is an OpenStack project that implements a generic VNF - Manager and Orchestrator, according to the ETSI MANO Architectural - Framework. + Enea NFV Core provides VNF management + capabilities using Tacker, which is an OpenStack project that + implements a generic VNF Manager and Orchestrator, according to the + ETSI MANO Architectural Framework. @@ -196,7 +212,11 @@ - Enea NFV Core 1.0 uses the same approach described above: + Enea NFV Core uses the same approach + described above: @@ -287,8 +307,11 @@ - The ENEA NFV Core 1.0 Pre-Release fully covers the required - Doctor functionality only for the Vitrage and Zabbix + The ENEA NFV Core Pre-Release fully covers the + required Doctor functionality only for the Vitrage and Zabbix components.
@@ -309,7 +332,9 @@ The Zabbix configuration dashboard is available at the same IP address where OpenStack can be reached, e.g. - http://10.0.101.42/zabbix. + http://10.0.101.42/zabbix. Default username and + password are admin and zabbix + respectively. @@ -422,7 +447,10 @@ - Next, select the Media tab and click + Reselect the admin alias to enter the + Configuration of Users screen once again. + + Select the Media tab and click Add to create and modify a new media type. A popup menu will appear for New Media. Fill each field with the values below: @@ -436,10 +464,10 @@ Send to: e.g. rabbit://nova:Q1Vt9iocA8OpXKOPoUYOLKie@192.168.0.4:5673/ - You need to search for this in - /etc/vitrage/vitrage.conf or in /etc/nova/nova.conf - transport_url. It is vital that the url contains the - ending " / ". + This url can be found in either + /etc/vitrage/vitrage.conf or in + /etc/nova/nova.conf. Only one url is needed and it is + vital that the url contains the ending " / ". @@ -473,7 +501,7 @@ Configuration tab select Actions. Then, under the Action tab, fill in the parameter fields with the - values below and click Add + values below: @@ -538,7 +566,7 @@ lastchange={EVENT.DATE} {EVENT.TIME} - Send to Users: add Admin + Send to Users: add admin @@ -578,7 +606,7 @@ lastchange={EVENT.DATE} {EVENT.TIME} In order to make use of these features, Vitrage supports additional configurations via yaml templates that - must be placed in /etc/vitrage/templates on the nodes + must be placed in /etc/vitrage/templates on the node that have the Vitrage role. @@ -667,8 +695,11 @@ root@node-6:~# systemctl restart vitrage-graph
Vitrage Customizations - Enea NFV Core 1.0 has added custom features for Vitrage which - allow two kinds of actions: + Enea NFV Core has added custom features for + Vitrage which allow two kinds of actions: @@ -866,12 +897,15 @@ RemoteOnline: [ node-4.domain.tld node-5.domain.tld ]
Pacemaker Fencing - ENEA NFV Core 1.0 makes use of the fencing capabilities of - Pacemaker to isolate faulty nodes and trigger recovery actions by means - of power cycling the failed nodes. Fencing is configured by creating - STONITH type resources for each of the servers in the - cluster, both Controller nodes and Compute nodes. The - STONITH adapter for fencing the nodes is + ENEA NFV Core makes use of the fencing + capabilities of Pacemaker to isolate faulty nodes and trigger recovery + actions by means of power cycling the failed nodes. Fencing is + configured by creating STONITH type resources for + each of the servers in the cluster, both Controller nodes and Compute + nodes. The STONITH adapter for fencing the nodes is fence_ipmilan, which makes use of the IPMI capabilities of the ThunderX servers. @@ -965,9 +999,12 @@ ipaddr=10.0.100.155 login=ADMIN passwd=ADMIN op monitor interval="60s" - ENEA NFV Core 1.0 aims to validate and integrate this work and to - make this feature available in the platform aimed as an alternative to the - Doctor framework, where simple, autonomous recovery of running instances - is desired. + ENEA NFV Core aims to validate and integrate + this work and to make this feature available in the platform aimed as an + alternative to the Doctor framework, where simple, autonomous recovery of + running instances is desired.
\ No newline at end of file diff --git a/book-enea-nfv-core-installation-guide/doc/hw_features.xml b/book-enea-nfv-core-installation-guide/doc/hw_features.xml index 6b4ac39..cdba908 100644 --- a/book-enea-nfv-core-installation-guide/doc/hw_features.xml +++ b/book-enea-nfv-core-installation-guide/doc/hw_features.xml @@ -2,8 +2,11 @@ Hardware Features - Enea NFV Core 1.0 leverages certain Hardware features within the - ThunderX SoCs, the most important being DPDK and SR-IOV. + Enea NFV Core leverages certain Hardware features + within the ThunderX SoCs, the most important being DPDK and SR-IOV. Enea's mission, through the OPNFV Armband project, is to extend the OPNFV capabilities on aarch64 commercial servers, including the Cavium 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 6a67b74..0bbcdc3 100644 --- a/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml +++ b/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml @@ -4,17 +4,24 @@ Installation Instructions - Enea NFV Core 1.0 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. + 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. Enea NFV Core uses the Fuel@OPNFV Installer as a deployment facility, hereafter referred to as Fuel. Fuel is an automated deployment tool capable of automatically provisioning and deploying OpenStack on a cluster of servers. - Enea NFV Core 1.0 is based on the OPNFV Danube - release. The 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 @@ -131,9 +138,16 @@
Hardware Requirements - Enea NFV Core 1.0 has been validated with the requirements shown - below, which represent the recommended configuration that must be met for - the installation of Enea NFV Core 1.0 using Fuel, to be successful. + Enea NFV Core has been validated with the + requirements shown below, which represent the recommended configuration + that must be met for the installation of Enea NFV Core using Fuel, to be + successful. Hardware Requirements for Aarch64: @@ -310,8 +324,11 @@ - Mount the Enea NFV Core 1.0 ISO file/media as a boot device to - the Fuel Master VM. + Mount the Enea NFV Core ISO file/media as a boot + device to the Fuel Master VM. @@ -1140,10 +1157,13 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm Configure Workload Acceleration - Enea NFV Core 1.0 supports NFV workload acceleration features such - as Huge Pages, Single-Root I/O Virtualization (SR-IOV), Data Plane - Developer Kit (DPDK), Non-Uniform Memory Access (NUMA) and CPU pinning. - Please refer to the Enea NFV Core supports NFV workload + acceleration features such as Huge Pages, Single-Root I/O Virtualization + (SR-IOV), Data Plane Developer Kit (DPDK), Non-Uniform Memory Access + (NUMA) and CPU pinning. Please refer to the Fuel User Guide for more information. @@ -1216,7 +1236,7 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm Please check the Release Notes for the 1.0.1 - release of ENFV Core when using Fuel as a deployment tool, + release of Enea NFV Core when using Fuel as a deployment tool, Change this to an Olink to the Release notes once the ID has been created for that book. Add the ID to pardoc-names.xml and pardoc-common if needed, then updated the OlinkDBfor an diff --git a/book-enea-nfv-core-installation-guide/doc/tacker.xml b/book-enea-nfv-core-installation-guide/doc/tacker.xml index e1791db..55cf18c 100644 --- a/book-enea-nfv-core-installation-guide/doc/tacker.xml +++ b/book-enea-nfv-core-installation-guide/doc/tacker.xml @@ -57,7 +57,7 @@ computes
-
+
Using Tacker After Tacker has been installed and configured, perform the -- cgit v1.2.3-54-g00ecf