[openstack-dev] [infra] [gate] [all] openstack services footprint lead to oom-kill in the gate

Paul Belanger pabelanger at redhat.com
Sat Feb 4 14:47:08 UTC 2017

On Fri, Feb 03, 2017 at 06:14:01PM +0000, Jeremy Stanley wrote:
> On 2017-02-03 11:12:04 +0100 (+0100), Miguel Angel Ajo Pelayo wrote:
> [...]
> > So, would it be realistic to bump the flavors RAM to favor our stability in
> > the short term? (considering that the less amount of workload our clouds
> > will be able to take is fewer, but the failure rate will also be fewer, so
> > the rechecks will be reduced).
> It's an option of last resort, I think. The next consistent flavor
> up in most of the providers donating resources is double the one
> we're using (which is a fairly typical pattern in public clouds). As
> aggregate memory constraints are our primary quota limit, this would
> effectively halve our current job capacity.
I completely agree. Halving our quote limit to address the issue of increases
memory consumption seems like the wrong approach.

More information about the OpenStack-dev mailing list