Activity Mount Rules associate a Mount Policy to an activity regex.

When recalling a file, the users can specify an activity (i.e. by using
filepath?activity=x). If specified, this activity will be used to select
a matching activity mount rule, if one exists. If more than one Activity
Mount Rule matches the activity, the one with highest retrieve priority
will be chosen.

Acitivity Mount Rules take precedence over Requester Mount Rules.

Remove the looping through the retrieve queue jobs while holding the global lock in OStoreDB::fetchMountInfo.
This was done when a tape was disabled, since we mount disabled tapes if they have pending retrieve requests.
Instead we now mount the tape if the queue object info as in the mount policy map a mount policy whose name
starts with "repack".

With this change, cta-admin now forces repacks added with the --disabledtape to have a mount policy
prefixed with repack (without the --disabledtape flag, the mount policy can have any name)

Also Removed the criteria that a disabled/broken tape is mounted if the queue is filled with deleted
retrieved jobs. Eventually the maxrequestage for the queue will expire, the tape will be mounted
and the queue flushed

This revert is due to the fact that we will probably not put the
maxdrivesallowed in the mount policy object. We will put it in the
TAPE_POOL table and in the VIRTUAL_ORGANIZATION table

This reverts commit f48c6cc48eaa9ab9e77fff5a4537a7a4641896b6.

not given

cta-admin tape add does not take a capacity anymore

address on EOS

Removed diskInstance attiribute from the common::dataStructures::StorageClass class
Adapted unit tests
Adapted cta-admin commands

StorageClass now belongs to a VO (madatory)
Adapted unit tests
Modified cta-admin command to set the VO of a Storage Class

Deleted Schema version 1.2
Adapted tapepool management so that it works with the new VIRTUAL_ORGANIZATION table
Adapted unit tests so that a VO is created before a tapePool is created
Adapted prepare_test.sh so that it creates a VO before creating the TapePool

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

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.