OpenStack Compute (Nova)

Scheduler defaults to fill-first. Spread-first is more intuitive and should be the default

Reported by Vish Ishaya on 2012-03-26
14
This bug affects 2 people
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Medium
Vish Ishaya

Bug Description

I've mentioned this issue to a few system administrators, and it seems that the general expectation for scheduling is to spread-first. This mirrors the old SimpleScheduler and is a closer approximation of ChanceScheduler than the current fill-first default. I think it will save us a lot of bug-reports if we default to spread-first.

Changed in nova:
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Vish Ishaya (vishvananda)
milestone: none → essex-rc2

Reviewed: https://review.openstack.org/5836
Committed: http://github.com/openstack/nova/commit/d4d081ad4cb028f9f9d389e0d7d4af3873c94cb6
Submitter: Jenkins
Branch: master

commit d4d081ad4cb028f9f9d389e0d7d4af3873c94cb6
Author: Vishvananda Ishaya <email address hidden>
Date: Mon Mar 26 14:33:39 2012 -0700

    Default scheduler to spread-first

     * Fixes bug 965732

    Change-Id: I239b2b235905b30879974144263037eba6ed409f

Changed in nova:
status: In Progress → Fix Committed
Thierry Carrez (ttx) wrote :

A bit uncomfortable with changing the default behavior so late...

Reviewed: https://review.openstack.org/6014
Committed: http://github.com/openstack/nova/commit/b05c9c0a81bbc680de987401981ed30a9b587c9d
Submitter: Jenkins
Branch: milestone-proposed

commit b05c9c0a81bbc680de987401981ed30a9b587c9d
Author: Vishvananda Ishaya <email address hidden>
Date: Mon Mar 26 14:33:39 2012 -0700

    Default scheduler to spread-first

     * Fixes bug 965732

    Change-Id: I239b2b235905b30879974144263037eba6ed409f

Changed in nova:
status: Fix Committed → Fix Released
Thierry Carrez (ttx) on 2012-04-05
Changed in nova:
milestone: essex-rc2 → 2012.1
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Duplicates of this bug

Other bug subscribers