[Pacemaker] How to set resource order to satisfy this situation

[Mia Lueng]

bingo,  I upgrade to sles11 hae sp3 and it provides the beiaviour I expect.

hatest01:~ # rpm -q pacemaker
pacemaker-1.1.9-0.19.102



2013/8/7 Andrew Beekhof <andrew at beekhof.net>

>
> On 06/08/2013, at 1:06 PM, Mia Lueng <xiaozunvlg at gmail.com> wrote:
>
> > colocation ftp_www_balance -inf: apache vsftp
> > order apache_mount inf: nfs_client_clone apache
> > order nfs_cs_order 0: nfs_server nfs_client_clone
> > order vsftp_mount inf: nfs_client_clone vsftp
> >
> >
> > nfsserver---->nfsclient----->www
> >         \
> >           \------->nfsclient----->ftp
> >
> > I want when nfsserver migrate from hostA to hostB, nfsclient/www/ftp do
> not stop/start.
> >
> > But  When I migrate nfsserver , nfsclient do not migrate, but www/ftp do
> migrate with nfsserver.
> >
> > How should I set the resource order to avoid www/ftp migrate with
> nfsserver?
>
> Update to something more recent, you'll find it provides the behaviour
> you're expected.
>
>
> _______________________________________________
> Pacemaker mailing list: Pacemaker at oss.clusterlabs.org
> http://oss.clusterlabs.org/mailman/listinfo/pacemaker
>
> Project Home: http://www.clusterlabs.org
> Getting started: http://www.clusterlabs.org/doc/Cluster_from_Scratch.pdf
> Bugs: http://bugs.clusterlabs.org
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.clusterlabs.org/pipermail/pacemaker/attachments/20130807/108cebf2/attachment.htm>