Good morning Michael,

>>> On 05.03.2015 at 20:20, Michael Friedrich
<[email protected]> wrote:
> Am Donnerstag, 5. März 2015 schrieb Kai Nothdurft :
>>  >>> On 05.03.2015 at 16:44, Michael Friedrich
<[email protected] <javascript:;>> wrote:
>> >
>> > I'm curious what makes you think that such an option
"ohcp_command"
>> > exists in Icinga 2.
>> >
>> > Michael
>>
>> Doesn't Icinga 2 inherit the option "ohcp_command" from Icinga,
which
>> inherited it from Nagios? Please don't tell me that this feature
was
>> removed.
> 
> 
> It's not implemented. There was no use case for it.

I'm curious what makes you think that there is no use case for anybody.
;)

>>  I need it. How should I otherwise transfer the states from ship
>> to shore?
> 
> Cluster feature with integrated replication. Check the docs. 

I did check the docs. Again, I am talking about remote Icinga2-hosts
on
seagoing vessels, which have only low-bandwith/high latency- Internet
once in a while via satellite with a very expensive data-plan. There
is no reliable Internet-connection at all, but at least we have a
robust
file-transfer-solution for maritime business.

Cluster Requirements (from the docs) not met:

<quote>
Cluster Requirements
- communication between zones happens bi-directional which means that a

DMZ-located node can still reach the master node, or vice versa 
- Update firewall rules and ACLs

Distributed Zones
That scenario fits if your instances are spread over the globe and they

all report to a master instance. Their network connection only works 
towards the master master (or the master is able to connect, depending

on firewall policies). 
</quote>

>There's also a mention for the differences between 1.x and 2.x.

Yep, a.o. it says:

<quote>
Distributed Monitoring

Icinga 1.x uses the native "obsess over host/service" method which 
requires the NSCA addon passing the slave's check results passively
onto 
the master's external command pipe. While this method may be used for 
check load distribution, it does not provide any configuration 
distribution out-of-the-box. Furthermore comments, downtimes, and other

stateful runtime data is not synced between the master and slave nodes.

There are addons available solving the check and configuration 
distribution problems Icinga 1.x distributed monitoring currently 
suffers from. 

Icinga 2 implements a new built-in distributed monitoring architecture,

including config and check distribution, IPv4/IPv6 support, SSL 
certificates and zone support for DMZ. High Availability and load 
balancing are also part of the Icinga 2 Cluster setup. 
</unquote>

I see propaganda for the (good) built-in distributed monitoring 
architecture but NO word, that the old way does NOT work anymore. 

>> In my test-setup now the config is accepted, but it looks like my
>> "ohcp_command"-script is never executed.
> 
> Just because that configuration is nonsense, and not documented
_anywhere_
> in the icinga2 docs.

Why so rude? I think you are right, that the configuration does not 
work. But "nonsense"? That something is not documented means that it is

not implemented? You say the documentation always reflects the latest 
state? I could argue that it is nonsense, that Icinga2 takes the
options 
from my conf-file without complaining. When it takes options w/o errors

or warnings one can  assume, that the options are valid and that they
have an 
effect. Btw, the documentaion for Icinga2 at docs.icinga.org lacks a
search
engine, which forced me to use Google, which in turn often displays
results
for Icinga even when searched for Icinga2.

Again, I think you don't know anything about maritime business. I only

need status updates every half an hour or so. Now that I know, that 
ocsp/ohcp is not implemented in Icinga2 (thanks for clarifying), I'll 
write a cron-job which gets the data via livestatus and feeds that to 
our file-transfer-routine. But I have to read the docs for klivestatus
first...

Thanks again for putting me on the right track and
best regards
Kai
_______________________________________________
icinga-users mailing list
[email protected]
https://lists.icinga.org/mailman/listinfo/icinga-users

Reply via email to