Hi Andrew, > I still don't understand why you can't simply make them regular > cluster resources. > Can you please explain?
I understand your opinion. I surely understand that simple RA can operate an object of respawn by shifting. However, an object of respawn of all users cannot shift to RA. For example, there is the user who does respawn of processing to work even if a node becomes the standby state. But, a primitive resource and the Clone resource stop when a node becomes the standby state. The user needing this respawn cannot easily shift to new environment. Best Regards, Hideo Yamauchi. --- Andrew Beekhof <and...@beekhof.net> wrote: > On Thu, Sep 17, 2009 at 7:03 AM, <renayama19661...@ybb.ne.jp> wrote: > > Hi, > > > > We test a shift to new environment(Corosync+Pacemaker...) now. > > > > A demand was discussed by the next email. > > > > * http://marc.info/?l=openais&m=124615212603435&w=2 > > > > Our many users use respawn. > > These many users feel a problem in moving the function of respawn in new > > environment. > > In addition, many users are not ready to shift in respawn. > > > > Support of respawn is necessary to shift to new environment. > > The support of respawn lets many hesitating users shift. > > > > We think the start by respawn to be the method that had better be realized > > in Pacemaker in the > same > > way as GUI. > > > > Will you think about the realization of the function like respawn supported > > in Heartbeat in > new > > environment? > > > > * I recognize that respawn is a provisional function in Heartbeat. > > * However, many users use it. > > I still don't understand why you can't simply make them regular > cluster resources. > Can you please explain? > > _______________________________________________ > Pacemaker mailing list > Pacemaker@oss.clusterlabs.org > http://oss.clusterlabs.org/mailman/listinfo/pacemaker > _______________________________________________ Pacemaker mailing list Pacemaker@oss.clusterlabs.org http://oss.clusterlabs.org/mailman/listinfo/pacemaker
