View Issue Details
|ID||Project||Category||View Status||Date Submitted||Last Update|
|0014910||Buildsys||Ci.centos.org Ecosystem Testing||public||2018-06-05 21:35||2018-06-06 03:13|
|Priority||normal||Severity||minor||Reproducibility||have not tried|
|Summary||0014910: Persistent volume for Cockpit in CentOS CI|
|Description||we've been trying on and off to move Cockpit's upstream CI away from our|
self-maintained OpenShift cluster/FedoraInCloud VMs towards an "official" CI
system. ci.centos.org seems appropriate for this.
A while ago, Stef started to investigate this, and tried to create a 100GiB
persistent volume "cockpit-images" that our test pods are supposed to use:
This has been pending for 5 months, so it's clearly not working. I put the
corresponding YAML below .
Are persistent volumes supported at all in CentOS CI? We really need one,
otherwise repeatedly downloading thousands of multi-GB test VM images ever day
would be a ridiculous resource waste. Perhaps the parameters are just wrong?
The guarantees for this don't need to be overly strong:
* Re-downloading or re-creating the images (in case of total loss) is
reasonably expensive, but doable. So this doesn't need to live on RAID or
gluster or anything rock-solid.
* ReadWriteOnce is sufficient, i. e. the volume does not (necessarily) need to
be shared/synced between different nodes. It's ok for every node to have its
own cockpit-images volume. That said, if it's possible or even easier to use
ReadWriteMany, i. e. share the volume between all nodes, that would increase
the test efficiency.
Do you have some insight here how to proceed with this?
|Additional Information||YAML used to create the volume:|
|Tags||No tags attached.|