[openstack-dev] [Gantt] Looking for some answers...
bpavlovic at mirantis.com
Mon Jan 6 20:08:37 UTC 2014
It should be pretty easy to do this in gantt though. Right now I would
probably do it against the current scheduler and then we'll port it
over. I don't think we should do major work only in gantt until we're
ready to deprecate the current scheduler.
That make sense.
In couple of they we will try to make some "real" benchmarks using Rally,
to ensure that no-db-scheduler works better then previous. So I hope we
will get interest from community.
It's a new repo created with the history filtered out. The history
was only maintained for code kept. That seems pretty ideal to me.
Not sure that nova history is right history for scheduler (Why not Cinder
for example? why exactly Nova?).
Imho Scheduler aaS for all projects and Nova Scheduler
are different things.
On Mon, Jan 6, 2014 at 11:59 PM, Russell Bryant <rbryant at redhat.com> wrote:
> On 01/06/2014 02:52 PM, Boris Pavlovic wrote:
> > Vish,
> > and as I understand it the hope will be to do the no-db-scheduler
> > There was quite a bit of debate on whether to do the no-db-scheduler
> > before or after the forklift and I think the consensus was to do the
> > forklift
> > first.
> > Current Nova scheduler is so deeply bind to nova data models, that it is
> > useless for every other project.
> > So I don't think that forkit in such state of Nova Scheduler is useful
> > for any other project.
> It should be pretty easy to do this in gantt though. Right now I would
> probably do it against the current scheduler and then we'll port it
> over. I don't think we should do major work only in gantt until we're
> ready to deprecate the current scheduler.
> Russell Bryant
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the OpenStack-dev