6b1cfbe079
The cirros project has released new images, add them to our cache prior to actually using them in the CI. We can remove the old images once the migration is completed and not too many stable branches using the old images are still active, but comparing the size of these in relation to the total size of our images, the impact of this shouldn't be too large in comparison to the benefit in CI stability. Signed-off-by: Dr. Jens Harbott <harbott@osism.tech> Change-Id: I6d6bcc0e9cfef059de70bbb19e4254e8d29d415b |
||
---|---|---|
.. | ||
element-deps | ||
README.rst | ||
source-repository-dstat_graph | ||
source-repository-images | ||
source-repository-pip | ||
source-repository-stackviz | ||
source-repository-zanatacli |
cache-devstack
Pre-cache a range of things into CI images. This element uses the
source-repositories
element to acquire files to be cached.
The standard cache location is /opt/cache/files
.
A number of strategies are used to get the files to be cached.
We have a number of source-repository-*
files for each
package package that should be cached into images.
extra-data.d/55-cache-devstack-repos
goes through each
devstack branch and runs the tools/image_list.sh
script to
dynamically build a list of files to cache as requested by devstack.
This is mostly virtual machine images, but also some other peripheral
packages.