instack-undercloud/elements
Alex Schultz ee5f25a726 Tune number of workers for undercloud
By default many services use the number of cpus as the default number of
workers.  On baremetal systems this can lead to excessive RAM
comsumption as this can be 16, 32, 48 or higher for each of the
services. In the upstream puppet openstack, a fact was created as part
of the Newton cycle that is the larger value between (number of cpus/4)
or 2 but is capped at 8. These defaults have not been updated yet in the
upstream modules and it would be better to specifically call out the
worker configurations in our puppet-stack-config.yaml template.

This change updates the worker settings for the classes that are pulled
in for the undercloud to leverage this tuned fact to lower the overall
number of workers for all the services.  This should improve memory
consumption and reduce the number of processes running on baremetal
systems. The os_workers fact will be 2 for unless the cpu count is
greater than 8 with an incremental increase of 1 worker for every 4
processors until 32 processors.  Anything above 32 processors will still
result in a worker value of 8.

This change updates 17 services that currently may use the number of
processors for the default number of workers.

Change-Id: I9ed855648e23b0a7e452e6a840a92779fa3f6d48
Closes-Bug: #1633544
2016-10-14 11:01:53 -06:00
..
centos-cr Add element for CentOS CR repo 2015-03-26 17:00:38 -05:00
instack-vm Add dib-lint to pep8 tox job 2016-05-04 16:58:07 +00:00
isolated-build Add isolated-build element 2014-11-21 16:46:57 -06:00
overcloud-full Force rebuild of ramdisk as part of overcloud-full 2016-03-28 21:29:27 +00:00
pip-and-virtualenv-override Restore pip-and-virtualenv-override 2016-05-23 11:50:17 -04:00
puppet-stack-config Tune number of workers for undercloud 2016-10-14 11:01:53 -06:00
undercloud-install Revert "Stop pinning Glance API version on stackrc" 2016-10-06 16:26:29 +00:00