>> Agree. So far I haven't created any ordering constraints because it
>> isn't important to me, YET, the order for starting services. However I
>> have a question... if I don't have any ordering constraints at all, am
>> I still able to activate resources no matter the order?
>
> Sort of, but not
> FYI, commands that "move" a resource do so by adding location
> constraints. The ID of these constraints will start with "cli-". They
> override the normal behavior of the cluster, and stay in effect until
> you explicitly remove them. (With pcs, you can remove them with "pcs
> resource clear".)
or
clusterdataClone? I want to make nodo2 Primary and nodo1 Secondary
but I have no idea how to do this manually (only for testing)
I hope someone can help :(
Thanks in advance
On Mon, Apr 4, 2016 at 4:50 PM, Jason Voorhees wrote:
> I started reading "Pacemaker explained" but as it
I started reading "Pacemaker explained" but as it's so depth I didn't
read that section regarding rules yet. I'll take a look at it and test
it before asking anything again.
Thanks a lot Ken
On Mon, Apr 4, 2016 at 9:26 AM, Ken Gaillot wrote:
> On 04/02/2016 01
Hello guys:
I've been recently reading "Pacemaker - Clusters from scratch" and
working on a CentOS 7 system with pacemaker 1.1.13, corosync-2.3.4 and
drbd84-utils-8.9.5.
The PDF instructs how to create a DRBD resource that seems to be
automatically started due to a symmetric-cluster setup.
Howev