diff options
author | Miruna Paun <Miruna.Paun@enea.com> | 2017-09-29 16:11:21 +0200 |
---|---|---|
committer | Miruna Paun <Miruna.Paun@enea.com> | 2017-09-29 16:11:21 +0200 |
commit | 24f09fb531b41a7ecb7df915cb4c7cd8df77f3ad (patch) | |
tree | 1ab4bb2e91a6b21ff256677c2bc875981fcdb556 /book-enea-nfv-core-installation-guide | |
parent | cc001420304566cd252f2c6323dec3a826a12954 (diff) | |
download | doc-enea-nfv-24f09fb531b41a7ecb7df915cb4c7cd8df77f3ad.tar.gz |
Adding lastest changes to the ENC1.0 Installation Guide
USERDOCAP-240
Signed-off-by: Miruna Paun <Miruna.Paun@enea.com>
Diffstat (limited to 'book-enea-nfv-core-installation-guide')
-rw-r--r-- | book-enea-nfv-core-installation-guide/doc/high_availability.xml | 20 | ||||
-rw-r--r-- | book-enea-nfv-core-installation-guide/doc/installation_instructions.xml | 48 |
2 files changed, 36 insertions, 32 deletions
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 93f6468..4fe02fe 100644 --- a/book-enea-nfv-core-installation-guide/doc/high_availability.xml +++ b/book-enea-nfv-core-installation-guide/doc/high_availability.xml | |||
@@ -53,14 +53,14 @@ | |||
53 | framework for the high availability of Network Services, on top of a | 53 | framework for the high availability of Network Services, on top of a |
54 | virtualized infrastructure. The key feature is immediate notification of | 54 | virtualized infrastructure. The key feature is immediate notification of |
55 | unavailability of virtualized resources from VIM, to process recovery of | 55 | unavailability of virtualized resources from VIM, to process recovery of |
56 | VNFs on them. </para> | 56 | VNFs on them.</para> |
57 | 57 | ||
58 | <para>The Doctor project has also collaborated with the Availability | 58 | <para>The Doctor project has also collaborated with the Availability |
59 | project on identifying gaps in upstream projects, such as but not | 59 | project on identifying gaps in upstream projects, such as but not |
60 | exclusively OpenStack. It has also worked towards implementing missing | 60 | exclusively OpenStack. It has also worked towards implementing missing |
61 | features and improving functionality, with a good example being the Aodh | 61 | features and improving functionality, with a good example being the Aodh |
62 | event based alarms, which allow for fast notifications when certain | 62 | event based alarms, which allow for fast notifications when certain |
63 | predefined events occur. </para> | 63 | predefined events occur.</para> |
64 | 64 | ||
65 | <para>The Doctor project also produced an architectural design and a | 65 | <para>The Doctor project also produced an architectural design and a |
66 | reference implementation based on opensource components, which will be | 66 | reference implementation based on opensource components, which will be |
@@ -128,7 +128,7 @@ | |||
128 | interfaces. These can be visual dashboards like OpenStack Horizon or | 128 | interfaces. These can be visual dashboards like OpenStack Horizon or |
129 | Fuel Dashboard, or via CLI tools like the OpenStack unified CLI, that | 129 | Fuel Dashboard, or via CLI tools like the OpenStack unified CLI, that |
130 | can be accessed from one of the servers that act as OpenStack | 130 | can be accessed from one of the servers that act as OpenStack |
131 | Controller nodes. </para> | 131 | Controller nodes.</para> |
132 | 132 | ||
133 | <para>In Enea NFV Core 1.0 the Administrator can also access the | 133 | <para>In Enea NFV Core 1.0 the Administrator can also access the |
134 | Zabbix dashboard to perform supplementary configurations. The same | 134 | Zabbix dashboard to perform supplementary configurations. The same |
@@ -136,7 +136,7 @@ | |||
136 | dashboard, enabling the user to visually inspect the faults reported | 136 | dashboard, enabling the user to visually inspect the faults reported |
137 | by the monitoring tools through visual representations of the virtual | 137 | by the monitoring tools through visual representations of the virtual |
138 | and physical resources, the relationships between them and the fault | 138 | and physical resources, the relationships between them and the fault |
139 | correlation. </para> | 139 | correlation.</para> |
140 | 140 | ||
141 | <para>For Vitrage, users will usually want to configure additional | 141 | <para>For Vitrage, users will usually want to configure additional |
142 | use-cases and describe relationships between components via template | 142 | use-cases and describe relationships between components via template |
@@ -221,7 +221,7 @@ | |||
221 | 221 | ||
222 | <listitem> | 222 | <listitem> |
223 | <para>The NFVI sends monitoring events for the resources the VIM has | 223 | <para>The NFVI sends monitoring events for the resources the VIM has |
224 | been subscribed to. </para> | 224 | been subscribed to.</para> |
225 | 225 | ||
226 | <note> | 226 | <note> |
227 | <para>This subscription message exchange between the VIM and NFVI | 227 | <para>This subscription message exchange between the VIM and NFVI |
@@ -251,7 +251,7 @@ | |||
251 | <para>This step shows database lookup geared to find the virtual | 251 | <para>This step shows database lookup geared to find the virtual |
252 | resources affected by the detected fault. Vitrage will perform | 252 | resources affected by the detected fault. Vitrage will perform |
253 | various calculations to detect what virtual resources are affected | 253 | various calculations to detect what virtual resources are affected |
254 | by the raw failure presented by Zabbix. </para> | 254 | by the raw failure presented by Zabbix.</para> |
255 | 255 | ||
256 | <para>Vitrage can be configured via templates to correlate instances | 256 | <para>Vitrage can be configured via templates to correlate instances |
257 | with the physical hosts they are running on, so that if a compute | 257 | with the physical hosts they are running on, so that if a compute |
@@ -259,7 +259,7 @@ | |||
259 | typical use-case is to mark the compute node down | 259 | typical use-case is to mark the compute node down |
260 | (<literal>mark_host_down</literal>) and update the states of all | 260 | (<literal>mark_host_down</literal>) and update the states of all |
261 | instances running on them. This is done by issuing Nova API calls | 261 | instances running on them. This is done by issuing Nova API calls |
262 | for each of these instances. </para> | 262 | for each of these instances.</para> |
263 | 263 | ||
264 | <para>Step 5c. shows the Controller (Nova in this case) acting upon | 264 | <para>Step 5c. shows the Controller (Nova in this case) acting upon |
265 | the state change of the instance and issuing an event alarm to | 265 | the state change of the instance and issuing an event alarm to |
@@ -555,7 +555,7 @@ root@node-6:~# systemctl restart vitrage-graph</programlisting> | |||
555 | control plane services, so it can effectively provide redundancy and | 555 | control plane services, so it can effectively provide redundancy and |
556 | recovery for the Controller nodes only. A reason for this is that | 556 | recovery for the Controller nodes only. A reason for this is that |
557 | Controller nodes and Compute nodes essentially have very different High | 557 | Controller nodes and Compute nodes essentially have very different High |
558 | Availability requirements that need to be considered. </para> | 558 | Availability requirements that need to be considered.</para> |
559 | 559 | ||
560 | <para>Typically, for Controller nodes, the services that run on them are | 560 | <para>Typically, for Controller nodes, the services that run on them are |
561 | stateless, with few exceptions, where only one instance of a given service | 561 | stateless, with few exceptions, where only one instance of a given service |
@@ -588,7 +588,7 @@ root@node-6:~# systemctl restart vitrage-graph</programlisting> | |||
588 | over a large cluster, since each node has to talk to every other, | 588 | over a large cluster, since each node has to talk to every other, |
589 | essentially creating a mesh configuration. A solution to this problem | 589 | essentially creating a mesh configuration. A solution to this problem |
590 | could be partitioning the cluster into smaller groups, but this has its | 590 | could be partitioning the cluster into smaller groups, but this has its |
591 | limitations and it is generally difficult to manage. </para> | 591 | limitations and it is generally difficult to manage.</para> |
592 | 592 | ||
593 | <para>A better solution is using <literal>pacemaker-remote</literal>, a | 593 | <para>A better solution is using <literal>pacemaker-remote</literal>, a |
594 | feature of pacemaker, which allows for extending the cluster beyond the | 594 | feature of pacemaker, which allows for extending the cluster beyond the |
@@ -788,7 +788,7 @@ ipaddr=10.0.100.155 login=ADMIN passwd=ADMIN op monitor interval="60s"</programl | |||
788 | </section> | 788 | </section> |
789 | </section> | 789 | </section> |
790 | 790 | ||
791 | <section id="ops_resources_agents"> | 791 | <section condition="hidden" id="ops_resources_agents"> |
792 | <title>OpenStack Resource Agents</title> | 792 | <title>OpenStack Resource Agents</title> |
793 | 793 | ||
794 | <para>The OpenStack community has been working for some time on | 794 | <para>The OpenStack community has been working for some time on |
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 8fe5e89..2b89490 100644 --- a/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml +++ b/book-enea-nfv-core-installation-guide/doc/installation_instructions.xml | |||
@@ -43,25 +43,25 @@ | |||
43 | <section id="other-preparations"> | 43 | <section id="other-preparations"> |
44 | <title>Other Preparations</title> | 44 | <title>Other Preparations</title> |
45 | 45 | ||
46 | <para>Reading the following documents aides in familiarizing yourself with | 46 | <para>Reading the following addition and optional documents aides in |
47 | Fuel:</para> | 47 | familiarizing yourself with Fuel:</para> |
48 | 48 | ||
49 | <itemizedlist> | 49 | <itemizedlist> |
50 | <listitem> | 50 | <listitem> |
51 | <para><ulink | 51 | <para><ulink |
52 | url="http://docs.openstack.org/developer/fueldocs/userdocs/fuel-install-guide.html">Fuel | 52 | url="https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-install-guide.html">Fuel |
53 | Installation Guide</ulink></para> | 53 | Installation Guide</ulink></para> |
54 | </listitem> | 54 | </listitem> |
55 | 55 | ||
56 | <listitem> | 56 | <listitem> |
57 | <para><ulink | 57 | <para><ulink |
58 | url="http://docs.openstack.org/developer/fuel-docs/userdocs/fueluser-guide.html">Fuel | 58 | url="https://docs.openstack.org/fuel-docs/latest/userdocs/fuel-user-guide.html">Fuel |
59 | User Guide</ulink></para> | 59 | User Guide</ulink></para> |
60 | </listitem> | 60 | </listitem> |
61 | 61 | ||
62 | <listitem> | 62 | <listitem> |
63 | <para><ulink | 63 | <para><ulink |
64 | url="http://docs.openstack.org/developer/fueldocs/devdocs/develop.html">Fuel | 64 | url="https://docs.openstack.org/fuel-docs/latest/devdocs/develop.html">Fuel |
65 | Developer Guide</ulink></para> | 65 | Developer Guide</ulink></para> |
66 | </listitem> | 66 | </listitem> |
67 | 67 | ||
@@ -70,6 +70,12 @@ | |||
70 | url="http://docs.openstack.org/developer/fueldocs/plugindocs/fuel-plugin-sdk-guide.html">Fuel | 70 | url="http://docs.openstack.org/developer/fueldocs/plugindocs/fuel-plugin-sdk-guide.html">Fuel |
71 | Plugin Developers Guide</ulink></para> | 71 | Plugin Developers Guide</ulink></para> |
72 | </listitem> | 72 | </listitem> |
73 | |||
74 | <listitem> | ||
75 | <para><ulink | ||
76 | url="http://docs.opnfv.org/en/stable-danube/submodules/armband/docs/release/installation/index.html">OPNFV | ||
77 | Fuel Installation Guide</ulink></para> | ||
78 | </listitem> | ||
73 | </itemizedlist> | 79 | </itemizedlist> |
74 | 80 | ||
75 | <para>Prior to installation, a number of deployment specific parameters | 81 | <para>Prior to installation, a number of deployment specific parameters |
@@ -121,8 +127,10 @@ | |||
121 | <section id="hw_req"> | 127 | <section id="hw_req"> |
122 | <title>Hardware Requirements</title> | 128 | <title>Hardware Requirements</title> |
123 | 129 | ||
124 | <para>The following minimum hardware requirements must be met for the | 130 | <para>Enea NFV Core 1.0 has been validated on the hardware configuration |
125 | installation of Enea NFV Core using Fuel, to be successful:</para> | 131 | shown below, which represents the minimum hardware requirements that must |
132 | be met for the installation of Enea NFV Core 1.0 using Fuel, to be | ||
133 | successful:</para> | ||
126 | 134 | ||
127 | <informaltable> | 135 | <informaltable> |
128 | <tgroup cols="2"> | 136 | <tgroup cols="2"> |
@@ -190,7 +198,7 @@ | |||
190 | 198 | ||
191 | <para>This section describes the installation of the Enea NFV Core | 199 | <para>This section describes the installation of the Enea NFV Core |
192 | installation server (Fuel Master) as well as the deployment of the full | 200 | installation server (Fuel Master) as well as the deployment of the full |
193 | ENFV Core reference platform stack across a server cluster.</para> | 201 | Enea NFV Core reference platform stack across a server cluster.</para> |
194 | 202 | ||
195 | <para>It is recommended to install the Fuel Master on a VM using | 203 | <para>It is recommended to install the Fuel Master on a VM using |
196 | virt-manager, with a minimum of 8GB of RAM, 4 CPUs and at least 100GB | 204 | virt-manager, with a minimum of 8GB of RAM, 4 CPUs and at least 100GB |
@@ -288,17 +296,6 @@ | |||
288 | </listitem> | 296 | </listitem> |
289 | 297 | ||
290 | <listitem> | 298 | <listitem> |
291 | <para>In the <literal>Security Setup</literal> menu, restrict the | ||
292 | <literal>ssh</literal> access on the network:</para> | ||
293 | |||
294 | <mediaobject> | ||
295 | <imageobject> | ||
296 | <imagedata contentwidth="600" fileref="images/extra.svg" /> | ||
297 | </imageobject> | ||
298 | </mediaobject> | ||
299 | </listitem> | ||
300 | |||
301 | <listitem> | ||
302 | <para>In the <literal>PXE setup</literal> menu, the default values can | 299 | <para>In the <literal>PXE setup</literal> menu, the default values can |
303 | be left unchanged.</para> | 300 | be left unchanged.</para> |
304 | </listitem> | 301 | </listitem> |
@@ -440,6 +437,10 @@ | |||
440 | <listitem> | 437 | <listitem> |
441 | <para>Zabbix for Fuel</para> | 438 | <para>Zabbix for Fuel</para> |
442 | </listitem> | 439 | </listitem> |
440 | |||
441 | <listitem> | ||
442 | <para>Tacker VNF Manager</para> | ||
443 | </listitem> | ||
443 | </itemizedlist> | 444 | </itemizedlist> |
444 | 445 | ||
445 | <para>Login to the Fuel Master via <literal>ssh</literal> using the | 446 | <para>Login to the Fuel Master via <literal>ssh</literal> using the |
@@ -447,7 +448,8 @@ | |||
447 | additional plugins:</para> | 448 | additional plugins:</para> |
448 | 449 | ||
449 | <programlisting>$ fuel plugins --install /opt/opnfv/vitrage-1.0-1.0.4-1.noarch.rpm | 450 | <programlisting>$ fuel plugins --install /opt/opnfv/vitrage-1.0-1.0.4-1.noarch.rpm |
450 | $ fuel plugins --install zabbix_monitoring-2.5-2.5.3-1.noarch.rpm</programlisting> | 451 | $ fuel plugins --install zabbix_monitoring-2.5-2.5.3-1.noarch.rpm |
452 | $ fuel plugins --install tacker-1.0-1.0.0-1.noarch.rpm</programlisting> | ||
451 | 453 | ||
452 | <para>Expected output: <programlisting>Plugin ....... was successfully installed.</programlisting></para> | 454 | <para>Expected output: <programlisting>Plugin ....... was successfully installed.</programlisting></para> |
453 | </section> | 455 | </section> |
@@ -496,7 +498,8 @@ $ fuel plugins --install zabbix_monitoring-2.5-2.5.3-1.noarch.rpm</programlistin | |||
496 | 498 | ||
497 | <listitem> | 499 | <listitem> |
498 | <para>Select <literal>Neutron with VLAN segmentation</literal> | 500 | <para>Select <literal>Neutron with VLAN segmentation</literal> |
499 | (recommended when enabling DPDK).</para> | 501 | (needed when enabling DPDK). VXLAN is available but not |
502 | supported.</para> | ||
500 | </listitem> | 503 | </listitem> |
501 | 504 | ||
502 | <listitem> | 505 | <listitem> |
@@ -823,7 +826,8 @@ $ fuel plugins --install zabbix_monitoring-2.5-2.5.3-1.noarch.rpm</programlistin | |||
823 | 826 | ||
824 | <para>In the FUEL UI of your Environment, click the | 827 | <para>In the FUEL UI of your Environment, click the |
825 | <literal>Settings</literal> tab and select <literal>OpenStack | 828 | <literal>Settings</literal> tab and select <literal>OpenStack |
826 | Services</literal> on the left side pane:</para> | 829 | Services</literal> on the left side pane, make sure Tacker is NOT enabled |
830 | and save your settings:</para> | ||
827 | 831 | ||
828 | <mediaobject> | 832 | <mediaobject> |
829 | <imageobject> | 833 | <imageobject> |