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 |
||
|---|---|---|
| .. | ||
| main.yml | ||
| repo_install.yml | ||
| repo_key_distribute.yml | ||
| repo_key_populate.yml | ||
| repo_post_install.yml | ||
| repo_pre_install.yml | ||
| repo_sync_manager.yml | ||