<div dir="ltr">Joe, as said, Amazon reservation is not like implemented in Climate - and really we had different original use cases to have the same result. Amazon instances reservations do not guarantee that instance will be provided to user, as in Climate we started implemented reservations possibilities with this guarantee (due to original use cases). That's why we're mostly speaking about time-based resource management now, not billing purposes.<div>
<br></div><div>Lease creation request now contains the following steps: create lease -> start lease -> end lease</div><div>Also there are user notifications, but they are connected with lease start/end events, so that's not some separated stuff now.</div>
<div><br></div><div>Although, if we'll implement one more second step like 'allocate resources' - that will allow us to have reservations with no guarantees, and that will make Climate possibilities containing Amazon use case.</div>
<div><br></div><div>Thanks</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Mon, Mar 3, 2014 at 9:04 PM, 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:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="HOEnZb"><div class="h5">On Mon, Mar 3, 2014 at 6:27 AM, Anne Gentle <<a href="mailto:anne@openstack.org">anne@openstack.org</a>> wrote:<br>
><br>
><br>
> On Mon, Mar 3, 2014 at 8:20 AM, Joe Gordon <<a href="mailto:joe.gordon0@gmail.com">joe.gordon0@gmail.com</a>> wrote:<br>
>><br>
>> On Mon, Mar 3, 2014 at 4:42 AM, Sylvain Bauza <<a href="mailto:sylvain.bauza@bull.net">sylvain.bauza@bull.net</a>><br>
>> 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>><br>
>> >> 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<br>
>> > single<br>
>> > tenant or user for a certain amount of time, which was not yet<br>
>> > implemented<br>
>> > in Nova: how as an user, can I ask Nova for one compute host with<br>
>> > certain<br>
>> > specs to be exclusively allocated to my needs, starting in 2 days and<br>
>> > being<br>
>> > freed in 5 days ?<br>
>> ><br>
>> > Albeit the exclusive resource lock can be managed on the Nova side,<br>
>> > 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<br>
>> > 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<br>
>> > of<br>
>> > resources. At the moment, we do provide way to reserve virtual instances<br>
>> > by<br>
>> > shelving/unshelving them at the lease start, but we also give<br>
>> > 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<br>
>> > not<br>
>> > to confuse with Nova's scheduler concerns) and capacity planning is too<br>
>> > big<br>
>> > to fail under the Compute's umbrella, as it has been agreed within the<br>
>> > Summit talks and periodical threads.<br>
>><br>
>> 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>
>> is.<br>
>><br>
>> ><br>
>> > From the user standpoint, there are multiple ways to integrate with<br>
>> > Climate<br>
>> > in order to get Capacity Planning capabilities. As you perhaps noticed,<br>
>> > the<br>
>> > workflow for reserving resources is different from one plugin to<br>
>> > 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<br>
>> > implicitly<br>
>> > integrate resource allocation from the Nova API (see virtual instance<br>
>> > API<br>
>> > hook).<br>
>><br>
>> I don't see how Climate reserves resources is relevant to the user.<br>
>><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<br>
>> > also<br>
>> > resource isolation and preemption must also be integrated with<br>
>> > subprojects<br>
>> > (we're currently seeing how to provision Cinder volumes and Neutron<br>
>> > routers<br>
>> > and nets), but anyway we still think there is a (IMHO big) room for<br>
>> > resource<br>
>> > and capacity management on its own project.<br>
>> ><br>
>> > Hoping it's clearer now,<br>
>><br>
>> 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>
>><br>
><br>
> Hi Joe,<br>
> I think it's meant to save consumers money by pricing instances based on<br>
> today's prices.<br>
><br>
> <a href="https://aws.amazon.com/ec2/purchasing-options/reserved-instances/" target="_blank">https://aws.amazon.com/ec2/purchasing-options/reserved-instances/</a><br>
<br>
<br>
</div></div>The reserved concept in Amazon, is very different then the one<br>
proposed here. The amazon concept doesn't support saying I will need<br>
an instance in 3 days, this is trying to support that use case.<br>
Furthermore I am not sure how the climate proposal would allow a<br>
cloud provider to offer a cheaper offering.<br>
<div class="HOEnZb"><div class="h5"><br>
><br>
> Anne<br>
><br>
>><br>
>> > -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>
><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>
_______________________________________________<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><br clear="all"><div><br></div>-- <br><div dir="ltr"><div style="color:rgb(34,34,34);font-family:arial,sans-serif;font-size:13px;background-color:rgb(255,255,255)"><p style="font-size:small;margin:0px;font-family:Helvetica">
Best regards,</p><p style="font-size:small;margin:0px;font-family:Helvetica">Dina Belova</p><p style="font-size:small;margin:0px;font-family:Helvetica">Software Engineer</p><p style="font-size:small;margin:0px;font-family:Helvetica">
Mirantis Inc.</p></div></div>
</div>