On 03/23/2016 06:41 AM, Ferenc Wágner wrote: > Ken Gaillot <kgail...@redhat.com> writes: > >> There is a fence parameter pcmk_host_check that specifies how pacemaker >> determines which fence devices can fence which nodes. The default is >> dynamic-list, which means to run the fence agent's list command to get >> the nodes. [...] >> >> You can specify pcmk_host_list or pcmk_host_map to use a static target >> list for the device. > > I meant to research this, but now that you brought it up: does the > default of pcmk_host_check automatically change to static-list if > pcmk_host_list is defined?
If pcmk_host_check is specified, it is used; otherwise, if pcmk_host_list and/or pcmk_host_map are specified, pcmk_host_check=static-list; otherwise, if the device supports the list or status commands, pcmk_host_check=dynamic-list; otherwise, pcmk_host_check=none. > Does pcmk_host_map override pcmk_host_list? Does it play together with > pcmk_host_check=dynamic-list? If pcmk_host_check=none, all devices can fence all nodes (i.e. if you explicitly specify none, pcmk_host_list/pcmk_host_map are ignored); otherwise, if pcmk_host_check=static-list, the values of pcmk_host_list and/or pcmk_host_map are allowed targets (i.e. they combine if both are specified, though that would be poor practice as it's confusing to read); otherwise, the device is queried (i.e. static and dynamic never combine). _______________________________________________ Users mailing list: Users@clusterlabs.org http://clusterlabs.org/mailman/listinfo/users Project Home: http://www.clusterlabs.org Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf Bugs: http://bugs.clusterlabs.org