On 29 November 2013 04:50, Gary Kotton <gkot...@vmware.com> wrote: > I am not really sure how we can have a client tree without even having > discussed the API's and interfaces. From the initial round of emails the > intention was to make use of the RPC mechanism to speak with the scheduler.
It still is. We have an existing RPC API in the nova/scheduler tree. > One option worth thinking about is to introduce a new scheduling driver to > nova - this driver will interface with the external scheduler. This will > let us define the scheduling API, model etc, without being in the current > confines of Nova. This will also enable all of the other modules, for > example Cinder to hook into it. The problem is that that is the boil-the-ocean approach that hasn't succeeded for several cycles. We have interest in trying something new - there are three failure modes I can see: A - we fail to split it out enough, and noone else uses it. B - we introduce a performance / correctness problem during the split out C - we stall and don't do anything Right now, I am mainly worried about B. Getting good APIs is step two after getting a solid split out scheduler. -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