Compile switches now applied to each target separately, cta_admin has
instrumentation switched off.

Rao branch

See merge request !4

If the whole contents of the ARCHIVE_FILE and TAPE_FILE tables are
listed without a search criteria and with an ORDER BY clause then the
first row back from the database will take a relatively long period of
time to be returned.  This is because the database will have to sort
every row before returning the first.  This long period of time will
cause the current (non SSI) cta command-line tool to time out.

The installation in the buildtree environment is not useful as all is pre-installed in the image.

Changed default location of cta-taped config file within the cta-taped command-line arguments to /etc/cta/cta-taped.conf

View the binary contents of the Protobuf received on the client side to
debug ParseFromArray() error

Also outputs stderr on success as well as failure

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 bedf9832
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 ~]#

Signed-off-by: Cristina Moraru <cristina-gabriela.moraru@cern.ch>