Command will remove drive or drives by regex from the drive register.
The drives must be in state Down unless --force option is set.
Usage: rm <drive_name> [--force/-f]

If there is any active tapeserver with this drive it will create the
entry in the drive register again with Down status.

Example of the usage:
  cta drive rm ^VDSTK
  Drive VDSTK41 in state Free and force is not set (skipped).
  Drive VDSTK42 removed.

This would detect instances where rados reports an object deletion before is actually happens.

These two message types were incorrectly removed by the
following commit back in 2016:

commit 78883f16
Author: Eric Cano <Eric.Cano@cern.ch>
Date:   Wed Aug 24 14:47:06 2016 +0200

    Moved and renamed TapeserverProxy class as TapedProxy.

    Added new functions allowing representation of the full life cycle of the tape sessions.
    Phased out the first old function (gotArchiveJobFromCTA).
    Removed some dead code.

The log for unlock appeared way after the action happened, and subsequent locks appeared as
in violation of the lock (at first sight).

The value was 10 minutes instead of 1. This value was too high as this represents the load time
of the drive, which is rather fast. Also it was misaligned with the mount to transfer state transition
timeout, which led to some sessions being killed instead of failing by themselves.

Without this index we got errors like:

[root@p06253947b39467 ~]# cta af ls --instance cta --path /eos/dev/test/gcancio/10072017/file_2167
Failed to execute the command. Reason: Failed to open root://10.16.135.81:10955//Y3Rh&YWY=&bHM=&LS1pbnN0YW5jZQ==&Y3Rh&LS1wYXRo&L2Vvcy9kZXYvdGVzdC9nY2FuY2lvLzEwMDcyMDE3L2ZpbGVfMjE2Nw==: [ERROR] Operation expired
[root@p06253947b39467 ~]#

With this index we execute the same query in less than a second:

[root@p06253947b39467 ~]# time cta af ls --instance cta --path /eos/dev/test/gcancio/10072017/file_2167
 289440       1  I20170    1381    51096      cta   18965         1006       ADLER32     0XFBA23F1D    german_raw  gcancio       c3    1499697578 /eos/dev/test/gcancio/10072017/file_2167

real    0m0.590s
user    0m0.005s
sys    0m0.006s
[root@p06253947b39467 ~]#

The updating of statistic in the objecttore (in drive register) could wait for a lock
for so long that the session get killed due to a heatbeat timeout.

To avoid this, we use lockfree access as much as possible, and when locking it srequired, do it with a
timeout.

The timeout will be logged as a warning.

Added timeouts to synchronous locking primitives in the object store backends to implement this feature.

Fixed a bug where the VFS backend always used exclusive locks.

Rao branch

See merge request !3

This completes the dispatcher logic in the frontend

avoid file metadata resolution on eos side.

when SSI is not used.

The probe state is also used. It represents the time when the drive is being checked
for tapes during the down to up transition.

Shutdown is not in use yet as it requires changing the behaviour of the system (clean shutdowns).

We now automatically find all binaries to symlink into /usr/bin of containers.

Changes dispatcher back to using a switch statement for the EOS commands
for easier static analysis.

Generating backtrace automatically when ctafrontend dies, collect it for artifacts and display it when the namespace gets deleted so that it appears on the Pipeline.

For the admin functions, it is very clunky to map <cmd,subcmd> pairs to
which function to call using nested switches. Instead we lookup which
function to call in a static const map of <cmd,subcmd> to method function
pointers. Now new commands can be added or old ones removed by editing a
single line in the map definition.

and 1 hour by default.
Previously when cta frontend coredumped, all the files appeared to have
been successfully deleted when it was not the case.
I am now making sure cta client returned with no error to correctly
detect failures.

This will give faster feedback to the operators as they put drives up.
The scheduling can sometimes take a long time and the status update only happened after that.

This is necessary after a system restart if the api server's IP address changed.

sqplus is needed to clean up the database.