summaryrefslogtreecommitdiffstats
path: root/book-enea-nfv-core-installation-guide/doc/high_availability.xml
diff options
context:
space:
mode:
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.xml205
1 files changed, 129 insertions, 76 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 5854e6c..41d107b 100644
--- a/book-enea-nfv-core-installation-guide/doc/high_availability.xml
+++ b/book-enea-nfv-core-installation-guide/doc/high_availability.xml
@@ -294,33 +294,45 @@
294 <section id="zabbix"> 294 <section id="zabbix">
295 <title>Zabbix Configuration for Push Notifications</title> 295 <title>Zabbix Configuration for Push Notifications</title>
296 296
297 <para>Vitrage supports Zabbix datasource by means of regularly polling 297 <para>Vitrage supports Zabbix datasource by regularly polling the Zabbix
298 the Zabbix agents, which need to be configured in advance. The Vitrage 298 agents, which need to be configured in advance.</para>
299 plugin developed internally by Enea can automatically configure Zabbix 299
300 so that everything works as expected. Polling however, is not fast 300 <para>The Vitrage plugin developed internally by Enea can automatically
301 enough for a telco use-case, so it is necessary to configure push 301 configure Zabbix so that everything works as expected. Polling however,
302 notifications for Zabbix . This requires manual configuration on one of 302 is not fast enough for a telco use-case, so it is necessary to configure
303 the controller nodes, since Zabbix uses a centralized database which 303 push notifications for Zabbix . This requires manual configuration on
304 makes the configuration available on all the other nodes.</para> 304 one of the controller nodes, which will be used by the centralized
305 database making the configuration available on all the other
306 nodes.</para>
305 307
306 <para>The Zabbix configuration dashboard is available at the same IP 308 <para>The Zabbix configuration dashboard is available at the same IP
307 address where OpenStack can be reached, e.g. 309 address where OpenStack can be reached, e.g.
308 <literal>http://10.0.6.42/zabbix</literal>.</para> 310 <literal>http://10.0.6.42/zabbix</literal>.</para>
309 311
310 <mediaobject> 312 <mediaobject>
311 <imageobject> 313 <imageobject role="fop">
312 <imagedata fileref="images/Zabbix_Home.PNG" /> 314 <imagedata contentwidth="600" fileref="images/Zabbix_Home.svg" />
315 </imageobject>
316
317 <imageobject role="html">
318 <imagedata fileref="images/Zabbix_Home.png" />
313 </imageobject> 319 </imageobject>
314 </mediaobject> 320 </mediaobject>
315 321
316 <para>To forward Zabbix events to Vitrage, a new media script needs to 322 <para>To forward Zabbix events to Vitrage, a new media script needs to
317 be created and associated with a user. Follow the steps below as a 323 be created and associated with a Zabbix Admin user.</para>
318 Zabbix Admin user:</para> 324
325 <para><emphasis role="bold">To create the
326 zabbix_vitrage.py</emphasis></para>
319 327
320 <orderedlist> 328 <orderedlist>
321 <listitem> 329 <listitem>
322 <para>Create a new media type [Admininstration Media Types &gt; 330 <para>Create a new media type by selecting the <literal>Media
323 Create Media Type]</para> 331 Types</literal> tab under the <literal>Admininstration</literal>,
332 tab and choosing <literal>Create Media Type</literal>.</para>
333
334 <para>Now fill each parameter field with the values given below,
335 before clicking <literal>add</literal>:</para>
324 336
325 <itemizedlist> 337 <itemizedlist>
326 <listitem> 338 <listitem>
@@ -335,67 +347,105 @@
335 <para>Script name: <filename>zabbix_vitrage.py</filename></para> 347 <para>Script name: <filename>zabbix_vitrage.py</filename></para>
336 </listitem> 348 </listitem>
337 </itemizedlist> 349 </itemizedlist>
350
351 <mediaobject>
352 <imageobject role="fop">
353 <imagedata contentwidth="600"
354 fileref="images/Zabbix_MediaType.svg" />
355 </imageobject>
356
357 <imageobject role="html">
358 <imagedata fileref="images/Zabbix_MediaType.png" />
359 </imageobject>
360 </mediaobject>
338 </listitem> 361 </listitem>
339 362
340 <listitem> 363 <listitem>
341 <para>Modify the Media for the Admin user [Administration 364 <para>Go to the <literal>User</literal> tab by clicking on the
342 Users]</para> 365 <literal>Administration</literal> and next to the field
343 366 <literal>Groups</literal>, click <literal>Add</literal>. In this
344 <para>Click on the Admin user, go to the Media tab and click 367 screen:</para>
345 <literal>Add</literal>.</para>
346 368
347 <itemizedlist> 369 <itemizedlist>
348 <listitem> 370 <listitem>
349 <para>Type: Vitrage Notifications</para> 371 <para>Check the Zabbix Administrators checkbox</para>
350 </listitem> 372 </listitem>
351 373
352 <listitem> 374 <listitem>
353 <para>Send to: 375 <para>Click <literal>Select</literal></para>
354 <literal>rabbit://rabbit_user:rabbit_pass@127.0.0.1:5672/
355 ---</literal> Vitrage message bus url (you need to search for
356 this in <literal>/etc/vitrage/vitrage.conf or
357 /etc/nova/nova.conf transport_url</literal>) It's also vital
358 that the url contains the ending "/".</para>
359 </listitem> 376 </listitem>
360 377
361 <listitem> 378 <listitem>
362 <para>When active: 1-7, 00:00-24:00</para> 379 <para>Click <literal>Update</literal></para>
363 </listitem> 380 </listitem>
381 </itemizedlist>
382
383 <mediaobject>
384 <imageobject role="fop">
385 <imagedata contentwidth="600" fileref="images/Zabbix_User.svg" />
386 </imageobject>
387
388 <imageobject role="html">
389 <imagedata fileref="images/Zabbix_User.png" />
390 </imageobject>
391 </mediaobject>
392 </listitem>
393
394 <listitem>
395 <para>Next select the <literal>Media</literal> tab and and click
396 <literal>Add</literal> to create and modify a new media type. A
397 popup menu will appear for <literal>New Media</literal>, fill each
398 field with the values below:</para>
364 399
400 <itemizedlist>
365 <listitem> 401 <listitem>
366 <para>Use if severity: (all)</para> 402 <para>Type: Vitrage Notifications</para>
367 </listitem> 403 </listitem>
368 404
369 <listitem> 405 <listitem>
370 <para>Status: Enabled</para> 406 <para>Send to: <literal>e.g.
407 rabbit://rabbit_user:rabbit_pass@127.0.0.1:5672/ ---</literal>
408 Vitrage message bus url.</para>
409
410 <para>You need to search for this in
411 <literal>/etc/vitrage/vitrage.conf or in /etc/nova/nova.conf
412 transport_url</literal>. It is vital that the url contains the
413 ending " / ".</para>
371 </listitem> 414 </listitem>
372 415
373 <listitem> 416 <listitem>
374 <para>Click <literal>Update.</literal></para> 417 <para>When active: 1-7, 00:00-24:00</para>
375 </listitem> 418 </listitem>
376 </itemizedlist>
377
378 <para>Go to User tab and next to Groups list click
379 <literal>Add.</literal></para>
380 419
381 <itemizedlist>
382 <listitem> 420 <listitem>
383 <para>Check Zabbix Administrators checkbox</para> 421 <para>Use if severity: (all)</para>
384 </listitem> 422 </listitem>
385 423
386 <listitem> 424 <listitem>
387 <para>Click <literal>Select.</literal></para> 425 <para>Status: Enabled</para>
388 </listitem> 426 </listitem>
389 427
390 <listitem> 428 <listitem>
391 <para>Click <literal>Update.</literal></para> 429 <para>Click <literal>Update</literal></para>
392 </listitem> 430 </listitem>
393 </itemizedlist> 431 </itemizedlist>
432
433 <mediaobject>
434 <imageobject role="fop">
435 <imagedata fileref="images/Zabbix_MediaNotifications.svg" />
436 </imageobject>
437
438 <imageobject role="html">
439 <imagedata fileref="images/Zabbix_MediaNotifications.png" />
440 </imageobject>
441 </mediaobject>
394 </listitem> 442 </listitem>
395 443
396 <listitem> 444 <listitem>
397 <para>Configure Action [Configuration &gt; Actions &gt; Create 445 <para>To configure an action, select <literal>Actions</literal>
398 Action &gt; Action]</para> 446 under the <literal>Configuration</literal> tab. Then, under the
447 <literal>Action</literal> tab, fill in the parameter fields with the
448 values below and click <literal>Add</literal></para>
399 449
400 <itemizedlist> 450 <itemizedlist>
401 <listitem> 451 <listitem>
@@ -419,66 +469,69 @@ expression={TRIGGER.EXPRESSION}
419value={TRIGGER.VALUE} 469value={TRIGGER.VALUE}
420priority={TRIGGER.NSEVERITY} 470priority={TRIGGER.NSEVERITY}
421lastchange={EVENT.DATE} {EVENT.TIME}</programlisting> 471lastchange={EVENT.DATE} {EVENT.TIME}</programlisting>
422 </listitem>
423 472
424 <listitem> 473 <mediaobject>
425 <para>To send events add under the <literal>Conditions</literal> 474 <imageobject role="fop">
426 tab: "Maintenance status not in "maintenance"" and remove 475 <imagedata contentwidth="600"
427 Trigger value = PROBLEM.</para> 476 fileref="images/Zabbix_Action.svg" />
428 </listitem> 477 </imageobject>
429 478
430 <listitem> 479 <imageobject role="html">
431 <para>Click Operations tab:</para> 480 <imagedata fileref="images/Zabbix_Action.png" />
481 </imageobject>
482 </mediaobject>
432 </listitem> 483 </listitem>
484 </itemizedlist>
485 </listitem>
433 486
434 <listitem> 487 <listitem>
435 <para>Under Action operatsion click New</para> 488 <para>To send events, in the <literal>Conditions</literal> tab shown
436 </listitem> 489 above, make sure <literal>Maintenance status not in
490 "maintenance"</literal> added and remove <literal>Trigger value =
491 PROBLEM</literal>, before saving your changes.</para>
492 </listitem>
493
494 <listitem>
495 <para>In the Operations tab, configure the users you wish to send
496 to:</para>
437 497
498 <itemizedlist>
438 <listitem> 499 <listitem>
439 <para>In the Operations details section select</para> 500 <para>In <literal>Operations Details</literal>, set:</para>
440 501
441 <itemizedlist> 502 <itemizedlist>
442 <listitem> 503 <listitem>
443 <para>Send to Users: Admin</para> 504 <para>Operation Type: Send message</para>
505 </listitem>
506
507 <listitem>
508 <para>Send to Users: add <literal>Admin</literal></para>
444 </listitem> 509 </listitem>
445 510
446 <listitem> 511 <listitem>
447 <para>Send only to: Vitrage Notifications</para> 512 <para>Send only to: Vitrage Notifications</para>
448 </listitem> 513 </listitem>
449 </itemizedlist> 514 </itemizedlist>
450 </listitem>
451 515
452 <listitem> 516 <mediaobject>
453 <para>Click Add in the Operarion details section</para> 517 <imageobject role="fop">
518 <imagedata fileref="images/Zabbix_ActionOperations.svg" />
519 </imageobject>
520
521 <imageobject role="html">
522 <imagedata fileref="images/Zabbix_ActionOperations.png" />
523 </imageobject>
524 </mediaobject>
454 </listitem> 525 </listitem>
455 526
456 <listitem> 527 <listitem>
457 <para>Finally outside Operations details section click<literal> 528 <para>Click Add both in the screen and in the return
458 Add</literal></para> 529 screen.</para>
459 </listitem> 530 </listitem>
460 </itemizedlist> 531 </itemizedlist>
461 </listitem> 532 </listitem>
462 </orderedlist> 533 </orderedlist>
463 534
464 <mediaobject>
465 <imageobject>
466 <imagedata fileref="images/Zabbix_MediaType.PNG" />
467 </imageobject>
468 </mediaobject>
469
470 <mediaobject>
471 <imageobject>
472 <imagedata fileref="images/Zabbix_User.PNG" />
473 </imageobject>
474 </mediaobject>
475
476 <mediaobject>
477 <imageobject>
478 <imagedata fileref="images/Zabbix_Action.PNG" />
479 </imageobject>
480 </mediaobject>
481
482 <para>Using these instructions, Zabbix will call the 535 <para>Using these instructions, Zabbix will call the
483 <literal>zabbix_vitrage.py</literal> script, made readily available by 536 <literal>zabbix_vitrage.py</literal> script, made readily available by
484 the Fuel Vitrage Plugin, to pass the arguments described in step 3. The 537 the Fuel Vitrage Plugin, to pass the arguments described in step 3. The