[Pacemaker] Migration atomicity

[Andrew Beekhof]

On Wed, Mar 14, 2012 at 6:40 PM, Vladislav Bogdanov
<bubble at hoster-ok.com> wrote:
> Hi,
>
> I'm observing a little bit unintuitive behavior of migration logic when
> transition is aborted (due to CIB change) in the middle of the resource
> migration.
>
> That is:
> 1. nodea: migrate_to nodeb
> 2. transition abort
> 3. nodeb: stop
> 4. nodea: migrate_to nodec

I'd like to see that a crm_report showing that behavior.
Because I'm looking at the same scenario and I see:

1. nodea: migrate_to nodeb
2. transition abort
3. nodea: stop
4. nodeb: stop
5. nodec: start

> 5. nodec: migrate_from nodea
> (note: no stop on nodea)
>
> While I expect migration operation pair to be "more atomic":
> 1. nodea: migrate_to nodeb
> 2. transition abort
> 3. nodeb: migrate_from nodea
> 4. nodea: stop
> 5. nodeb: migrate_to nodec
> 6. nodec: migrate_from nodeb
> 7. nodeb: stop
>
> Is the current behavior intended?
>
> hb_report is available.
>
> Best regards,
> Vladislav
>
> _______________________________________________
> 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