17 Apr
2009
17 Apr
'09
1:04 p.m.
Hi
I think it might be useful to know the exact state at sometime. Maybe we an split is up: It only get in migration state when the users triggered the operation. It stays in running when it is a load-balacing operation.
The user cannot request a migration, there is no reason for that. Migration can only be triggered by the local/internal scheduler of VM placement. And in such a case, as long as the user receives the contracted capacity, the migration is transparent. Ignacio