<html><body><span style="font-family:Verdana; color:#000000; font-size:10pt;"><div>Good stuff. Couple of questions:</div><div><br></div><div>a) Looks like one of the major drivers is the rules based scheduling - mutual exclusion, temporal and spatial rules, and so forth. Is there an existing way to capture these placement pragmas ? Or should we have a light rules framework ? <br></div><div><br></div><div>b) Saw your note "<i>I am looking for a way to define these attributes in a single place that
is importable from both the scheduler and compute services, so that the
compute node can read in these attributes and post their values to its
ZoneManager, and the scheduler service can do the same. The details of
this remain to be worked out.</i>" </div><div> This might be a good time to introduce the concept of distributed cmDb that has the run time configurations. </div><div><br></div><div>c) Do we have a blueprint yet ? Would be happy to contribute ... </div><div><br></div><div>Cheers</div><div><k/><br></div>
<blockquote id="replyBlockquote" webmail="1" style="border-left: 2px solid blue; margin-left: 8px; padding-left: 8px; font-size: 10pt; color: black; font-family: verdana;">
<div id="wmQuoteWrapper">
-------- Original Message --------<br>
Subject: [Openstack] DIstributed Scheduler blueprint update<br>
From: Ed Leafe <<a href="mailto:ed@leafe.com">ed@leafe.com</a>><br>
Date: Thu, March 10, 2011 8:06 am<br>
To: Openstack <<a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a>><br>
<br>
I've updated the specification for the Distributed Scheduler blueprint to include details of the proposed implementation. Up until now it hasn't been possible to provide any detail, since this depended on the implementation of the changes for multi-cluster/zones. Now that Sandy has made some progress, we've discussed an approach we think will work, and so I've written it out in as much detail as I could here:<br>
<br>
<a href="http://wiki.openstack.org/DistributedScheduler">http://wiki.openstack.org/DistributedScheduler</a><br>
<br>
The only change is the "Implementation" section of that page. Please review that, and let me know if either something isn't clear, or if something could be improved. I will at PyCon for the next few days, so I won't be continuously available to respond, but I will when I have the chance.<br>
<br>
<br>
<br>
-- Ed Leafe<br>
<br>
<br>
<br>
<br>
_______________________________________________<br>
Mailing list: <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
Post to : <a href="mailto:openstack@lists.launchpad.net">openstack@lists.launchpad.net</a><br>
Unsubscribe : <a href="https://launchpad.net/~openstack">https://launchpad.net/~openstack</a><br>
More help : <a href="https://help.launchpad.net/ListHelp">https://help.launchpad.net/ListHelp</a><br>
</div>
</blockquote></span></body></html>