<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 Jay,<br>
<br>
Le 20/01/2014 17:34, Jay Pipes a écrit :<br>
</div>
<blockquote
cite="mid:CAAE6tVZHGBf=QN55kJ0eWkDEzqe+b3F54wQAZJW5f6QOz+rSxA@mail.gmail.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">On Mon, Jan 20, 2014 at 11:18 AM,
Sylvain Bauza <span dir="ltr"><<a moz-do-not-send="true"
href="mailto:sylvain.bauza@bull.net" target="_blank">sylvain.bauza@bull.net</a>></span>
wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
<div>Jay, please be aware of the existence of Climate,
which is a Stackforge project for managing dedicated
resources (like AWS reserved instances). This is not
another API extension, but another API endpoint for
creating what we call "leases" which can be started now
or in the future and last for a certain amount of time.
We personnally think there is a space for Reservations
in Openstack, and this needs to be done as a service.<span
class="HOEnZb"></span></div>
</blockquote>
<div><br>
</div>
<div>Hi Sylvain! Hope all is well with you :)<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
Thanks, doing well but a bit under pressure, as Climate has its 0.1
milestone this week...<br>
<br>
<blockquote
cite="mid:CAAE6tVZHGBf=QN55kJ0eWkDEzqe+b3F54wQAZJW5f6QOz+rSxA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div><br>
</div>
<div>So, I actually don't think the two concepts
(reservations and "isolated instances") are competing
ideas. Isolated instances are actually not reserved. They
are simply instances that have a condition placed on their
assignment to a particular compute node that the node must
only be hosting other instances of one or more specified
projects (tenants).<br>
<br>
</div>
</div>
</div>
</div>
</blockquote>
<br>
I got your idea. This filter [1] already does most of the work,
although it relies on aggregates and requires admin management. The
main issue with isolated instances is that it requires kind of
capacity planning for making sure you can cope with the load, that's
why we placed the idea of having such a placement scheduler.<br>
<br>
[1] :
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a
href="https://github.com/openstack/nova/blob/master/nova/scheduler/filters/aggregate_multitenancy_isolation.py">https://github.com/openstack/nova/blob/master/nova/scheduler/filters/aggregate_multitenancy_isolation.py</a>
<blockquote
cite="mid:CAAE6tVZHGBf=QN55kJ0eWkDEzqe+b3F54wQAZJW5f6QOz+rSxA@mail.gmail.com"
type="cite">
<div dir="ltr">
<div class="gmail_extra">
<div class="gmail_quote">
<div>Best,<br>
</div>
<div>-jay <br>
</div>
</div>
<br>
</div>
</div>
<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>