diff options
author | Miruna Paun <Miruna.Paun@enea.com> | 2017-11-20 19:00:03 +0100 |
---|---|---|
committer | Miruna Paun <Miruna.Paun@enea.com> | 2017-11-20 19:00:03 +0100 |
commit | 467269e04948e00ef12eb8c18affa6b0d4dd67e6 (patch) | |
tree | 607d1f0a80221ccd587797f2929f6b4d6b110617 /book-enea-nfv-core-installation-guide/doc/high_availability.xml | |
parent | 6efcc73a2e266a2a467be03073449975dc21b76f (diff) | |
download | doc-enea-nfv-467269e04948e00ef12eb8c18affa6b0d4dd67e6.tar.gz |
COSNOSCR-576 final corrections made to the install. guide and rel info. ver update.
Diffstat (limited to 'book-enea-nfv-core-installation-guide/doc/high_availability.xml')
-rw-r--r-- | book-enea-nfv-core-installation-guide/doc/high_availability.xml | 133 |
1 files changed, 85 insertions, 48 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 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 @@ | |||
2 | <chapter id="high_availability"> | 2 | <chapter id="high_availability"> |
3 | <title>High Availability Guide</title> | 3 | <title>High Availability Guide</title> |
4 | 4 | ||
5 | <para>Enea NFV Core 1.0 has been designed to provide high availability | 5 | <para>Enea NFV Core <xi:include |
6 | characteristics that are needed for developing and deploying telco-grade NFV | 6 | href="../../s_docsrc_common/pardoc-distro.xml" |
7 | solutions on top of our OPNFV based platform. The High Availability subject | 7 | xmlns:xi="http://www.w3.org/2001/XInclude" |
8 | in general is very wide and still an important focus in both opensource | 8 | xpointer="element(EneaNFV_REL_VER/1)" /> has been designed to provide high |
9 | communities and the independent/proprietary solutions market.</para> | 9 | availability characteristics that are needed for developing and deploying |
10 | 10 | telco-grade NFV solutions on top of our OPNFV based platform. The High | |
11 | <para>Enea NFV Core 1.0 aims to initially leverage the efforts in the | 11 | Availability subject in general is very wide and still an important focus in |
12 | upstream OPNFV and OpenStack opensource projects, combining solutions from | 12 | both opensource communities and the independent/proprietary solutions |
13 | both worlds in an effort to provide flexibility and use-case coverage. Enea | 13 | market.</para> |
14 | has long term expertise and proprietary solutions addressing High | 14 | |
15 | Availability for telco applications, which are subject to integration with | 15 | <para>Enea NFV Core <xi:include |
16 | the NFV based solutions.</para> | 16 | href="../../s_docsrc_common/pardoc-distro.xml" |
17 | xmlns:xi="http://www.w3.org/2001/XInclude" | ||
18 | xpointer="element(EneaNFV_REL_VER/1)" /> aims to initially leverage the | ||
19 | efforts in the upstream OPNFV and OpenStack opensource projects, combining | ||
20 | solutions from both worlds in an effort to provide flexibility and use-case | ||
21 | coverage. Enea has long term expertise and proprietary solutions addressing | ||
22 | High Availability for telco applications, which are subject to integration | ||
23 | with the NFV based solutions.</para> | ||
17 | 24 | ||
18 | <section id="levels"> | 25 | <section id="levels"> |
19 | <title>High Availability Levels</title> | 26 | <title>High Availability Levels</title> |
@@ -94,7 +101,10 @@ | |||
94 | communicate with Controllers in order to update the states of the | 101 | communicate with Controllers in order to update the states of the |
95 | virtual and physical resources.</para> | 102 | virtual and physical resources.</para> |
96 | 103 | ||
97 | <para>For this component Enea NFV Core 1.0 makes use of Vitrage, an | 104 | <para>For this component Enea NFV Core <xi:include |
105 | href="../../s_docsrc_common/pardoc-distro.xml" | ||
106 | xmlns:xi="http://www.w3.org/2001/XInclude" | ||
107 | xpointer="element(EneaNFV_REL_VER/1)" /> makes use of Vitrage, an | ||
98 | OpenStack related project used for Root Cause Analysis. The | 108 | OpenStack related project used for Root Cause Analysis. The |
99 | integration into the platform is done with the help of a Fuel Plugin | 109 | integration into the platform is done with the help of a Fuel Plugin |
100 | which has been developed internally by Enea.</para> | 110 | which has been developed internally by Enea.</para> |
@@ -130,13 +140,16 @@ | |||
130 | can be accessed from one of the servers that act as OpenStack | 140 | can be accessed from one of the servers that act as OpenStack |
131 | Controller nodes.</para> | 141 | Controller nodes.</para> |
132 | 142 | ||
133 | <para>In Enea NFV Core 1.0 the Administrator can also access the | 143 | <para>In Enea NFV Core <xi:include |
134 | Zabbix dashboard to perform supplementary configurations. The same | 144 | href="../../s_docsrc_common/pardoc-distro.xml" |
135 | applies for the Vitrage tool, which comes with its own Horizon | 145 | xmlns:xi="http://www.w3.org/2001/XInclude" |
136 | dashboard, enabling the user to visually inspect the faults reported | 146 | xpointer="element(EneaNFV_REL_VER/1)" /> the Administrator can also |
137 | by the monitoring tools through visual representations of the virtual | 147 | access the Zabbix dashboard to perform supplementary configurations. |
138 | and physical resources, the relationships between them and the fault | 148 | The same applies for the Vitrage tool, which comes with its own |
139 | correlation.</para> | 149 | Horizon dashboard, enabling the user to visually inspect the faults |
150 | reported by the monitoring tools through visual representations of the | ||
151 | virtual and physical resources, the relationships between them and the | ||
152 | fault correlation.</para> | ||
140 | 153 | ||
141 | <para>For Vitrage, users will usually want to configure additional | 154 | <para>For Vitrage, users will usually want to configure additional |
142 | use-cases and describe relationships between components via template | 155 | use-cases and describe relationships between components via template |
@@ -152,10 +165,13 @@ | |||
152 | the VNFs. The role of the Consumer thus falls to that of a VNF Manager | 165 | the VNFs. The role of the Consumer thus falls to that of a VNF Manager |
153 | and Orchestrator.</para> | 166 | and Orchestrator.</para> |
154 | 167 | ||
155 | <para>Enea NFV Core 1.0 provides VNF management capabilities using | 168 | <para>Enea NFV Core <xi:include |
156 | Tacker, which is an OpenStack project that implements a generic VNF | 169 | href="../../s_docsrc_common/pardoc-distro.xml" |
157 | Manager and Orchestrator, according to the ETSI MANO Architectural | 170 | xmlns:xi="http://www.w3.org/2001/XInclude" |
158 | Framework.</para> | 171 | xpointer="element(EneaNFV_REL_VER/1)" /> provides VNF management |
172 | capabilities using Tacker, which is an OpenStack project that | ||
173 | implements a generic VNF Manager and Orchestrator, according to the | ||
174 | ETSI MANO Architectural Framework.</para> | ||
159 | </listitem> | 175 | </listitem> |
160 | </itemizedlist> | 176 | </itemizedlist> |
161 | 177 | ||
@@ -196,7 +212,11 @@ | |||
196 | </imageobject> | 212 | </imageobject> |
197 | </mediaobject> | 213 | </mediaobject> |
198 | 214 | ||
199 | <para>Enea NFV Core 1.0 uses the same approach described above:</para> | 215 | <para>Enea NFV Core <xi:include |
216 | href="../../s_docsrc_common/pardoc-distro.xml" | ||
217 | xmlns:xi="http://www.w3.org/2001/XInclude" | ||
218 | xpointer="element(EneaNFV_REL_VER/1)" /> uses the same approach | ||
219 | described above:</para> | ||
200 | 220 | ||
201 | <orderedlist> | 221 | <orderedlist> |
202 | <listitem> | 222 | <listitem> |
@@ -287,8 +307,11 @@ | |||
287 | </orderedlist> | 307 | </orderedlist> |
288 | 308 | ||
289 | <note condition="hidden"> | 309 | <note condition="hidden"> |
290 | <para>The ENEA NFV Core 1.0 Pre-Release fully covers the required | 310 | <para>The ENEA NFV Core <xi:include |
291 | Doctor functionality only for the Vitrage and Zabbix | 311 | href="../../s_docsrc_common/pardoc-distro.xml" |
312 | xmlns:xi="http://www.w3.org/2001/XInclude" | ||
313 | xpointer="element(EneaNFV_REL_VER/1)" /> Pre-Release fully covers the | ||
314 | required Doctor functionality only for the Vitrage and Zabbix | ||
292 | components.</para> | 315 | components.</para> |
293 | </note> | 316 | </note> |
294 | </section> | 317 | </section> |
@@ -309,7 +332,9 @@ | |||
309 | 332 | ||
310 | <para>The Zabbix configuration dashboard is available at the same IP | 333 | <para>The Zabbix configuration dashboard is available at the same IP |
311 | address where OpenStack can be reached, e.g. | 334 | address where OpenStack can be reached, e.g. |
312 | <literal>http://10.0.101.42/zabbix</literal>.</para> | 335 | <literal>http://10.0.101.42/zabbix</literal>. Default username and |
336 | password are <literal>admin</literal> and <literal>zabbix</literal> | ||
337 | respectively.</para> | ||
313 | 338 | ||
314 | <mediaobject> | 339 | <mediaobject> |
315 | <imageobject> | 340 | <imageobject> |
@@ -422,7 +447,10 @@ | |||
422 | </listitem> | 447 | </listitem> |
423 | 448 | ||
424 | <listitem> | 449 | <listitem> |
425 | <para>Next, select the <literal>Media</literal> tab and click | 450 | <para>Reselect the <literal>admin</literal> alias to enter the |
451 | <literal>Configuration of Users</literal> screen once again.</para> | ||
452 | |||
453 | <para>Select the <literal>Media</literal> tab and click | ||
426 | <literal>Add</literal> to create and modify a new media type. A | 454 | <literal>Add</literal> to create and modify a new media type. A |
427 | popup menu will appear for <literal>New Media</literal>. Fill each | 455 | popup menu will appear for <literal>New Media</literal>. Fill each |
428 | field with the values below:</para> | 456 | field with the values below:</para> |
@@ -436,10 +464,10 @@ | |||
436 | <para>Send to: <literal>e.g. | 464 | <para>Send to: <literal>e.g. |
437 | rabbit://nova:Q1Vt9iocA8OpXKOPoUYOLKie@192.168.0.4:5673/</literal></para> | 465 | rabbit://nova:Q1Vt9iocA8OpXKOPoUYOLKie@192.168.0.4:5673/</literal></para> |
438 | 466 | ||
439 | <para>You need to search for this in | 467 | <para>This url can be found in either |
440 | <literal>/etc/vitrage/vitrage.conf or in /etc/nova/nova.conf | 468 | <literal>/etc/vitrage/vitrage.conf or in |
441 | transport_url</literal>. It is vital that the url contains the | 469 | /etc/nova/nova.conf</literal>. Only one url is needed and it is |
442 | ending " / ".</para> | 470 | vital that the url contains the ending " / ".</para> |
443 | </listitem> | 471 | </listitem> |
444 | 472 | ||
445 | <listitem> | 473 | <listitem> |
@@ -473,7 +501,7 @@ | |||
473 | <literal>Configuration</literal> tab select | 501 | <literal>Configuration</literal> tab select |
474 | <literal>Actions</literal>. Then, under the | 502 | <literal>Actions</literal>. Then, under the |
475 | <literal>Action</literal> tab, fill in the parameter fields with the | 503 | <literal>Action</literal> tab, fill in the parameter fields with the |
476 | values below and click <literal>Add</literal></para> | 504 | values below:</para> |
477 | 505 | ||
478 | <itemizedlist> | 506 | <itemizedlist> |
479 | <listitem> | 507 | <listitem> |
@@ -538,7 +566,7 @@ lastchange={EVENT.DATE} {EVENT.TIME}</programlisting> | |||
538 | </listitem> | 566 | </listitem> |
539 | 567 | ||
540 | <listitem> | 568 | <listitem> |
541 | <para>Send to Users: add <literal>Admin</literal></para> | 569 | <para>Send to Users: add <literal>admin</literal></para> |
542 | </listitem> | 570 | </listitem> |
543 | 571 | ||
544 | <listitem> | 572 | <listitem> |
@@ -578,7 +606,7 @@ lastchange={EVENT.DATE} {EVENT.TIME}</programlisting> | |||
578 | 606 | ||
579 | <para>In order to make use of these features, Vitrage supports | 607 | <para>In order to make use of these features, Vitrage supports |
580 | additional configurations via <literal>yaml</literal> templates that | 608 | additional configurations via <literal>yaml</literal> templates that |
581 | must be placed in <literal>/etc/vitrage/templates</literal> on the nodes | 609 | must be placed in <literal>/etc/vitrage/templates</literal> on the node |
582 | that have the Vitrage role.</para> | 610 | that have the Vitrage role.</para> |
583 | 611 | ||
584 | <mediaobject> | 612 | <mediaobject> |
@@ -667,8 +695,11 @@ root@node-6:~# systemctl restart vitrage-graph</programlisting> | |||
667 | <section id="vitrage_custom"> | 695 | <section id="vitrage_custom"> |
668 | <title>Vitrage Customizations</title> | 696 | <title>Vitrage Customizations</title> |
669 | 697 | ||
670 | <para>Enea NFV Core 1.0 has added custom features for Vitrage which | 698 | <para>Enea NFV Core <xi:include |
671 | allow two kinds of actions:</para> | 699 | href="../../s_docsrc_common/pardoc-distro.xml" |
700 | xmlns:xi="http://www.w3.org/2001/XInclude" | ||
701 | xpointer="element(EneaNFV_REL_VER/1)" /> has added custom features for | ||
702 | Vitrage which allow two kinds of actions:</para> | ||
672 | 703 | ||
673 | <orderedlist> | 704 | <orderedlist> |
674 | <listitem> | 705 | <listitem> |
@@ -866,12 +897,15 @@ RemoteOnline: [ node-4.domain.tld node-5.domain.tld ]</programlisting> | |||
866 | <section id="pm_fencing"> | 897 | <section id="pm_fencing"> |
867 | <title>Pacemaker Fencing</title> | 898 | <title>Pacemaker Fencing</title> |
868 | 899 | ||
869 | <para>ENEA NFV Core 1.0 makes use of the fencing capabilities of | 900 | <para>ENEA NFV Core <xi:include |
870 | Pacemaker to isolate faulty nodes and trigger recovery actions by means | 901 | href="../../s_docsrc_common/pardoc-distro.xml" |
871 | of power cycling the failed nodes. Fencing is configured by creating | 902 | xmlns:xi="http://www.w3.org/2001/XInclude" |
872 | <literal>STONITH</literal> type resources for each of the servers in the | 903 | xpointer="element(EneaNFV_REL_VER/1)" /> makes use of the fencing |
873 | cluster, both Controller nodes and Compute nodes. The | 904 | capabilities of Pacemaker to isolate faulty nodes and trigger recovery |
874 | <literal>STONITH</literal> adapter for fencing the nodes is | 905 | actions by means of power cycling the failed nodes. Fencing is |
906 | configured by creating <literal>STONITH</literal> type resources for | ||
907 | each of the servers in the cluster, both Controller nodes and Compute | ||
908 | nodes. The <literal>STONITH</literal> adapter for fencing the nodes is | ||
875 | <literal>fence_ipmilan</literal>, which makes use of the IPMI | 909 | <literal>fence_ipmilan</literal>, which makes use of the IPMI |
876 | capabilities of the ThunderX servers.</para> | 910 | capabilities of the ThunderX servers.</para> |
877 | 911 | ||
@@ -965,9 +999,12 @@ ipaddr=10.0.100.155 login=ADMIN passwd=ADMIN op monitor interval="60s"</programl | |||
965 | resources capable of identifying failures in compute nodes and can perform | 999 | resources capable of identifying failures in compute nodes and can perform |
966 | automatic evacuation of the instances affected by these failures.</para> | 1000 | automatic evacuation of the instances affected by these failures.</para> |
967 | 1001 | ||
968 | <para>ENEA NFV Core 1.0 aims to validate and integrate this work and to | 1002 | <para>ENEA NFV Core <xi:include |
969 | make this feature available in the platform aimed as an alternative to the | 1003 | href="../../s_docsrc_common/pardoc-distro.xml" |
970 | Doctor framework, where simple, autonomous recovery of running instances | 1004 | xmlns:xi="http://www.w3.org/2001/XInclude" |
971 | is desired.</para> | 1005 | xpointer="element(EneaNFV_REL_VER/1)" /> aims to validate and integrate |
1006 | this work and to make this feature available in the platform aimed as an | ||
1007 | alternative to the Doctor framework, where simple, autonomous recovery of | ||
1008 | running instances is desired.</para> | ||
972 | </section> | 1009 | </section> |
973 | </chapter> \ No newline at end of file | 1010 | </chapter> \ No newline at end of file |