From 2c6c61e3570a80dbd6c859840b8a1a9fac7691a4 Mon Sep 17 00:00:00 2001 From: Miruna Paun Date: Wed, 4 Oct 2017 14:17:39 +0200 Subject: USERDOCAPAP-240 included tacker.xml and minor edits, ommissions --- .../doc/about_release.xml | 24 +++--- book-enea-nfv-core-installation-guide/doc/book.xml | 3 +- .../doc/high_availability.xml | 2 +- .../doc/installation_instructions.xml | 93 ++++++++++------------ .../doc/tacker.xml | 56 +++++++++++++ .../doc/use_cases_per_target_node.xml | 6 +- 6 files changed, 116 insertions(+), 68 deletions(-) create mode 100644 book-enea-nfv-core-installation-guide/doc/tacker.xml (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 82d1ced..184a67a 100644 --- a/book-enea-nfv-core-installation-guide/doc/about_release.xml +++ b/book-enea-nfv-core-installation-guide/doc/about_release.xml @@ -4,22 +4,18 @@ About This Release -
- Introduction + 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. - 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. + The available installation options give a high degree of freedom in + how the system is set-up, including architecture, services and features, + etc., however, the noted permutations may not provide an Enea NFV compliant + reference architecture. - The available installation options give a high degree of freedom in - how the system is set-up, including architecture, services and features, - etc., however, the noted permutations may not provide an Enea NFV - compliant reference architecture. - - The audience of this document is assumed to have good grasp of - networking and Unix/Linux/OpenStack administration knowledge. -
+ The audience of this document is assumed to have good grasp of + networking and Unix/Linux/OpenStack administration knowledge.
Definitions and Acronyms diff --git a/book-enea-nfv-core-installation-guide/doc/book.xml b/book-enea-nfv-core-installation-guide/doc/book.xml index fcba092..18673e6 100644 --- a/book-enea-nfv-core-installation-guide/doc/book.xml +++ b/book-enea-nfv-core-installation-guide/doc/book.xml @@ -12,6 +12,7 @@ + - + 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 655654b..4047dd6 100644 --- a/book-enea-nfv-core-installation-guide/doc/high_availability.xml +++ b/book-enea-nfv-core-installation-guide/doc/high_availability.xml @@ -546,7 +546,7 @@ root@node-6:~# systemctl restart vitrage-graph
-
+
Pacemaker High Availability Many of the OpenStack solutions which offer High Availability 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 caf7b58..2de6353 100644 --- a/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml +++ b/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml @@ -14,15 +14,11 @@ deploying OpenStack on a cluster of servers. Enea NFV Core 1.0 is based on the OPNFV Danube - release, available for aarch64 servers through the OPNFV Armband - project that is driven by Enea, which also uses the Fuel Installer. The - Armband project is out of the scope of this document but information is - available online on the OPNFV wiki. - - 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. + 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. Covering chapters 1-6 of the Fuel Installation Guide is useful for @@ -137,19 +133,14 @@ 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: + the installation of Enea NFV Core 1.0 using Fuel, to be successful. + + Hardware Requirements for + Aarch64: - - Hardware Aspect for ThunderX - - Requirement - - Nr. of nodes @@ -199,20 +190,12 @@ - Below are detailed the requirements for validated x86 - configurations: + Hardware Requirements for + x86: - - Hardware Aspect - - Requirement - - Nr. of nodes @@ -267,14 +250,6 @@ - - Hardware Aspect - - Requirement - - Nr. of nodes @@ -515,7 +490,7 @@ Connect to the FUEL UI via the URL provided in the Console - (default: https://10.20.0.2:8443) + (default: http://10.0.6.10) @@ -575,8 +550,8 @@ additional plugins in /opt/opnfv: $ fuel plugins --install /opt/opnfv/vitrage-1.0-1.0.4-1.noarch.rpm -$ fuel plugins --install zabbix_monitoring-2.5-2.5.3-1.noarch.rpm -$ fuel plugins --install tacker-1.0-1.0.0-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/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm Expected output: Plugin ....... was successfully installed. @@ -745,6 +720,10 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm Set VLAN tagging as needed + + + Set an appropriate VLAN ID (default 102) + @@ -910,22 +889,33 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm
-
- Enabling Plugins +
+ Storage, Plugins and Additional Components In the FUEL UI of your Environment, click the - Settings tab and select OpenStack - Services on the left side pane, make sure Tacker is NOT enabled - and save your settings. Tacker functionality will be enabled after - deployment is performed. + Settings tab and select Storage. + Make sure the components shown below in Common and + Storage Backends are enabled: + + + + + + + + Save your settings and select OpenStack Services + on the left side pane. Install Ceilometer and Aodh + should be enabled, while Tacker VNF manager should not. + Tacker functionality will be enabled after deployment is performed. - + - Click on Other on the left pane and do the + Select Other on the left pane and do the following: @@ -949,8 +939,13 @@ $ fuel plugins --install /opt/opnfv/fuel-plugin-kvm-1.0-1.0.0-1.noarch.rpm - Enable and configure the KVM For NFV Plugin. insert - screenshot here of Tacker not checked and KVM checked. + Enable and configure the KVM For NFV Plugin. + + + + + + diff --git a/book-enea-nfv-core-installation-guide/doc/tacker.xml b/book-enea-nfv-core-installation-guide/doc/tacker.xml new file mode 100644 index 0000000..b1f44d4 --- /dev/null +++ b/book-enea-nfv-core-installation-guide/doc/tacker.xml @@ -0,0 +1,56 @@ + + + Installing Tacker + + Tacker is an OpenStack project, + building a generic VNF Manager and a NFV Orchestrator in order to deploy and + operate Network Services and Virtual Network Functions on an NFV + infrastructure platform. It is based on ETSI MANO Architectural Framework + and provides a functional stack to Orchestrate Network Services end-to-end + using VNFs. + + Follow these steps to install the plugin: + + + + ssh into the + fuel-master:ssh ${FUEL_IP} + + + + Go to the tacker plugin directory:cd /var/www/nailgun/plugins/tacker-1.0/repositories/tacker + + + + Run the initialization script:./files/init.shThis + will create a hosts file for ansible + /etc/ansible/hosts of the form:********** +[controllers] +node-3 mac_addr+68:05:ca:46:8b:64 ipmi_ip=0.0.0.0 ipmi_user=****** ipmi_pass=****** +node-2 mac_addr+68:05:ca:46:8c:d4 ipmi_ip=0.0.0.0 ipmi_user=****** ipmi_pass=****** +node-1 mac_addr+68:05:ca:46:8c:45 ipmi_ip=0.0.0.0 ipmi_user=****** ipmi_pass=****** +[main_cont] +node-3 +[computes] +node-5 mac_addr+68:05:ca:46:8c:c9 ipmi_ip=0.0.0.0 ipmi_user=****** ipmi_pass=****** +node-4 mac_addr+68:05:ca:46:8c:c2 ipmi_ip=0.0.0.0 ipmi_user=****** ipmi_pass=****** +[nodes:children] +controllers +computes +********** + + + + Use your favorite text editor to manually edit + ipmi_ip with the ip address of the ipmi interface, + ipmi_user with the user for accessing the ipmi + interface, and ipmi_psss with the password used by + the user to access the ipmi interface for all the nodes. + + + + Run the ansible playbook responsible with the installation and + configuration of tacker plugin.ansible-playbook tacker_deploy.yaml + + + \ No newline at end of file diff --git a/book-enea-nfv-core-installation-guide/doc/use_cases_per_target_node.xml b/book-enea-nfv-core-installation-guide/doc/use_cases_per_target_node.xml index 3d2582c..34d46eb 100644 --- a/book-enea-nfv-core-installation-guide/doc/use_cases_per_target_node.xml +++ b/book-enea-nfv-core-installation-guide/doc/use_cases_per_target_node.xml @@ -2,11 +2,11 @@ - Use Cases + Use Cases This chapter contains use-case examples for each target node pool(s) used/compatible with the Fuel Deployment Tool. - FIXME Team COSNOS/Enea NFV Core will need to fill this chapter with any - and all appropriate use cases. + FIXME Team COSNOS/Enea NFV Core will need to fill this chapter with + any and all appropriate use cases. \ No newline at end of file -- cgit v1.2.3-54-g00ecf