yahoo-eng-team team mailing list archive

[OpenStack Infra <1746294@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/531517
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=f029784eaf0d19bd7bb5d4eb66f1ea37d3036099
Submitter: Zuul
Branch:    master

commit f029784eaf0d19bd7bb5d4eb66f1ea37d3036099
Author: Dan Smith <dansmith@xxxxxxxxxx>
Date:   Fri Jan 5 14:47:50 2018 -0800

    Pass limit to /allocation_requests
    
    This makes us pass an upper limit to placement when doing scheduling
    activities. Without this, we'll always receive every host in the
    deployment (that has space for the request), which may be very large.
    
    Closes-Bug: #1746294
    Change-Id: I1c34964a74123b3d94ccae89d7cac0426b57b9b6


** 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/1746294

Title:
  Scheduler requests unlimited results from placement

Status in OpenStack Compute (nova):
  Fix Released

Bug description:
  The scheduler will request an infinitely-large host set from placement
  during scheduling operations. This may be very large on big clouds and
  makes for a huge JSON response from placement to scheduler each time a
  single host needs to be selected.

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