yahoo-eng-team team mailing list archive

[Alex Xu <soulxu@xxxxxxxxx>]

Public bug reported:

When rebuild instance with another image, nova won't rescheduling
instance to another host.

The new image make have bigger disk requirement, that orginal host
didn't satisfy it.

And new image may include different numa topology, the nova didn't
consider that also.

So nova should try to schedule instance to another host if the orignal
host doesn't satisfy the resource requirement. But the original host
should be the first choice.

** Affects: nova
     Importance: Undecided
     Assignee: Alex Xu (xuhj)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Alex Xu (xuhj)

** Description changed:

  When rebuild instance with another image, nova won't rescheduling
  instance to another host.
  
  The new image make have bigger disk requirement, that orginal host
  didn't satisfy it.
  
  And new image may include different numa topology, the nova didn't
  consider that also.
  
  So nova should try to schedule instance to another host if the orignal
  host doesn't satisfy the resource requirement. But the original host
- should be the first choice, that can reduce
+ should be the first choice.

-- 
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/1402522

Title:
  Rebuild won't scheduling instance to another host even the orignal
  host didn't satisfy the resource requirement

Status in OpenStack Compute (Nova):
  New

Bug description:
  When rebuild instance with another image, nova won't rescheduling
  instance to another host.

  The new image make have bigger disk requirement, that orginal host
  didn't satisfy it.

  And new image may include different numa topology, the nova didn't
  consider that also.

  So nova should try to schedule instance to another host if the orignal
  host doesn't satisfy the resource requirement. But the original host
  should be the first choice.

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