This can now be done without tearing down and re-creating the containers.

Add standalone command line tool cta-tape-label.

Command mount, label, umount the tape pointed by VID option. Tape drive
and library parameters used from /etc/cta/TPCONFIG file and catalogue
parameters from /etc/cta/cta-catalogue.conf.
To be labelled the tape must be present in the catalogue and must be
empty.
By default the tool labels the tape with enabled logical block protection
if drive supports such mode. For non-blank tapes command checks previous tape
label and label only if the old label is the same or match to the label in the
command line oldLabel option. To skip label checks for non-blank tapes --force
option could be used.

tapes

Add read-only tape flag support in the catalogue for the TAPE table.
Add RdbmsCatalogue::setTapeReadOnly method to modify this flag with
  "cta-admin tape ch" command.
Add RdbmsCatalogue::setTapeReadOnlyOnError to set this flag from taped.
Add support for rdonly flag listing for "cta-admin tape ls" and
  "cta-admin sq" command.

all containers.
Many failures were due to slow DNS name resolution by kube-dns.
To solve this I am now scanning all registered services in the namespace
and adding entries to /etc/hosts on all the `Running` containers in the
namespace. This solution is valid for both systemd and non-systemd
containers.

Added MEDIA_TYPE and VENDOR columns to TAPE table and upgraded xrootd-ssi-protobuf-interface to v0.29

Done

Now use -m for comments not -c.

Also fixes some typos.

If CI passes...

and generating all the required krb5 keytabs

adding all the missing bits to allow the simple systemtest to run on the client pod:
- add user `daemon` to sudoer in eos so that we can xrdfs prepare as a `powerusers` user
- add the `powerusers` group mount rule in cta
- add the missing bits in client_test.sh

to allow all users with ctausers as their primary group to mount tapes. the uid-gid mapping is performed by the mgm

2 tapeservers are now available: tpsrv01 and tpsrv02.
systest.sh only put tpsrv01 up and perform the basic test on 1 drive only.

Removed the "--encryptionkey" option from "cta tape add"

Now `run_systemtest.sh` can be used standalone, outside of CI environment.

Waiting for library configuration. If missing it leads to failed test: no drive tape or library available...