On Jan 30, 2014, at 5:55 AM, Andrew Laski andrew.la...@rackspace.com wrote:
I'm of the opinion that the scheduler should use objects, for all the reasons
that Nova uses objects, but that they should not be Nova objects. Ultimately
what the scheduler needs is a concept of capacity,
On Thu, Jan 30, 2014 at 8:55 AM, Dan Smith d...@danplanet.com wrote:
I'm of the opinion that the scheduler should use objects, for all the
reasons that Nova uses objects, but that they should not be Nova
objects. Ultimately what the scheduler needs is a concept of capacity,
allocations, and
Hi,
I have heard a couple of conflicting comments about the scheduler and nova
objects that I would like to clear up. In one scheduler/gantt meeting, Gary
Kotton offered to convert the scheduler to use Nova objects. In another I heard
that with the creation of Gantt, the scheduler would avoid
Hi,
I started to do the work – https://review.openstack.org/#/c/65691/. From the
comments on the review it did not seem the right way to go. So I gave up on it.
Sorry to not have updated. I personally think that the scheduler should use
objects, the reason for this is as follows:
1. One of
On 01/30/14 at 04:13am, Gary Kotton wrote:
Hi,
I started to do the work – https://review.openstack.org/#/c/65691/. From the
comments on the review it did not seem the right way to go. So I gave up on it.
Sorry to not have updated. I personally think that the scheduler should use
objects, the
I'm of the opinion that the scheduler should use objects, for all the
reasons that Nova uses objects, but that they should not be Nova
objects. Ultimately what the scheduler needs is a concept of capacity,
allocations, and locality of resources. But the way those are modeled
doesn't need to
