On Oct 31, 2012, at 1:44 PM, Jonathan Proulx <j...@jonproulx.com> wrote:
> I'd only been pushing these options to the host the scheduler runs on, is it > that simple? I'm delight if I'm an an idiot and just need a few line in a > config file, but puzzled why this was (seemingly at least) working with > Essex, certainly my users didn't start screaming till I dropped Folsom on > them… Looking at the code it appears that the relevent info is being sent down to the compute node. That said I can't seem to repro your issue with even just the ram filter. I can't get it to overallocate on one node unless I specifically change the ratio, regardless of fill-first or spread-first. Vish _______________________________________________ Mailing list: https://launchpad.net/~openstack Post to : openstack@lists.launchpad.net Unsubscribe : https://launchpad.net/~openstack More help : https://help.launchpad.net/ListHelp
