<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">Le 11/02/2014 17:23, Yathiraj Udupi
(yudupi) a écrit :<br>
</div>
<blockquote cite="mid:CF1F8D7F.2835A%25yudupi@cisco.com" type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>Hi Dina, </div>
<div><br>
</div>
<div>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 - <a moz-do-not-send="true"
href="https://blueprints.launchpad.net/nova/+spec/solver-scheduler">https://blueprints.launchpad.net/nova/+spec/solver-scheduler</a> </div>
<div>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. </div>
<div><br>
</div>
<div>Thanks,</div>
<div>Yathi. </div>
<br>
</blockquote>
<br>
<br>
There are possibly 2 ways for creating a lease : either thru the CLI
or by the python binding.<br>
<br>
We implemented these 2 possibilities within the current Climate 0.1
release : <br>
- a Nova extension plugin is responsible for creating the lease if
a VM should be reserved (using the Climate pythonclient binding)<br>
- an user can request for reserving a compute host using the
Climate python client directly<br>
<br>
Both logics (VM and compute host) are actually referring to 2
distinct plugins in the Climate manager, so the actions are
completely different. <br>
<br>
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.<br>
<br>
I don't think that's a huge volume of work, as Climate already
defines and implements the main features that you need.<br>
<br>
-Sylvain<br>
</body>
</html>