yahoo-eng-team team mailing list archive

[Zhenyu Zheng <zhengzhenyu@xxxxxxxxxx>]

Public bug reported:

In the current implementation, when doing instance resize action. The CONF.allow_resize_to_same_host is first checked in 
compute/api which is on controller node. If CONF.allow_resize_to_same_host = True, nothing will added to 
filter_properties['ignore_hosts'], if it is set to False, the source host will be added to filter_properties['ignore_hosts'] and it 
will be ignored when performing select_destinations.

The value of CONF.allow_resize_to_same_host has been checked again in compute/manager.py which is on the destination
host which has already been selected by scheduler.

This will lead to a problem, if CONF.allow_resize_to_same_host parameter is set to True in controller node but set to False
or didn't set in compute node. When scheduler decided that the original compute node is the best one for resize but when
the compute node implementing the resize action, it will throw an exception.

The value of CONF.allow_resize_to_same_host should only check once in controller node (compute/api.py) and let scheduler
judge which host is best for rebuild, the compute node should only perform the action when it has been selected.

** Affects: nova
     Importance: Undecided
     Assignee: Zhenyu Zheng (zhengzhenyu)
         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/1459468

Title:
  When doing resize action, CONF.allow_resize_on_same_host should check
  only once

Status in OpenStack Compute (Nova):
  New

Bug description:
  In the current implementation, when doing instance resize action. The CONF.allow_resize_to_same_host is first checked in 
  compute/api which is on controller node. If CONF.allow_resize_to_same_host = True, nothing will added to 
  filter_properties['ignore_hosts'], if it is set to False, the source host will be added to filter_properties['ignore_hosts'] and it 
  will be ignored when performing select_destinations.

  The value of CONF.allow_resize_to_same_host has been checked again in compute/manager.py which is on the destination
  host which has already been selected by scheduler.

  This will lead to a problem, if CONF.allow_resize_to_same_host parameter is set to True in controller node but set to False
  or didn't set in compute node. When scheduler decided that the original compute node is the best one for resize but when
  the compute node implementing the resize action, it will throw an exception.

  The value of CONF.allow_resize_to_same_host should only check once in controller node (compute/api.py) and let scheduler
  judge which host is best for rebuild, the compute node should only perform the action when it has been selected.

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