Sehr geehrte Damen und Herren,
in der Zeit vom 02.11.2018 bis einschließlich 18.11.2018 befinde ich mich nicht
im Büro.
Beachten Sie bitte, dass Ihre E-Mail nicht automatisch weitergeleitet wird.
In dringenden Fällen wenden Sie sich bitte an unsere Hotline, 0203-378530, oder
an Herrn Hesselmann (hesselm...@opm-computer.de).
Mit freundlichen Grüßen
Ronny Bär
OPM IT Service GmbH
Send icinga-users mailing list submissions to
icinga-users@lists.icinga.org
To subscribe or unsubscribe via the World Wide Web, visit
https://lists.icinga.org/mailman/listinfo/icinga-users
or, via email, send a message with subject or body 'help' to
icinga-users-requ...@lists.icinga.org
You can reach the person managing the list at
icinga-users-ow...@lists.icinga.org
When replying, please edit your Subject line so it is more specific
than "Re: Contents of icinga-users digest..."
Today's Topics:
1. Single-click downtime for multiple hosts (and all associated
services) (Antony Stone)
----------------------------------------------------------------------
Message: 1
Date: Fri, 1 Mar 2019 21:20:39 +0100
From: Antony Stone <antony.st...@icinga.open.source.it>
To: "Icinga User's Corner" <icinga-users@lists.icinga.org>
Subject: [icinga-users] Single-click downtime for multiple hosts (and
all associated services)
Message-ID: <201903012120.39393.antony.st...@icinga.open.source.it>
Content-Type: text/plain; charset="us-ascii"
Hi.
Background:
I have a high-availability setup which consists of three machines running
corosync / pacemaker managing a floating IP address, and a second group of
three machines similarly running another floating IP address.
Either of those addresses can be used to access various services running on
the entire "cluster".
In Icinga(2.10.3) I've created host entries for:
- each of the six "real" servers
- each of the two floating IPs at which services can be accessed
- one "cluster" entity which represents either of the floating addresses being
available
Requirement:
>From time to time I run updates to the software on one or more of the real
servers, and of course this results in short-term unavailability of the
services they are running, during the upgrade.
If I'm updating just one machine, I can put it into Downtime in Icingaweb2
(along with all its services) and avoid getting alerts while the services (or
indeed the host, if a reboot is involved) are unavailable.
I would like to be able to set Downtime on one of the floating IP "Hosts" and
have it take effect on all three of the real servers which provide this single
address, or to set Downtime on the single "cluster" Host, and have this take
effect on all six servers together.
Can anyone think of a way to do this?
I've tried using Group membership, and custom Host variables, but I can't find
any way to have a setting I change on the "higher level" host ripple down to
the component hosts which are members of it.
Any ideas gratefully received :)
Antony.
--
"640 kilobytes (of RAM) should be enough for anybody."
- Bill Gates
Please reply to the list;
please *don't* CC me.
------------------------------
Subject: Digest Footer
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
------------------------------
End of icinga-users Digest, Vol 63, Issue 1
*******************************************
_______________________________________________
icinga-users mailing list
icinga-users@lists.icinga.org
https://lists.icinga.org/mailman/listinfo/icinga-users
