On 22 November 2013 15:57, Boris Pavlovic <bpavlo...@mirantis.com> wrote: > Robert, > > It is nice that community like idea of making one scheduler as a service. > > > But I saw in https://etherpad.openstack.org/p/icehouse-external-scheduler > some misleading about > https://blueprints.launchpad.net/nova/+spec/no-db-scheduler
Ok, lets fix that up. > Approach no-db-scheduler is actually base step that allows us to make > scalable scheduler as a service without huge pain of changing too much in > current architecture: As I mention on HK summit, there are just few steps, > that should be implemented: .. > 3.a) Make Nova Scheduler as a separated service This is the bit that all previous efforts on the scheduler have failed to deliver - and it's just the bit that my proposal tackles. ... > I don't think that it is step backward as it was mentioned in etherpad.. I don't see any mention of a step backwards. -Rob -- Robert Collins <rbtcoll...@hp.com> Distinguished Technologist HP Converged Cloud _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
