[ClusterLabs] KVM RHEL7 cluster
Andrew Beekhof
andrew at beekhof.net
Tue Aug 4 01:11:01 EDT 2015
So…
your resource definition was:
<clone id="libvirtd-clone">
<primitive class="systemd" id="libvirtd" type="libvirtd">
<instance_attributes id="libvirtd-instance_attributes"/>
<operations>
<op id="libvirtd-monitor-interval-60s" interval="60s" name="monitor"/>
</operations>
<meta_attributes id="libvirtd-meta_attributes">
<nvpair id="libvirtd-meta_attributes-interleave" name="interleave" value="true"/>
</meta_attributes>
</primitive>
<meta_attributes id="libvirtd-clone-meta"/>
</clone>
but needed to be:
<clone id="libvirtd-clone">
<primitive class="systemd" id="libvirtd" type="libvirtd">
<instance_attributes id="libvirtd-instance_attributes"/>
<operations>
<op id="libvirtd-monitor-interval-60s" interval="60s" name="monitor"/>
</operations>
</primitive>
<meta_attributes id="libvirtd-clone-meta">
<nvpair id="libvirtd-meta_attributes-interleave" name="interleave" value="true"/>
</meta_attributes>
</clone>
always set clone options on the clone, not the thing being cloned.
Once I made that change it seemed to behave.
> On 20 May 2015, at 7:00 pm, Ondrej Koch <ondrej.koch at techlib.cz> wrote:
>
> ...and maybe some better logs using crm_report.
>
>
> On 20.5.2015 05:57, Andrew Beekhof wrote:
>>
>>> On 19 May 2015, at 9:59 pm, Ondrej Koch <ondrej.koch at techlib.cz> wrote:
>>>
>>> Hi,
>>> we're trying to build a 6-node KVM virtualization cluster on
>>> CentOS7/RHEL7 using GFS2, CLVM and DLM.
>>> More or less we were following Red Hat documentation and everything
>>> seems to be fine but... We can stop cluster service on a single node and
>>> everything migrates to other nodes. However, as soon as that node
>>> becomes a cluster member again, every VirtualDomain on every cluster
>>> node reboots.
>>>
>>> We tried to kill clvmd as well, cluster noticed that, reinitialized
>>> clvmd and... again every VirtualDomain rebooted.
>>> Our cib is attached.
>>
>> Logs would be required to say much about this
>>
>>>
>>> We suspect something about our dependency and/or colocation rules causes
>>> that. Could you please inspect and give us some directions?
>>>
>>> Thanks,
>>> Ondrej
>>> <cib.xml>_______________________________________________
>>> Users mailing list: Users at 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
>>
>>
>> _______________________________________________
>> Users mailing list: Users at 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
>>
> <lva.tar.bz2>_______________________________________________
> Users mailing list: Users at 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
More information about the Users
mailing list