Hi, On Fri, Jan 14, 2011 at 01:57:40PM +0100, Alain.Moulle wrote: > Hi Dejan, > > thanks for your response. > ok, but on what clue crm knows that it must stop/start instead of live > migrate ?
It doesn't know anything about it. All crm does is invoke crm_resource -M -r ... and crm_resource inserts a location constraint. Then it's up to the PE to compute a new set of actions. > how does it recognize that there are migrate function availble in the > OCF script or > decide that it must execute a stop then start ? migrate has to be enabled for the resource using the allow-migrate meta attribute. > FYI : > it seems that migrate (or move) does not work as fine as before > with the pacemaker 1.1.2-7 release (in older releases it was working > fine) > I test it with Dummy ocf script and it works fine, but with resources > which take more time to start (like Lustre OST, or VM), it does not work > as fine as in older releases. It's sort of difficult to quantify what does "fine" mean in this context. Do you have any hard data (logs, etc)? Thanks, Dejan > I'm not able for now to identify where is exactly the problem ... > > Alain > _______________________________________________ > Linux-HA mailing list > [email protected] > http://lists.linux-ha.org/mailman/listinfo/linux-ha > See also: http://linux-ha.org/ReportingProblems _______________________________________________ Linux-HA mailing list [email protected] http://lists.linux-ha.org/mailman/listinfo/linux-ha See also: http://linux-ha.org/ReportingProblems
