On Wed, Jun 15, 2011 at 11:57:38PM +0200, Pawel Warowny wrote:
> Dnia Wed, 15 Jun 2011 18:14:19 +0200
> Dejan Muhamedagic napisał(a):
>
> Hi
>
> Thank you for reply.
>
> > That's really odd. Is it that at this time vr_debian_squeeze
> > runs on node1?
>
> No, vr_debian_squeeze doesn't run on n
Dnia Wed, 15 Jun 2011 18:14:19 +0200
Dejan Muhamedagic napisał(a):
Hi
Thank you for reply.
> That's really odd. Is it that at this time vr_debian_squeeze
> runs on node1?
No, vr_debian_squeeze doesn't run on node1, it starts on node2 as the
first resource despite of order and colocation constr
Hi,
On Wed, Jun 15, 2011 at 10:26:36AM +0200, Pawel Warowny wrote:
> Hi
>
> I have problem with starting order on node after manual migration.
> My cluster consists of two nodes that provides bunch of kvm virtualized
> hosts.
>
> When I start node, first starting drbd, dlm (and the like) next li
Dnia Wed, 15 Jun 2011 10:26:36 +0200
Pawel Warowny napisał(a):
Hi
Sorry, I forgot to change original node name in my example, so:
> location vr_debian_squeeze_loc vr_debian_squeeze 100: lolek
in my previous post should be:
location vr_debian_squeeze_loc vr_debian_squeeze 100: node1
Best regard
Hi
I have problem with starting order on node after manual migration.
My cluster consists of two nodes that provides bunch of kvm virtualized
hosts.
When I start node, first starting drbd, dlm (and the like) next libvirt
and the last hosts provided by VirtualDomain resource.
When I stop node, th
