* WIP migration scripts
* migrate compute node
* do not skip some migration
* migrate more properties on compute node
* migrate software installation
* migrate compute already linked to a project
* trigger instance tree migration
* migrate more instance trees
* migrate Instance Tree, Software/Slave Instance
* migrate instance tree
* do not create not needed activities
* migrate instance tree linked to an existing project
* migrate existing subscription requests/projects
* allow to run the migration multiple time
* move an instance to the same virtual master than his main compute node
* if all instances are linked to the same project, move the computer to that project
* migrate computer network
* move to personal if no instance allocated
* partially destroyed instanc ewill move to personal
  Unallocated instance will use remote note
* force migration to remaining compute nodes
* break network link if not consistent
* create Remote Node and Remote Instances
* reduce concurrency on instance tree creation
* try to reduce conflict
* some sla xml seems broken
* instances do not always have a predecessor
* it seems activity is also triggered on already migrated instance
* some instances were manually invalidated...
* do not go too slowly
* generate a graph showing the virtual master relation
* another report
* prepare migrating Instance Tree to a remote node
* change report output
* fixup instance virtual master migration
  do not forget to also move the successor to the new virtual master
* do not fail if already migrated
* create Software Product (and its variations)
* create Instance Node
* create allocation supplies