<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=us-ascii">
<meta name="Generator" content="Microsoft Exchange Server">
<!-- converted from text --><style><!-- .EmailQuote { margin-left: 1pt; padding-left: 4pt; border-left: #800000 2px solid; } --></style>
</head>
<body>
<div>
<div style="font-size:10pt">
<p style="margin-top:0; margin-bottom:0">The solver-scheduler is designed to solve for an arbitrary list of instances of different flavors. We need to have some updated apis in the scheduler to be able to pass on such requests. Instance group api is an initial
effort to specify such groups. </p>
<p style="margin-top:0; margin-bottom:0"> </p>
<p style="margin-top:0; margin-bottom:0">Even now the existing solver scheduler patch, works for a group request, only that it is a group of a single flavor. It still solves once for the entire group based on the constraints on available capacity. </p>
<p style="margin-top:0; margin-bottom:0"> </p>
<p style="margin-top:0; margin-bottom:0">With updates to the api that call the solver scheduler we can easily demonstrate how an arbitrary group of VM request can be satisfied and solved together in a single constraint solver run. (LP based solver for now in
the current patch, But can be any constraint solver) </p>
<p style="margin-top:0; margin-bottom:0"> </p>
<p style="margin-top:0; margin-bottom:0">Thanks,</p>
<p style="margin-top:0; margin-bottom:0">Yathi. </p>
<p style="margin-top:0; margin-bottom:0"> </p>
<p style="margin-top:0; margin-bottom:0"> </p>
<p style="margin-top:0; margin-bottom:0">------ Original message------</p>
<p style="margin-top:0; margin-bottom:0"><b>From: </b>Chris Friesen</p>
<p style="margin-top:0; margin-bottom:0"><b>Date: </b>Mon, 2/3/2014 11:24 AM</p>
<p style="margin-top:0; margin-bottom:0"><b>To: </b>openstack-dev@lists.openstack.org;</p>
<p style="margin-top:0; margin-bottom:0"><b>Subject:</b>Re: [openstack-dev] [Nova][Scheduler] Policy Based Scheduler and Solver Scheduler</p>
<p style="margin-top:0; margin-bottom:0"> </p>
</div>
</div>
<font size="2"><span style="font-size:10pt;">
<div class="PlainText">On 02/03/2014 12:28 PM, Khanh-Toan Tran wrote:<br>
<br>
> Another though would be the need for Instance Group API [1].<br>
> Currently users can only request multiple instances of the same<br>
> flavors. These requests do not need LP to solve, just placing<br>
> instances one by one is sufficient. Therefore we need this API so<br>
> that users can request instances of different flavors, with some<br>
> relations (constraints) among them. The advantage is that this logic<br>
> and API will help us add Cinder volumes with ease (not sure how the<br>
> Cinder-stackers think about it, though).<br>
<br>
I don't think that the instance group API actually helps here. (I think <br>
it's a good idea, just not directly related to this.)<br>
<br>
I think what we really want is the ability to specify an arbitrary list <br>
of instances (or other things) that you want to schedule, each of which <br>
may have different image/flavor, each of which may be part of an <br>
instance group, a specific network, have metadata which associates with <br>
a host aggregate, desire specific PCI passthrough devices, etc.<br>
<br>
An immediate user of something like this would be heat, since it would <br>
let them pass the whole stack to the scheduler in one API call. The <br>
scheduler could then take a more holistic view, possibly doing a better <br>
fitting job than if the instances are scheduled one-at-a-time.<br>
<br>
Chris<br>
<br>
_______________________________________________<br>
OpenStack-dev mailing list<br>
OpenStack-dev@lists.openstack.org<br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev">http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev</a><br>
</div>
</span></font>
</body>
</html>