<div dir="ltr"><div>Thanks Chris and Sylvain.<br><br></div>@Chris, yes,my case is do a select_destination call, and then call the create/rebuild/migrate/evacuate while specifying the selected destination<br><br>@Sylvain, I was also thinking of Gantt, but as you said, Gantt might be available in K or L which might be a bit late, that's why I say I want to first do it in nova then migrate to Gantt. OK, agree with you, considering the spec is freeze now, I will consider this in K or L and find a workaround for now. ;-)<br>
<br>Thanks.<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">2014-07-22 1:13 GMT+08:00 Sylvain Bauza <span dir="ltr"><<a href="mailto:sbauza@redhat.com" target="_blank">sbauza@redhat.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
<div>Le 21/07/2014 17:52, Jay Lau a écrit :<br>
</div><div class="">
<blockquote type="cite">
<div dir="ltr">Sorry, correct one typo. I mean "Promote
select_destination as a REST API"<br>
<div>
<div class="gmail_extra"><br>
</div>
</div>
</div>
</blockquote>
<br>
<br></div>
-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.<br>
<br>
By providing select_destinations as a new API endpoint, it would
create a disruptive change where the Scheduler would have a new
entrypoint.<br>
<br>
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)<span class="HOEnZb"><font color="#888888"><br>
<br>
-Sylvain<br>
<br>
</font></span><blockquote type="cite"><div class="">
<div dir="ltr">
<div>
<div class="gmail_extra"><br>
<div class="gmail_quote">2014-07-21 23:49 GMT+08:00 Jay Lau
<span dir="ltr"><<a href="mailto:jay.lau.513@gmail.com" target="_blank">jay.lau.513@gmail.com</a>></span>:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">
<div dir="ltr">
<div>Now in OpenStack Nova, select_destination is used
by create/rebuild/migrate/evacuate VM when selecting
target host for those operations.<br>
<br>
</div>
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?<span><font color="#888888"><br>
<div>
<div>
<div>
<div><br>
-- <br>
<div dir="ltr">
<div>Thanks,<br>
<br>
</div>
Jay<br>
</div>
</div>
</div>
</div>
</div>
</font></span></div>
</blockquote>
</div>
<br>
<br clear="all">
<br>
-- <br>
<div dir="ltr">
<div>Thanks,<br>
<br>
</div>
Jay<br>
</div>
</div>
</div>
</div>
<br>
<fieldset></fieldset>
<br>
</div><div class=""><pre>_______________________________________________
OpenStack-dev mailing list
<a href="mailto:OpenStack-dev@lists.openstack.org" target="_blank">OpenStack-dev@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</div></blockquote>
<br>
</div>
</blockquote></div><br><br clear="all"><br>-- <br><div dir="ltr"><div>Thanks,<br><br></div>Jay<br></div>
</div>