[ClusterLabs] Early VM resource migration
klecho at gmail.com
Wed Dec 16 11:30:06 EST 2015
On 16.12.2015 17:52, Ken Gaillot wrote:
> On 12/16/2015 02:09 AM, Klechomir wrote:
>> Hi list,
>> I have a cluster with VM resources on a cloned active-active storage.
>> VirtualDomain resource migrates properly during failover (node standby),
>> but tries to migrate back too early, during failback, ignoring the
>> "order" constraint, telling it to start when the cloned storage is up.
>> This causes unnecessary VM restart.
>> Is there any way to make it wait, until its storage resource is up?
> Hi Klecho,
> If you have an order constraint, the cluster will not try to start the
> VM until the storage resource agent returns success for its start. If
> the storage isn't fully up at that point, then the agent is faulty, and
> should be modified to wait until the storage is truly available before
> returning success.
> If you post all your constraints, I can look for anything that might
> affect the behavior.
Thanks for the reply, Ken
Seems to me that that the constraints for a cloned resources act a a bit
Here is my config:
primitive p_AA_Filesystem_CDrive1 ocf:heartbeat:Filesystem \
directory="/volumes/AA_CDrive1" fstype="ocfs2" options="rw,noatime"
primitive VM_VM1 ocf:heartbeat:VirtualDomain \
hypervisor="qemu:///system" migration_transport="tcp" \
meta allow-migrate="true" target-role="Started"
clone AA_Filesystem_CDrive1 p_AA_Filesystem_CDrive1 \
meta interleave="true" resource-stickiness="0"
order VM_VM1_after_AA_Filesystem_CDrive1 inf: AA_Filesystem_CDrive1 VM_VM1
Every time when a node comes back from standby, the VM tries to live
migrate to it long before the filesystem is up.
> Users mailing list: Users at clusterlabs.org
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
More information about the Users