Update description of our testing environment

In particular be more specific about us not mirroring certain sites like
PyPi, but just cache accesses.

Signed-off-by: Dr. Jens Harbott <harbott@osism.tech>
Change-Id: I3fc4856b39a4561450b666cb9c381814cd0dd9a3
This commit is contained in:
Dr. Jens Harbott 2021-11-03 12:00:44 +01:00
parent 735e66ee78
commit b303896a75
1 changed files with 4 additions and 3 deletions

View File

@ -46,12 +46,13 @@ Each single use VM has these attributes which you can count on:
Generally you will want to write large things to /opt to take
advantage of available disk.
* Swap is not guaranteed to be present. Some clouds give us swap and
others do not. Some tests (like devstack-gate based tests) will create
others do not. Some tests (like devstack based tests) will create
swap either using a second disk device if available or by using a
file otherwise. Be aware you may need to create swap if you need it.
* Filesystems are ext4. If you need other filesystems you can create
them on files mounted via loop devices.
* Package mirrors for PyPi, NPM, Ubuntu, Debian, and Centos 7 (including
* Package mirrors and/or caches for PyPi, NPM, Ubuntu, Debian, Fedora
and Centos (including
EPEL) are provided and preconfigured on these instances before starting
any jobs. We also have mirrors for Ceph and Ubuntu Cloud Archive that
jobs must opt into using (details for these are written to disk on the
@ -62,7 +63,7 @@ root access to them. This means you can install system packages, modify
partition tables, and so on. Note that if you reboot the test instances
you will need to restart the zuul-console process.
If jobs need to perform privileged actions they can do so using Zuul v3's
If jobs need to perform privileged actions they can do so using Zuul's
secrets. Things like AFS access tokens or dockerhub credentials can
be stored in Zuul secrets then used by jobs to perform privileged
actions requiring this data. Please refer to the Zuul documentation