Additional information regarding cluster files

This commit is contained in:
Bernd Erk 2013-10-16 17:17:32 +02:00
parent 8686305848
commit 0ab76e7843
2 changed files with 6 additions and 6 deletions

View File

@ -246,8 +246,6 @@ Objects can inherit attributes from other objects.
Example:
template Host "default-host" {
check_interval = 30,
macros["color"] = "red"
}

View File

@ -42,7 +42,7 @@ Then you can start CA creation using
After that you can find your ca.crt and ca.key file in the keys directory and can create a server certificate for every node in the cluster using
./build-key-server <node-name>
./build-key <node-name>
Please don't use a passphrase during the certificate creation process.
@ -66,6 +66,7 @@ The ClusterListener needs to be configured on every node in the cluster with the
-------------------------|------------------------------------
ca_path | path to ca.crt file
cert_path | path to server certificate
key_path | path to server key
bind_port | port for incoming and outgoing conns
peers | array of all reachable nodes
------------------------- ------------------------------------
@ -100,7 +101,7 @@ In addition to the configured port and hostname every endpoint can have specific
host | hostname
port | port
accept_config | defines all nodes allowed to send configs
config_files | defines all files to be send to other nodes
config_files | defines all files to be send to that node - MUST BE ABSOLUTE PATH
------------------------- ------------------------------------
A sample config part can look like this:
@ -111,10 +112,11 @@ A sample config part can look like this:
object Endpoint "icinga-node-1" {
host = "icinga-node-1.localdomain",
port = 8888
port = 8888,
config_files = ["/etc/icinga2/conf.d/*.conf"]
}
If you update the configs on the configured file sender, it will force a restart on all receiving nodes after validating the new config.
## Dependencies