<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 Yathi,<br>
<br>
Le 08/10/2013 05:10, Yathiraj Udupi (yudupi) a écrit :<br>
</div>
<blockquote
cite="mid:2AB0F5F851B5644A9B0AA69323D1100538F6CB51@xmb-aln-x15.cisco.com"
type="cite">
<meta http-equiv="Content-Type" content="text/html;
charset=ISO-8859-1">
<div>Hi, </div>
<div><br>
</div>
<div>Based on the discussions we have had in the past few
scheduler sub-team meetings, I am sharing a document that
proposes an updated Instance Group Model and API extension
model. </div>
<div>This is a work-in-progress draft version, but sharing it for
early feedback. </div>
<div><a moz-do-not-send="true"
href="https://docs.google.com/document/d/17OIiBoIavih-1y4zzK0oXyI66529f-7JTCVj-BcXURA/edit?usp=sharing">https://docs.google.com/document/d/17OIiBoIavih-1y4zzK0oXyI66529f-7JTCVj-BcXURA/edit?usp=sharing</a> </div>
<div><br>
</div>
<div>This model support generic instance types, where an instance
can represent a virtual node of any resource type. But in the
context of Nova, an instance refers to the VM instance. </div>
<div><br>
</div>
<div>This builds on the existing proposal for Instance Group
Extension as documented here in this blueprint: <a
moz-do-not-send="true"
href="https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension">https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension</a> </div>
<div><br>
</div>
<div>Thanks,</div>
<div>Yathi. </div>
<div></div>
</blockquote>
<br>
<br>
<br>
Well, I actually read the design document, and I'm strongly
interested in jumping to the project. <br>
We started a few months ago a Stackforge project, called Climate
[0], aiming to reserve both physical and virtual resources.
Initially, the project came from a blueprint targeting only physical
reservations [1], and then Mirantis folks joined us having a new
usecase for virtual reservations (potentially implementing deferred
starts, as said above).<br>
<br>
Basically, the physical host reservation is not about deferred
starts of instances, it's about grouping for a single tenant a list
of hosts, in other words a whole host allocation (see [2]).<br>
<br>
We'll provide to end-users a Reservation API allowing to define
policies for selecting hosts based on their capabilities [3] and
then create host aggregates (or "Pclouds" if we implement [2]).
Actually, we could define some policies in the Climate host
aggregate for affinity and network-proximity policies, so that any
VM to boot from one of these hosts would be applied these host
aggregate policies.<br>
<br>
As you maybe see, there are some concerns which are close in between
your BP [4] and our vision of Climate. What are your thoughts about
it ?<br>
<br>
[0] :
<meta http-equiv="content-type" content="text/html;
charset=ISO-8859-1">
<a href="https://github.com/stackforge/climate">https://github.com/stackforge/climate</a><br>
[1] :
<a class="moz-txt-link-freetext" href="https://wiki.openstack.org/wiki/Blueprint-nova-planned-resource-reservation-api">https://wiki.openstack.org/wiki/Blueprint-nova-planned-resource-reservation-api</a><br>
[2] : <a class="moz-txt-link-freetext" href="https://wiki.openstack.org/wiki/WholeHostAllocation">https://wiki.openstack.org/wiki/WholeHostAllocation</a><br>
[3] : <a
href="https://docs.google.com/document/d/1U36k5wk0sOUyLl-4Cz8tmk8RQFQGWKO9dVhb87ZxPC8/edit#heading=h.ujapi6o0un65">https://docs.google.com/document/d/1U36k5wk0sOUyLl-4Cz8tmk8RQFQGWKO9dVhb87ZxPC8/edit#heading=h.ujapi6o0un65</a><br>
[4] : <a
href="https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension">https://blueprints.launchpad.net/nova/+spec/instance-group-api-extension</a><br>
</body>
</html>