On 12/02/2013 10:59 AM, Gary Kotton wrote: > I think that this is certainly different. It is something that we we want > and need a user facing API. > Examples: > - aggregates > - per host scheduling > - instance groups > > Etc. > > That is just taking the nova options into account and not the other > modules. How doul one configure that we would like to have storage > proximity for a VM? This is where things start to get very interesting and > enable the cross service scheduling (which is the goal of this no?).
An explicit part of this plan is that all of the things you're talking about are *not* in scope until the forklift is complete and the new thing is a functional replacement for the existing nova-scheduler. We want to get the project established and going so that it is a place where this work can take place. We do *not* want to slow down the work of getting the project established by making these things a prerequisite. -- Russell Bryant _______________________________________________ OpenStack-dev mailing list OpenStack-dev@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
