<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">Hi Mike,<br>
<br>
Dina and you outlined some differences in terms of seeing what is
dependent on what. <br>
As Dina explained, Climate plans to be integrated into Nova and
Heat logics, where Heat and Nova would request Climate API by
asking for a lease and would tag on their own the resources as
'RESERVED'.<br>
On your point, and correct me if I'm wrong, you would rather see
Climate on top of Heat and Nova, scheduling resources on its own,
and only send creation requests to Heat and Nova. <br>
<br>
I'm happy to say both of you are right : Climate aims to be both
called by Nova and *also* calling Nova. That's just matter of what
Climate *is*. And here is the confusion.<br>
<br>
That's why Climate is not only one API endpoint. It actually have
two distinct endpoints : one called the Lease API endpoint, and
one called the Resource Reservation API endpoint.<br>
<br>
As a Climate developer working on physical hosts reservations (and
not Heat stacks), my concern is to be able to guarantee to a REST
client (either a user or another service) that if this user wants
to provision X hosts on a specific timeframe in the future
(immediate or in 10 years), Climate will be able to provision
them. By meaning "being able" and "guarantee", I do use strong
words for stating that we engage ourselves to be able to plan what
will be resources capacity state in the future.<br>
<br>
This decision-making process (ie. this "Climate scheduler") will
be implemented as RPC Service for the Reservation API, and thus
will needs to keep its own persistence layer in Climate. Of
course, it will request the Lease API for really creating the
lease and managing lease start/end hooks, that's the Lease API job.<br>
<br>
<br>
Provided you would want to use the Reservation API for "reserving"
Heat stacks, you would have to implement it tho.<br>
<br>
<br>
Thanks,<br>
-Sylvain<br>
<br>
Le 06/10/2013 20:41, Mike Spreitzer a écrit :<br>
</div>
<blockquote
cite="mid:OF3CDE27B2.72A92AB8-ON85257BFC.00659441-85257BFC.0066A36B@us.ibm.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<font face="sans-serif" size="2">Thanks, Dina. Yes, we do not
understand
each other; can I ask some more questions?</font>
<br>
<br>
<font face="sans-serif" size="2">You outlined a two-step
reservation
process ("</font><font size="3">We assume the following
reservation
process for the OpenStack services</font><font face="sans-serif"
size="2">..."),
and right after that talked about changing your mind to use Heat
instead
of individual services. So I am confused, I am not sure which
of
your remarks reflect your current thinking and which reflect old
thinking.
Can you just state your current thinking?</font>
<br>
<br>
<font face="sans-serif" size="2">On what basis would Climate
decide to
start or stop a lease? What sort of event notifications would
Climate
be sending, and when and why, and what would subscribers do upon
receipt
of such notifications?</font>
<br>
<br>
<font face="sans-serif" size="2">If the individual resource
services
continue to make independent scheduling decisions as they do
today, what
value does Climate add?</font>
<br>
<br>
<font face="sans-serif" size="2">Maybe a little more detailed
outline
of what happens in your current thinking, in support of an
explicitly stated
use case that shows the value, would help here.</font>
<br>
<br>
<font face="sans-serif" size="2">Thanks,</font>
<br>
<font face="sans-serif" size="2">Mike</font>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
OpenStack-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a>
<a class="moz-txt-link-freetext" href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a>
</pre>
</blockquote>
<br>
</body>
</html>