<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; ">FWIW, I've opened <a href="https://bugs.launchpad.net/nova/+bug/1039065">https://bugs.launchpad.net/nova/+bug/1039065</a><br><div><div><br></div><div>I'll get my implementation into <a href="http://review.openstack.org">review.openstack.org</a>. </div><div><br></div><div>Regards,</div><div>Tom</div><div><br></div><div>On Aug 19, 2012, at 3:27 PM, Blake Yeager wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite">On Wed, Aug 15, 2012 at 10:14 AM, Tom Gall <span dir="ltr"><<a href="mailto:tom_gall@vnet.ibm.com" target="_blank">tom_gall@vnet.ibm.com</a>></span> wrote:<br><div class="gmail_quote"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
You have a scheduler hint where you want the scheduler to pick resources that are in close proximity to a particular ip address.<br>
<br>
ex:<br>
scheduler_hints': { 'cidr': '/32',<br>
'build_near_host_ip': affinity_ip}<br>
<br>
<time passes><br>
<br>
Now you migrate the instance to a different host. There are no hints since they weren't saved and unless the person issuing the migration command remembers the desire for affinity, it becomes a matter of luck if the affinity will be broken. To me this makes the case that if scheduler_hints are initially passed they should be saved, such that if there is a later migration the filter should be applied against the desired destination and if that destination doesn't pass the filter an error should be raised.<br>
<br></blockquote><div> </div><div>I completely agree this is an important use case that Nova needs to support. If this doesn't make it into Folsom we should push to get this into Grizzly as soon as possible.</div><div>
<br></div><div>-Blake</div></div><br>
_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></body></html>