Adding an indirection level in the directory structure to allow a

dedicated PV for quarkdb

continuousintegration/docker/ctafrontend/cc7/opt/run/bin/start_quarkdb.sh

 #!/bin/bash
 
+# I need 2 level of directories for quarkdb:
+# /var/lib/<possible PV mount point>/<directory owned by xrootd>
+# this way I can either use:
+# - a PV that mounts a dedicated SSD for long tests
+# - a directory in the container for shorter ones
+
 QUARKDB_CONFIG=/etc/config/eos/xrootd-quarkdb.cfg
 
-QUARKDB_DIRECTORY=$(cat ${QUARKDB_CONFIG} | grep redis.database | sed -e 's/.*redis.database\ \+//')
+QUARKDB_DIRECTORY=$(cat ${QUARKDB_CONFIG} | grep redis.database | sed -e 's/.*redis.database\ \+//;s%/\ *$%%')
+
+QUARKDB_SUBDIRECTORY=$(echo ${QUARKDB_DIRECTORY} | sed -e 's%/[^/]\+/*\ *$%%')
+
+# make sure the first level of directory exists if there is no mounted PV
+mkdir -p ${QUARKDB_SUBDIRECTORY}
 
 yum-config-manager --enable eos-quarkdb
 

continuousintegration/orchestration/eos-config-quarkdb.yaml

+apiVersion: v1
+kind: ConfigMap
+metadata:
+  name: eos-config
+  labels:
+    config: eos
+data:
+  xrd.cf.mgm: |
+    mgmofs.nslib /usr/lib64/libEosNsQuarkdb.so
+    mgmofs.qdbcluster localhost:7777
+  xrootd-quarkdb.cfg: |
+    xrd.port 7777
+    xrd.protocol redis:7777 /usr/lib64/libXrdQuarkDB.so
+    redis.mode standalone
+    redis.database /var/lib/quarkdb/quarkdb1