<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><div><div apple-content-edited="true">Yuriy:<div><br></div><div><div><br></div></div></div><div><div>On May 3, 2012, at 4:46 AM, Yuriy Taraday wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div>Just note that since Essex release Nova by default use fill-first cost<br>function, meaning that nodes with less free RAM will be preferred for<br>new instances.<br><br>Kind regards, Yuriy.<br><br></div></blockquote><div><br></div><div>I thought the default behavior in essex was spread-first:</div><div><br></div><div>From: </div><div><br></div><div><a href="https://github.com/openstack/nova/blob/stable/essex/nova/scheduler/least_cost.py#L41">https://github.com/openstack/nova/blob/stable/essex/nova/scheduler/least_cost.py#L41</a></div><div><br></div><div> cfg.FloatOpt('compute_fill_first_cost_fn_weight',</div><div><div> default=-1.0,</div><div> help='How much weight to give the fill-first cost function. '</div><div> 'A negative value will reverse behavior: '</div><div> 'e.g. spread-first'),</div><div> ]</div><div><br></div></div><div><br></div><div><br></div><div><br></div><div><div>Take care,</div><div><br></div><div>Lorin</div><div>--</div><div>Lorin Hochstein</div><div>Lead Architect - Cloud Services</div><div>Nimbis Services, Inc.</div><div><a href="https://www.nimbisservices.com/">www.nimbisservices.com</a></div><div><br></div></div><div><br></div></div></div></div></body></html>