Document that modified attributes require accept_config for cluster/clients

fixes #10368
This commit is contained in:
Michael Friedrich 2015-10-22 16:24:42 +02:00
parent f31837a6ba
commit b2fb4546df
2 changed files with 12 additions and 1 deletions

View File

@ -266,6 +266,9 @@ the defined parent zone `config-ha-master`.
## <a id="cluster-zone-config-sync"></a> Zone Configuration Synchronisation ## <a id="cluster-zone-config-sync"></a> Zone Configuration Synchronisation
In case you are using the Icinga 2 API for creating, modifying and deleting objects
at runtime, please continue over [here](9-icinga2-api.md#icinga2-api-config-objects-cluster-sync).
By default all objects for specific zones should be organized in By default all objects for specific zones should be organized in
/etc/icinga2/zones.d/<zonename> /etc/icinga2/zones.d/<zonename>

View File

@ -587,8 +587,16 @@ will not be joined.
Newly created or updated objects can be synced throughout your Newly created or updated objects can be synced throughout your
Icinga 2 cluster. Set the `zone` attribute to the zone this object Icinga 2 cluster. Set the `zone` attribute to the zone this object
belongs to and let the API and cluster handle the rest. belongs to and let the API and cluster handle the rest.
Objects without zone attribute are only synced in the same (HA) zone.
If you add a new cluster instance, or boot an instance beeing offline > **Note**
>
> Cluster nodes must accept configuration for creating, modifying
> and deleting objects. Ensure that `accept_config` is set to `true`
> in the [ApiListener](6-object-types.md#objecttype-apilistener) object
> on each node.
If you add a new cluster instance, or boot an instance which was offline
for a while, Icinga 2 takes care of the initial object sync for all for a while, Icinga 2 takes care of the initial object sync for all
objects created by the API. objects created by the API.