A retry might sneak into the session (depending of end of sessions and reporting speeds).
Relaxed the test criteria for this case.

cta/CTA#296 Temporary disabled unit-test OStoreDBPlusMockSchedulerTestVFS/DataTransferSessionTest.DataTransferSessionMissingFilesMigration/0

This setup allows reproducing a but seen in system tests.

This is validated in a unit test.

The catalogue can receive polymorphic items as input for recording.
The strict sequencing of fSeqs is still enforced.
Currently, 2 items types are recorded: files and placehoders.
Files are recorded to the tape catalogue, while place holders are not,
but they are used to enforce the fSeq sequencing.

This version is not data safe as the request is created late, right after
referencing the job to the queue.

The top half goes as far as when the request is safe in the object store.
At that point, the bottom half is launched in a new thread, and success is returned
the called. This will enable lower latency for the users while retaining
the same data safety.

This version is experimental aas it spans an undetermined number of threads. A more controlled
version with a work queue should be implenented on the long run.

Moved maxTriesToConnect parameter to CatalogueFactory::create().

Done.

Adapted unit tests to validate this fetching.

Change RAO synchronization:
  * move all RAO operations right after mounting,
before the exection of any tape read task
  * while waiting for the tape to be mounted, the
ReacallTaskInjector fetches more tape read jobs
  * once the tape is mounted and the RecallTaskInjector
gets access to the drive performs RAO query for all queued
files
  * after performing RAO query for this files, RAO is deactivated

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

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

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

This patch extends RecallTaskInjector to perform a
Recommended Access Query to the tape drive to reorder
a set of jobs. This patch also adds a unit test for the
newly added RAO functionality

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

The VFS implementation only launches the operation in the background (via std::async).
The Rados implementation uses the aio features of Rados. Lock and update are launched in the background via std::async.
Also now uses override for Backend virtual function.

Done.

Created a garbage collector subprocess for the drive daemon.
Created a AgentHeartbeat thread and added it to frontend, drive subprocess and GC subprocess.
Fixed logs and drive subprocess.
Renamed common/threading/Threading.[hc]pp to Thread.[hc]pp as there is only one class left in this file.

Work for issue #65 EOS+CTA interface definition and implementation

Removed DataTransferSessionEmptyOnVolReq unit test which now locks (sessions now loop until they schedule).

Added drive status reporting in scheduler
Added drive status reporting in OStoreDB
Added support for drive status listing in the front end
Removed virtual functions from the Scheduler, which is never overloaded.
Added DesiredDriveState structure to drive state.
Removed usage of duplicate MountType, DriveStatus and DriveState structures.
Created DriveInfo structure to allow recreation of drive register entry in all
reporting situation (potentially with partial/assumed info).