Statically define the repo build concurrency

The repo build concurrency was pulling the processor core count and using
that int as the value for determining concurrent builds. Sadly,
this value can be high, low, or simply undefined and is entirely dependent
on the Ansible fact gathering system which has additional complexities and
dependencies based on how the hardware has represented the information.

Examples:
  * Should the value be low, 3 or less than, the build process would run
    serially making things painfully slow.
  * Should the value be high the build process may run too many tasks at
    one time causing general system instability.

This commit statically defines the concurrency level as "4" which is small
enough to support vagant, and minimal resource machines, while also being
performant enough to support large scale production clouds.

Change-Id: If2ad496c31c4d0092e7856c3deb07035ebc6c8b9
This commit is contained in:
Kevin Carter 2016-11-03 02:41:26 -05:00 committed by Kevin Carter (cloudnull)
parent 37e2b61ec5
commit 534f40f3dd
1 changed files with 1 additions and 1 deletions

View File

@ -76,7 +76,7 @@ repo_build_uca_enable: True
uca_apt_repo_url: "http://ubuntu-cloud.archive.canonical.com/ubuntu"
repo_build_timeout: 120
repo_build_concurrency: "{{ ansible_processor_count if ansible_processor_count > 0 else 5}}"
repo_build_concurrency: "{{ (((ansible_processor_vcpus|default(1)) | int) > 4) | ternary(8, 4) }}"
repo_build_venv_build_dir: "/tmp/openstack-venv-builder"
repo_build_venv_dir: "/var/www/repo/venvs"
repo_build_venv_pip_install_options: >