<html><head><meta http-equiv="Content-Type" content="text/html charset=windows-1252"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div><br></div><div><div>On Jan 16, 2013, at 11:22 AM, "Day, Phil" <<a href="mailto:philip.day@hp.com">philip.day@hp.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><div lang="EN-GB" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">Hi Folks,<o:p></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">In working with the Filter Scheduler we’ve come with a couple of ideas on enhancement to make the final host selection stage configurable. Whilst its sometimes fine to just pick the first host from the list of weighted hosts, the more general case is that I’d like to be able to have the scheduler pick one of the first N hosts on the weighted list. The specific use cases that I have in mind are:</div></div></div></blockquote><blockquote type="cite"><div lang="EN-GB" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "> <o:p></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">i) On a large system there is very rarely a single ideal / optimal host for a particular instance to be placed on. In practice any of the N most </div></div></div></blockquote>[…]</div><div><br></div><div>Hey cool, I actually have a patch for picking at random from the top N hosts as well, but I haven't gotten around to proposing it. :) Consider that as support for the idea. ;) Not sure I like the implementation, but I can comment on that in the review.</div><div><br></div><div><blockquote type="cite"><div lang="EN-GB" link="blue" vlink="purple"><div class="WordSection1" style="page: WordSection1; "><div style="margin: 0cm 0cm 0.0001pt 18pt; font-size: 11pt; font-family: Calibri, sans-serif; "><o:p> </o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; ">ii) The second idea is that when creating M instances in one request we could randomly select M hosts out of the first N hosts in the list (since these have all been filtered as being suitable) which would save having to iterate through the filter / weighting functions for each successive instance. Haven’t done any coding for this yet, but would appreciate thoughts.<o:p></o:p></div><div style="margin: 0cm 0cm 0.0001pt; font-size: 11pt; font-family: Calibri, sans-serif; "></div></div></div></blockquote><div><br></div><div>You don't need to re-filter the whole list of hosts. However, you do need to re-filter the host that has been chosen on every pass. It may have only been suitable for 1 instance.</div><div><br></div><div>- Chris</div><div><br></div></div></body></html>