Open Stack

>
> So after a reservation lease for a VM is made by Climate, who acts on it
> to finally instantiate the VM ? Is it Climate or Nova should act on the
> lease to finally provision the VM.


Now to take resources for VM it's actually created and then immediately
shelved, not to be in active state and not to actually work while it's not
needed. Climate then uses Keystone trusts to unshelve it the time lease
actually starts.

Thanks,
Dina


On Tue, Feb 11, 2014 at 9:28 PM, Yathiraj Udupi (yudupi)
<yudupi at cisco.com>wrote:

>  hi Sylvain and Dina,
>
>  Thanks for your pointers about Climate.  I will take a closer look at it
> and try it out.  So after a reservation lease for a VM is made by Climate,
> who acts on it to finally instantiate the VM ? Is it Climate or Nova should
> act on the lease to finally provision the VM.
>
>  Thanks,
> Yathi.
>
>   On 2/11/14, 8:42 AM, "Sylvain Bauza" <sylvain.bauza at bull.net> wrote:
>
>   Le 11/02/2014 17:23, Yathiraj Udupi (yudupi) a écrit :
>
> Hi Dina,
>
>  Thanks for note about Climate logic.  This is something that will be
> very useful, when we will have to schedule from Nova multiple instances (of
> potentially different flavors) as a single request.  If the Solver
> Scheduler, can make a request to the Climate service to reserve the
> resources soon after the placement decision has been made, then the nova
> provisioning logic can handle the resource provisioning using the climate
> reserved leases.  Regarding Solver Scheduler for your reference, just sent
> another email about this with some pointers about it.  Otherwise this is
> the blueprint -
> https://blueprints.launchpad.net/nova/+spec/solver-scheduler
> I guess this is something to explore more and see how Nova provisioning
> logic to work with Climate leases. Or this is something that already works.
>  I need to find out more about Climate.
>
>  Thanks,
> Yathi.
>
>
>
> There are possibly 2 ways for creating a lease : either thru the CLI or by
> the python binding.
>
> We implemented these 2 possibilities within the current Climate 0.1
> release :
>  - a Nova extension plugin is responsible for creating the lease if a VM
> should be reserved (using the Climate pythonclient binding)
>  - an user can request for reserving a compute host using the Climate
> python client directly
>
> Both logics (VM and compute host) are actually referring to 2 distinct
> plugins in the Climate manager, so the actions are completely different.
>
> Based on your use-case, you could imagine a call from the SolverScheduler
> to Climate for creating a lease containing multiple VM reservations, and
> either you would use the Climate VM plugin or you would use a dedicated
> plugin if your need is different.
>
> I don't think that's a huge volume of work, as Climate already defines and
> implements the main features that you need.
>
> -Sylvain
>
>
> _______________________________________________
> OpenStack-dev mailing list
> OpenStack-dev at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>


-- 

Best regards,

Dina Belova

Software Engineer

Mirantis Inc.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-dev/attachments/20140211/7f4212a6/attachment.html>