Hello,
Absolutely no logs from openais found even in debug mode which looks
strange (my configuration bellow).
Some interesting logs from Xend:
[2009-09-24 13:49:47 3710] DEBUG (XendDomainInfo:467)
XendDomainInfo.shutdown(poweroff)
[2009-09-24 13:49:47 3710] DEBUG (XendDomainInfo:1092)
XendDomainInfo.handleShutdownWatch
[2009-09-24 13:49:47 3710] INFO (XendDomainInfo:485) HVM save:remote
shutdown dom 36!
[2009-09-24 13:49:47 3710] INFO (XendDomainInfo:1283) Domain has
shutdown: name=xps-102 id=36 reason=poweroff.
It seems that Pacemaker request for resource poweroff instead of
migration as allowed in resource configuration.
Saying that, it seems that allow_migrate syntax has changed: in GUI the
only choice I have is allow_migrate as instance attribute.
And after tests, I saw it must be "allow-migrate" as meta attribute for
xen live migration to work.
That may explain what happens.
So, is my configuration suitable to open a bug, or have I made a mistake?
Regards,
JB
===============================================
Openais logging configuration:
logging {
debug: on
timestamp: on
to_file: yes
logfile: /home/openais.log
}
Xen resource config:
primitive xps-102 ocf:heartbeat:Xen \
params xmfile="/cluster/xen/xps-102.cfg" allow_migrate="true" \
op monitor interval="10s" \
meta allow-migrate="true" resource-stickiness="0"
Dejan Muhamedagic a écrit :
> Hi,
>
> On Wed, Sep 23, 2009 at 11:07:27PM +0200, Jean Baptiste Favre wrote:
>> Hello,
>> I'm still building a xen cluster managed by pacemaker/openais.
>> Things are quite close to be OK I think, execpt when I want to put a
>> node in standby mode:
>> When it happens, all XEN VM are shut down and restarted on the other node.
>> When I ask for ressource migration, XEN Live Migration does the job so
>> that no downtime occurs.
>>
>> Is there any way to "slow down" standby mode so that XEN VM can migrate
>> gracefully ?
>
> There are no special options for standby, but I think that it
> should do migrate instead of stop/start if migrate is allowed.
> Did you see anything suspicious in the logs? If not, then you
> should open a bugzilla.
>
> Thanks,
>
> Dejan
>
>> Bellow you can find my cluster configuration, if it can help.
>>
>> Thanks,
>> JB
>>
>> =======================================
>> node remus attributes standby="false"
>> node romulus attributes standby="false"
>> primitive Cluster-ocfs-DRBD ocf:linbit:drbd \
>> params drbd_resource="cluster-ocfs" \
>> operations $id="Cluster-ocfs-DRBD-operations" \
>> op monitor interval="20" role="Master" timeout="20" \
>> op monitor interval="30" role="Slave" timeout="20"
>> primitive Cluster-ocfs-FS ocf:heartbeat:Filesystem \
>> params device="/dev/drbd/by-res/cluster-ocfs" \
>> directory="/cluster" fstype="ocfs2"
>> primitive xps-101-DRBD ocf:linbit:drbd \
>> params drbd_resource="xps-101" \
>> operations $id="xps-101-DRBD-operations" \
>> op monitor interval="20" role="Master" timeout="20" \
>> op monitor interval="30" role="Slave" timeout="20"
>> primitive xps-101 ocf:heartbeat:Xen \
>> params xmfile="/cluster/xen/xps-101.cfg" allow_migrate="true" \
>> op monitor interval="10s" \
>> meta allow-migrate="true"
>> ms Cluster-ocfs-MS Cluster-ocfs-DRBD \
>> meta resource-stickines="100" master-max="2" notify="true" \
>> interleave="true"
>> ms xps-101-MS xps-101-DRBD \
>> meta resource-stickines="100" master-max="2" notify="true" \
>> interleave="true"
>> clone Cluster-ocfs-FSCL Cluster-ocfs-FS \
>> meta interleave="true" ordered="true"
>> colocation xps-101-Xen-DRBD inf: xps-101 xps-101-MS:Master
>> order Cluster-ocfs-AfterDRBD inf: Cluster-ocfs-MS:promote \
>> Cluster-ocfs-FSCL:start
>> order xps-101-AfterDRBD inf: xps-101-MS:promote xps-101:start
>> property $id="cib-bootstrap-options" \
>> dc-version="1.0.4-2ec1d189f9c23093bf9239a980534b661baf782d" \
>> cluster-infrastructure="openais" \
>> expected-quorum-votes="2" \
>> last-lrm-refresh="1253739607" \
>> node-health-red="0" \
>> stonith-enabled="false" \
>> no-quorum-policy="ignore"
>> _______________________________________________
>> Linux-HA mailing list
>> [email protected]
>> http://lists.linux-ha.org/mailman/listinfo/linux-ha
>> See also: http://linux-ha.org/ReportingProblems
_______________________________________________
Linux-HA mailing list
[email protected]
http://lists.linux-ha.org/mailman/listinfo/linux-ha
See also: http://linux-ha.org/ReportingProblems
