6663637374
The repo container's package cache causes quite a bit of confusion given that it's a 'hidden' feature which catches deployers off-guard when they already have their own cache configured. This is really the kind of service which people should manage outside of OSA. It also makes no sense if the deployer is using their own local mirror which is a fairly common practise. Adding to that, it seems that it is broken in bionic, causing massive delays in package installs. Finally, it also adds to quite a bit of complexity due to the fact that it's in a container - so in the playbooks prior to the container's existence we have to detect whether it's there and add/remove the config accordingly. Let's just remove it and let deployers managing their own caching infrastructure if they want it. Change-Id: I829b9cfa16fbd1f9f4d33b5943f1e46623e1b157
23 lines
920 B
YAML
23 lines
920 B
YAML
---
|
|
deprecations:
|
|
- |
|
|
The package cache on the repo server has been removed. If caching of
|
|
packages is desired, it should be setup outside of OpenStack-Ansible
|
|
and the variable ``lxc_container_cache_files`` (for LXC containers)
|
|
or ``nspawn_container_cache_files_from_host`` (for nspawn containers)
|
|
can be used to copy the appropriate host configuration from the host
|
|
into the containers on creation. Alternatively, environment variables
|
|
can be set to use the cache in the host /etc/environment file prior
|
|
to container creation, or the ``deployment_environment_variables``
|
|
can have the right variables set to use it. The following variables
|
|
have been removed.
|
|
|
|
* ``repo_pkg_cache_enabled``
|
|
* ``repo_pkg_cache_port``
|
|
* ``repo_pkg_cache_bind``
|
|
* ``repo_pkg_cache_dirname``
|
|
* ``repo_pkg_cache_dir``
|
|
* ``repo_pkg_cache_owner``
|
|
* ``repo_pkg_cache_group``
|
|
|