<div dir="ltr"><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 3, 2014 at 8:20 AM, Joe Gordon <span dir="ltr"><<a href="mailto:joe.gordon0@gmail.com" target="_blank">joe.gordon0@gmail.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex"><div class=""><div class="h5">On Mon, Mar 3, 2014 at 4:42 AM, Sylvain Bauza <<a href="mailto:sylvain.bauza@bull.net">sylvain.bauza@bull.net</a>> wrote:<br>
> Hi Joe,<br>
><br>
> Thanks for your reply, I'll try to further explain.<br>
><br>
><br>
> Le 03/03/2014 05:33, Joe Gordon a écrit :<br>
><br>
>> On Sun, Mar 2, 2014 at 11:32 AM, Dina Belova <<a href="mailto:dbelova@mirantis.com">dbelova@mirantis.com</a>> wrote:<br>
>>><br>
>>> Hello, folks!<br>
>>><br>
>>> I'd like to request Climate project review for incubation. Here is<br>
>>> official<br>
>>> incubation application:<br>
>>><br>
>>> <a href="https://wiki.openstack.org/wiki/Climate/Incubation" target="_blank">https://wiki.openstack.org/wiki/Climate/Incubation</a><br>
>><br>
>> I'm unclear on what Climate is trying to solve. I read the 'Detailed<br>
>> Description' from the link above, and it states Climate is trying to<br>
>> solve two uses cases (and the more generalized cases of those).<br>
>><br>
>> 1) Compute host reservation (when user with admin privileges can<br>
>> reserve hardware resources that are dedicated to the sole use of a<br>
>> tenant)<br>
>> 2) Virtual machine (instance) reservation (when user may ask<br>
>> reservation service to provide him working VM not necessary now, but<br>
>> also in the future)<br>
><br>
> Climate is born from the idea of dedicating compute resources to a single<br>
> tenant or user for a certain amount of time, which was not yet implemented<br>
> in Nova: how as an user, can I ask Nova for one compute host with certain<br>
> specs to be exclusively allocated to my needs, starting in 2 days and being<br>
> freed in 5 days ?<br>
><br>
> Albeit the exclusive resource lock can be managed on the Nova side, there is<br>
> currently no possibilities to ensure resource planner.<br>
><br>
> Of course, and that's why we think Climate can also stand by its own<br>
> Program, resource reservation can be seen on a more general way : what about<br>
> reserving an Heat stack with its volume and network nested resources ?<br>
><br>
><br>
>> You want to support being able to reserve an instance in the future.<br>
>> As a cloud operator how do I take advantage of that information? As a<br>
>> cloud consumer, what is the benefit? Today OpenStack supports both<br>
>> uses cases, except it can't request an Instance for the future.<br>
><br>
><br>
> Again, that's not only reserving an instance, but rather a complex mix of<br>
> resources. At the moment, we do provide way to reserve virtual instances by<br>
> shelving/unshelving them at the lease start, but we also give possibility to<br>
> provide dedicated compute hosts. Considering it, the logic of resource<br>
> allocation and scheduling (take the word as resource planner, in order not<br>
> to confuse with Nova's scheduler concerns) and capacity planning is too big<br>
> to fail under the Compute's umbrella, as it has been agreed within the<br>
> Summit talks and periodical threads.<br>
<br>
</div></div>Capacity planning not falling under Compute's umbrella is news to me,<br>
are you referring to Gantt and scheduling in general? Perhaps I don't<br>
fully understand the full extent of what 'capacity planning' actually<br>
<div class="">is.<br>
<br>
><br>
> From the user standpoint, there are multiple ways to integrate with Climate<br>
> in order to get Capacity Planning capabilities. As you perhaps noticed, the<br>
> workflow for reserving resources is different from one plugin to another.<br>
> Either we say the user has to explicitly request for dedicated resources<br>
> (using Climate CLI, see dedicate compute hosts allocation), or we implicitly<br>
> integrate resource allocation from the Nova API (see virtual instance API<br>
> hook).<br>
<br>
</div>I don't see how Climate reserves resources is relevant to the user.<br>
<div class=""><br>
><br>
> We truly accept our current implementation as a first prototype, where<br>
> scheduling decisions can be improved (possibly thanks to some tight<br>
> integration with a future external Scheduler aaS, hello Gantt), where also<br>
> resource isolation and preemption must also be integrated with subprojects<br>
> (we're currently seeing how to provision Cinder volumes and Neutron routers<br>
> and nets), but anyway we still think there is a (IMHO big) room for resource<br>
> and capacity management on its own project.<br>
><br>
> Hoping it's clearer now,<br>
<br>
</div>Unfortunately that doesn't clarify things for me.<br>
<br>
>From the user's point of view what is the benefit from making a<br>
reservation in the future? Versus what Nova supports today, asking for<br>
an instance in the present.<br>
<br>
Same thing from the operator's perspective, what is the benefit of<br>
taking reservations for the future?<br>
<br>
This whole model is unclear to me because as far as I can tell no<br>
other clouds out there support this model, so I have nothing to<br>
compare it to.<br>
<div class=""><div class="h5"><br></div></div></blockquote><div><br></div><div>Hi Joe,</div><div>I think it's meant to save consumers money by pricing instances based on today's prices. </div><div><br></div><div>
<a href="https://aws.amazon.com/ec2/purchasing-options/reserved-instances/">https://aws.amazon.com/ec2/purchasing-options/reserved-instances/</a><br></div><div><br></div><div>Anne</div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left-width:1px;border-left-color:rgb(204,204,204);border-left-style:solid;padding-left:1ex">
<div class=""><div class="h5">
> -Sylvain<br>
><br>
><br>
> _______________________________________________<br>
> OpenStack-dev mailing list<br>
> <a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
> <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><br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
<a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>
<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><br>
</div></div></blockquote></div><br></div></div>