Yes, there is more than the northbound API to discuss. Gary started us there in the Scheduler chat on Oct 1, when he broke the issues down like this: 11:12:22 AM garyk: 1. a user facing API 11:12:41 AM garyk: 2. understanding which resources need to be tracked 11:12:48 AM garyk: 3. backend implementation The full transcript is at http://eavesdrop.openstack.org/meetings/scheduling/2013/scheduling.2013-10-01-15.08.log.html Alex Glikson <GLIKSON at il.ibm.com> wrote on 10/09/2013 02:14:03 AM: > > Good summary. I would also add that in A1 the schedulers (e.g., in > Nova and Cinder) could talk to each other to coordinate. Besides > defining the policy, and the user-facing APIs, I think we should > also outline those cross-component APIs (need to think whether they > have to be user-visible, or can be admin). > > Regards, > Alex -------------- next part -------------- An HTML attachment was scrubbed... URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20131010/c74320a4/attachment.html>