heat-engine and heat-api are deployed with number of workers=cores

[Sai Sindhur Malleni]

heat-engine and heat-api are deployed with number of workers=number of cores which leads to a large number of workers on machines with large core count. On a 56 core machine, 56 heat-api and 56 heat-engine workers are spawned which causes significant load on the database as each worker opens 10-15 connections to the database.

[OpenStack Infra (hudson-openstack)]

Fix proposed to branch: stable/ocata
Review: https://review.openstack.org/481232

[OpenStack Infra (hudson-openstack)]

Reviewed: https://review.openstack.org/481232
Committed: https://git.openstack.org/cgit/openstack/tripleo-heat-templates/commit/?id=0139f1e6f9a394f27743e546a59ac0b2208ebeaf
Submitter: Jenkins
Branch: stable/ocata

commit 0139f1e6f9a394f27743e546a59ac0b2208ebeaf
Author: Sai Sindhur Malleni <email address hidden>
Date: Thu Jul 6 16:54:22 2017 -0400

    Use conditional to set heat workers

    Heat is spawning number of workers equal to number of cores. This commit
    fixes the problem by using a conditional so that os_workers fact is used
    when the worker value is unset. This was changed in master in an
    unrelated commit
    https://github.com/openstack/tripleo-heat-templates/commit/aedb22be76be53716e30b60c93d323a3fbeb8f00
    However, the above commit cannot be cherry picked.

    Change-Id: I30b4ce6650c7f90d4a6bc96992baa201ce413fb8
    Closes-Bug: #1702761

[OpenStack Infra (hudson-openstack)]

This issue was fixed in the openstack/tripleo-heat-templates 6.2.3 release.

[Emilien Macchi (emilienm)]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (FUTURE, PIKE, QUEENS, ROCKY, STEIN).
  Valid example: CONFIRMED FOR: FUTURE