← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1289064] [NEW] live migration of instance should claim resources on target compute node

 

Public bug reported:

I'm looking at the current Icehouse code, but this applies to previous
versions as well.

When we create a new instance via _build_instance() or
_build_and_run_instance(), in both cases we call instance_claim() to
test for resources and reserve them.

During a cold migration we call prep_resize() which calls resize_claim()
to reserve resources.

However, when we live-migrate or evacuate an instance we don't do this.
As far as I can see the current code will just spawn the new instance
but the resource usage won't be updated until the audit runs at some
unknown time in the future at which point it will add the new instance
to self.tracked_instances and update the resource usage.

This means that until the audit runs the scheduler has a stale view of
system resources.

** Affects: nova
     Importance: Undecided
         Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1289064

Title:
  live migration of instance should claim resources on target compute
  node

Status in OpenStack Compute (Nova):
  New

Bug description:
  I'm looking at the current Icehouse code, but this applies to previous
  versions as well.

  When we create a new instance via _build_instance() or
  _build_and_run_instance(), in both cases we call instance_claim() to
  test for resources and reserve them.

  During a cold migration we call prep_resize() which calls
  resize_claim() to reserve resources.

  However, when we live-migrate or evacuate an instance we don't do
  this.  As far as I can see the current code will just spawn the new
  instance but the resource usage won't be updated until the audit runs
  at some unknown time in the future at which point it will add the new
  instance to self.tracked_instances and update the resource usage.

  This means that until the audit runs the scheduler has a stale view of
  system resources.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1289064/+subscriptions


Follow ups

References