tyler.durden/icinga2
1
0
Fork 0
mirror of https://github.com/Icinga/icinga2.git synced 2025-07-27 07:34:15 +02:00
Code Issues Packages Projects Releases Wiki Activity

Merge pull request #7390 from Icinga/feature/docs-cluster-sync-binaries

Browse Source 
Docs: Syncing binaries with the config sync are not supported
This commit is contained in:
Michael Friedrich 2019-08-02 11:36:04 +02:00 committed by GitHub
commit 8fde836582
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
2 changed files with 21 additions and 0 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
doc/06-distributed-monitoring.md
View File

@ -1179,6 +1179,17 @@ Disadvantages:
* Additional zone and endpoint configuration needed. * Additional zone and endpoint configuration needed.
* Replay log is replicated on reconnect after connection loss. This might increase the data transfer and create an overload on the connection. * Replay log is replicated on reconnect after connection loss. This might increase the data transfer and create an overload on the connection.
> **Note**
>
> This mode only supports **configuration text files** for Icinga. Do not abuse
> this for syncing binaries, this is not supported and may harm your production
> environment. The config sync uses checksums to detect changes, binaries may
> trigger reload loops.
>
> This is a fair warning. If you want to deploy plugin binaries, create
> packages for dependency management and use infrastructure lifecycle tools
> such as Foreman, Puppet, Ansible, etc.
To make sure that all involved nodes accept configuration and/or To make sure that all involved nodes accept configuration and/or
commands, you need to configure the `Zone` and `Endpoint` hierarchy commands, you need to configure the `Zone` and `Endpoint` hierarchy
on all nodes. on all nodes.

10
doc/16-upgrading-icinga-2.md
View File

@ -168,6 +168,16 @@ prior to installing new clients/agents.
Technical details are available in the [technical concepts](19-technical-concepts.md#technical-concepts-cluster-config-sync) chapter. Technical details are available in the [technical concepts](19-technical-concepts.md#technical-concepts-cluster-config-sync) chapter.
Since the config sync change detection now uses checksums, this may fail
with anything else than syncing configuration text files. Syncing binary
files were never supported, but rumors say that some users do so.
Such binaries wrapped into JSON-RPC cluster messages may always cause changes
and trigger reload loops. In order to prevent such harm in production,
use infrastructure tools such as Foreman, Puppet, Ansible, etc. to install
plugins on the masters, satellites and agents.
#### HA-aware Features <a id="upgrading-to-2-11-cluster-ha-aware-features"></a> #### HA-aware Features <a id="upgrading-to-2-11-cluster-ha-aware-features"></a>
v2.11 introduces additional HA functionality similar to the DB IDO feature. v2.11 introduces additional HA functionality similar to the DB IDO feature.