----- On Aug 7, 2017, at 10:26 PM, kgaillot kgail...@redhat.com wrote:
> > Unmanaging doesn't stop monitoring a resource, it only prevents starting > and stopping of the resource. That lets you see the current status, even > if you're in the middle of maintenance or what not. You can disable > monitoring separately by setting the enabled="false" meta-attribute on > the monitor operation. > Aah. > Standby would normally stop all resources from running on a node (and > thus all monitors as well), but if a resource is unmanaged, standby > won't override that -- it'll prevent the cluster from starting any new > resources on the node, but it won't stop the unmanaged resource (or any > of its monitors). That sounds logical. If a resource is unmanaged, it is not controlled by the cluster. And if it is not controlled by the cluster, it can't be switched off by the cluster if the cluster goes into standby. Bernd Helmholtz Zentrum Muenchen Deutsches Forschungszentrum fuer Gesundheit und Umwelt (GmbH) Ingolstaedter Landstr. 1 85764 Neuherberg www.helmholtz-muenchen.de Aufsichtsratsvorsitzende: MinDir'in Baerbel Brumme-Bothe Geschaeftsfuehrer: Prof. Dr. Guenther Wess, Heinrich Bassler, Dr. Alfons Enhsen Registergericht: Amtsgericht Muenchen HRB 6466 USt-IdNr: DE 129521671 _______________________________________________ Users mailing list: Users@clusterlabs.org http://lists.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