Steve Baker adb2121795 Make minimum default num_engine_workers>=4 ... Downstream test environments are frequently having failing stacks with error messages like: MessagingTimeout: resources[0]: Timed out waiting for a reply to message ID ... These environments generally have 1 or 2 cores, so only spawn one or two engine workers. This deadlocks with stacks that have many nested stacks due to engine->engine RPC calls. Even our own functional tests don't work reliably with less than 4 workers, and the workaround has been to set that explicitly in pre_test_hook.sh. This change sets the default minimum number of workers to 4, but still matches workers to cores for larger servers. This change also moves the default evaluation to heat.cmd.engine so that generated configuration doesn't get a inappropriate default value. Change-Id: Iae6b3956bad414406d901bb2213c9ec230ff4304 Closes-Bug: #1526045		2016-01-11 13:32:51 +13:00
..
__init__.py	Add a basic heat-manage	2013-05-27 21:06:31 +10:00
api.py	Fix [H405] pep rule in heat/cmd	2015-09-24 16:22:25 +03:00
api_cfn.py	Fix [H405] pep rule in heat/cmd	2015-09-24 16:22:25 +03:00
api_cloudwatch.py	Fix [H405] pep rule in heat/cmd	2015-09-24 16:22:25 +03:00
engine.py	Make minimum default num_engine_workers>=4	2016-01-11 13:32:51 +13:00
manage.py	Merge "Stop ignore skipped crypt_operation option"	2015-12-15 14:13:31 +00:00