Open Stack

Le 21/07/2014 17:52, Jay Lau a écrit :
> Sorry, correct one typo. I mean "Promote select_destination as a REST API"
>


-1 to it. During last Summit, we agreed on externalizing current
Scheduler code into a separate project called Gantt. For that, we agreed
on first doing necessary changes within the Scheduler before recreating
a new repository.

By providing select_destinations as a new API endpoint, it would create
a disruptive change where the Scheduler would have a new entrypoint.

As this change would need a spec anyway and as there is a Spec Freeze
now for Juno, I propose to delay this proposal until Gantt is created
and propose a REST API for Gantt instead (in Kilo or L)

-Sylvain

>
> 2014-07-21 23:49 GMT+08:00 Jay Lau <jay.lau.513 at gmail.com
> <mailto:jay.lau.513 at gmail.com>>:
>
>     Now in OpenStack Nova, select_destination is used by
>     create/rebuild/migrate/evacuate VM when selecting target host for
>     those operations.
>
>     There is one requirement that some customers want to get the
>     possible host list when create/rebuild/migrate/evacuate VM so as
>     to create a resource plan for those operations, but currently
>     select_destination is not a REST API, is it possible that we
>     promote this API to be a REST API?
>
>     -- 
>     Thanks,
>
>     Jay
>
>
>
>
> -- 
> Thanks,
>
> Jay
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140721/6f920f59/attachment.html>