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-schedulersome misleading about https://blueprints.launchpad.net/nova/+spec/no-db-scheduler 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: 1) Scheduler should store all data by self: 1.1) Keep all data locally + mechanism that effectively sync all schedulers 1.2) new scheduler RPC method: update_host(host_name, namespace, values) e.g. in this patchset https://review.openstack.org/#/c/45867/ It is still WIP: During this week we are going to make final version: a) Garbage collector for sync mechanism b) Support of name spaces c) Support of sqlaclhemy backends (not only memcached) 2) Cleanup Nova scheduler 2.1) Remove compute_node tables 2.2) Remove from db.api methods that returns state of hosts, and use Scheduler 3.a) Make Nova Scheduler as a separated service 3.b) Call from cinder in "cinder" namespace Scheduler Service update_host() method 4) Move cinder scheduler rpc method to scheduler service 5) Remove Cinder Scheduler 3.c) Call from malina in "malina" namespace Scheduler Service update_host() method 4) Move malina scheduler rpc method to scheduler service 5) Remove Malina Scheduler I don't think that it is step backward as it was mentioned in etherpad.. Best regards, Boris Pavlovic On Fri, Nov 22, 2013 at 12:58 AM, Robert Collins <robe...@robertcollins.net>wrote: > https://etherpad.openstack.org/p/icehouse-external-scheduler > > I'm looking for 4-5 folk who have: > - modest Nova skills > - time to follow a fairly mechanical (but careful and detailed work > needed) plan to break the status quo around scheduler extraction > > And of course, discussion galore about the idea :) > > Cheers, > 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 >
_______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
