Open Stack

On Jan 16, 2014, at 1:12 PM, Chris Friesen <chris.friesen at windriver.com> wrote:

> Hi,
> 
> I'm trying to figure out how resource tracking is intended to work for live migration and evacuation.
> 
> For a while I thought that maybe we were relying on the call to ComputeManager._instance_update() in ComputeManager.post_live_migration_at_destination().  However, in
> ResourceTracker.update_usage() we see that on a live migration the instance that has just migrated over isn't listed in self.tracked_instances and so we don't actually update its usage.
> 
> As far as I can see, the current code will just wait for the audit to run at some unknown time in the future and call update_available_resource(), which will add the newly-migrated instance to self.tracked_instances and update the resource usage.
> 
> From my poking around so far the same thing holds true for evacuation as well.
> 
> In either case, just waiting for the audit seems somewhat haphazard.
> 
> Would it make sense to do something like ResourceTracker.instance_claim() during the migration/evacuate and properly track the resources rather than wait for the audit?

Yes that makes sense to me. Live migration was around before we had a resource tracker so it probably was just never updated.

Vish

> 
> Chris
> 
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 455 bytes
Desc: Message signed with OpenPGP using GPGMail
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140116/875b4566/attachment.pgp>