We currently have two issues with venvs:
- if you update your venv on the repo server, it is not possible for
that updated venv to land on the service's container as the get_url
task always skips if the file exists (even if the file is different)
- if you have an updated venv on the repo server and forcefully delete
the cached venv tarball on the service's container, the new tarball
will get unarchived over top of the existing venv
This commit does the following:
- gets the checksum of the /var/cache tarball and downloads checksum
file from repo server
- updates "Attempt venv download" to only download the venv if the
cache doesn't exist or if the local and remote checksums differ
- adds a "force: true" to "Attempt venv download" task so that the venv
tarball will get re-downloaded when the when condition is true (this
is necessary otherwise the download will get skipped since the
destination already exists)
- adds a new task "Remove existing venv" so we can first remove the
venv before we unarchive the potentially new venv from the repo
server
- updates "Create neutron venv dir" and "Unarchive pre-built venv"
tasks to only proceed if "neutron_get_venv | changed", which
prevents these tasks from running when they the venv tarball hasn't
changed
- adds multiple service restarts to
os_neutron/tasks/neutron_install.yml so that neutron will restart
correctly should the venv/packages update without any associated
config changes
NOTE: The reason why we compare local and remote checksum is to avoid
unnecessarily downloading the venv when the checksums are in fact
the same. On small deploys this is more or less a non-issue but
if a deploy w/ thousands of compute nodes re-runs playbooks we
want to limit the venv downloads when it's unnecessary.
Change-Id: Ie0ba2956e5bf90cec6615171b50a2397c7624257
The pip install tasks were distributed into many files with no clear
benefit from doing so. This patch consolidates the pip install tasks
to ensure that they are all handled together, are all installed into
the appropriate venv, and all use the right constraints.
Change-Id: I8bad68c57c0ffa986817aa80d79e9d2ab4b86a3d
This commit adds the ability to install Ironic without requiring an
OpenStack-Ansible pip wheel repository.
In 'developer mode' the git source is cloned directly and the services
are installed directly from the git clone with its requirements being
installed from pypi. The OpenStack upper-constraints file is also used
to ensure that the install is executed using the appropriately tested
set of pypi packages.
Change-Id: I38f6b0796fa2bb647e51194907274d9ca6cfb585
