Hi, Thank you for your response, I have some follow-up questions. >> >> Now what I am looking for is a way to completely delete/remove >> openvzve_itv without affecting the other resources. > > is-managed-default=false and/or resource-stickiness=INFINITY > When trying to use the first "method", setting is-managed-default to false, how would I go on about that? I think I'd have to "crm configure property is-managed-default=false" (How would I list all set properties?) After that I should be able to delete the stuff from the configuration without it causing pacemaker to act upon it, right? I noticed that only deleting the group entry of openvzve_itv causes the cluster to want to move all resources to the other node. (Even after setting said property) I'm curious as to why the cluster would decide to do this in the first place, how he decides that this would be a good idea.
regards, Julian D. Seifert --
signature.asc
Description: OpenPGP digital signature
_______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
