[Linux-cluster] ordered/ restricted and clusvcadm -F

[Edson Marquezani Filho]

On Mon, Aug 24, 2009 at 12:37, Alain.Moulle<Alain.Moulle at bull.net> wrote:
> Hi,
> given a failover domain like this one :
> <failoverdomain name="FailoverDomain-1" ordered="???" restricted="???">
>          <failoverdomainnode name="node1" priority="1"/>
>          <failoverdomainnode name="node2" priority="2"/>
>          <failoverdomainnode name="node3" priority="3"/>
> </failoverdomain>
> and a service serv1 configured on this failoverdomain.
>
> I would like that the command:
>  clusvcadm -e serv1
> executed on whatever node of the three nodes starts the serv1 on the
> prefered node  node1 (priority1)

I wanted that two, but it seems like there's no way do that exactly
like this. See below.

> And  in the case serv1 is started on node2 (or node3) (after a failover
> for example) and that node1 transitions online , I don't want an
> automatic migration of serv1 onto node1.

This can be done with nofailback="1" on <failoverdomain> tag. I want
things working like this too, I use that option, and it works.

> My understanding was to set ordered=1 and restricted=0  but
> it seems that clusvcadm -e serv1 starts it on the node where clusvcadm is
> executed, even if it is node the "priority 1" node (node1).

Yes, acording to this[1], clusvcadm will always start the service on
the node where the command was issued. The only way to make it to run
on a specific node is setting it with -m option. ( FAQ says -n, but as
far as I have seen, it's -m that specifies the cluster member, and
actualy, there is no -n option at all.)

> Option -F of clusvcadm seemed to give a response to my question, but
> it is announced as "deprecated" ...

That option seemed not work to me too.

> Thanks for your response.

I'm a very begginer in RHCS, but I have been playing around with
rgmanager and that's what I could figure out during these last days.

I hope I could help you.

[1] http://sources.redhat.com/cluster/wiki/FAQ/RGManager#rgm_svcstart