yahoo-eng-team team mailing list archive

[OpenStack Infra <1553099@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/288373
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=214b7550bca6b78c99660f257fc63d6ea4ccf212
Submitter: Jenkins
Branch:    master

commit 214b7550bca6b78c99660f257fc63d6ea4ccf212
Author: pcarlton <paul.carlton2@xxxxxxx>
Date:   Fri Mar 4 08:46:03 2016 +0000

    Add include_disabled parameter to service_get_all_by_binary
    
    The database query service_get_all_by_binary should return a list
    of services with the specified binary but it currently excludes
    disabled hosts. This change adds a name parameter called
    'include_disabled' which provides the caller with the option
    of having disabled hosts returned too.
    
    This query is used by the scheduler to retrieve the list of
    available hosts. The initial list should include disabled hosts.
    The ComputeFilter removes disabled hosts so inclusion of this
    filter is the proper way to exclude disabled hosts.  Excluding
    disabled hosts from the initial list prevents the forcehost
    feature from being used to place an instance on a disabled host.
    
    The query is only used in objects.ServiceList.get_by_binary which
    is only called in one other place, in cells/state.py by
    CellStateManager._get_compute_hosts. Adding the named parameter
    to the get_by_binary method of the ServiceList class means the
    behaviour of CellStateManager._get_compute_hosts will not be
    impacted.
    
    Change-Id: I05c2716da45119e6e6aa272b0701be9ae098842c
    Closes-Bug: #1553099


** Changed in: nova
       Status: In Progress => Fix Released

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

Title:
  forcehost feature not working

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  The option of adding a specific nova compute host to the availability-
  zone selection as per http://docs.openstack.org/user-guide-
  admin/cli_nova_specify_host.html is not working, i.e. boot  ...
  --availability-zone nova:server2 should schedule the instance to
  server2  regardless of scheduler filters or server2's capacity to
  accommodate the instance.

  This feature is useful for testing newly provisioned nodes or
  potentially faulty nodes.

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