Use the same wheel path as the repo_build

Once we remove the repo build process, this needs to point
to the location where wheels are served by pypiserver.

For now we use this to ensure that we don't rebuild the wheels
that were already built by the repo build process. It has also
been found that pypiserver hangs when it encounters duplicated
wheels.

Change-Id: I86510cb7407e4ee69a376fc64ba5b8f5676f0bff
This commit is contained in:
Jesse Pretorius 2018-09-02 16:01:38 +01:00
parent 2e3af35ee6
commit 381f3ffba2
1 changed files with 9 additions and 1 deletions

View File

@ -77,7 +77,15 @@ venv_build_host_venv_path: "/openstack/venvs/wheel-builder"
# The path where the wheels are cached on the build host
# for speeding up the build process.
venv_build_host_wheel_path: "{{ repo_pypiserver_package_path | default('/var/www/repo/pools') }}"
# TODO(odyssey4me):
# Once we remove the repo build process, this needs to point
# to the location where wheels are served by pypiserver.
# For now we use this to ensure that we don't rebuild the wheels
# that were already built by the repo build process. It has also
# been found that pypiserver hangs when it encounters duplicated
# wheels.
venv_build_host_wheel_path: >-
/var/www/repo/os-releases/{{ openstack_release | default('master') }}/{{ (ansible_distribution | lower) | replace(' ', '_') }}-{{ ansible_distribution_version.split('.')[:2] | join('.') }}-{{ ansible_architecture | lower }}
# The facts to set when the venv changes during a
# build, or the installation of a venv.