The garbage collector now sets a flag on the agent object indicating garbage collection.
The process will immediately exit when detecting garbage collection.

The status of the repack request is updated throughout all its lifecycle (Pending, ToExpand, Starting, Running, Complete or failed)

Changed the reporting structures in the repack request to better handle repoting
(we will report one archive job per rearchived copy number, which is potentially
several per fSeq.

Created the getNextBatch() function for retrieve successes and partially implemented
the report function.

The retrieve requests now carry all the information necessary to create the archive jobs.
Retrive requests carry an isRepack boolean. The distinction between repack and non-repack behaviour
is pushed as low as possible in the api (in the object store) so that client code can be more
generic. For the same reason, the
The expand repack mode (re-creation of missing tape files) is not supported yet.
Changed the represenation of copy numbers to uint32 (as this is the smalled number supported but protocol buffers).
Added ArchiveRoute::StorageClassMap and ArchiveRoute::FullMap to store archive routing in memory.
Added repack buffer base URL support, and mechanism to compute temporary copy location in disk cache.
Fixed bug in ObjectOps<>::asyncInsert();
Inplemented the path generation for repack disk storage (<BaseURL>/<VID>/<FSeq (09%d)>).

Renamed some status (#447 issue)
Harmonized the name of the Archive and Retrieve queues in the cta.proto file and made the changes in the C++ code

Harmonized the copyNb type to uint32_t
Corrected a bug in RetrieveQueue::getContainerSummary() --> After insertion in the queue, the number of files and bytes added were equal to 0.

Queueing of Archive Jobs is done and unit tested
Queueing of Retrieve Requests is not completely done yet

Started to queue the ArchiveRequest for Repack

Removed the "User" message from the cta.proto (duplication of UserIdentity message)

Simplified protobuf schema.

Changed the status of succeeded retrieve requests as RJS_Succeeded and inserted them to the RetrieveQueueToReportToRepackForSuccess, unit tested but memory leak

Created subrequest pointer in RepackRequest serialization.
Created initial scheduler database repack request.
Removed duplicate function in Scheduler.

Merged RepackInfo and RepackType.
Simplifed RepackInfo to what is currently implemented.
Implmented repack related dumps.

Added partial support for repack queueing in scheduler database,
scheduler and CLI.

Changed the lifecycle of the ArchiveRequest to handle the various
combinations of several jobs and their respective success/failures.
Most notably, the request now holds a reportdecided boolan, which
is set when decing to report. This happens when failing to archive
one copy (first failure), or when all copies are transferred (success
for all copies).

Added support for in-mount retries. On falure, the job will be
requeued (with a chance to pick it up again) in the same session
if sane session retries are not exceeded. Otherwise, the job is
left owned by the session, to be picked up by the garbage collector
at tape unmount.

Made disk reporter generic, dealing with both success and failure.
Improved mount policy support fir queueing.

Expanded information avaible in popped element from archive queues.

Added optional parameters to ArchiveRequest::asyncUpdateJobOwner() to
cover various cases.

Updated the archive job statuses.

Clarified naming of functions (transfer/report failure instead of bare
\"failure\").

Updated garbage collector for new archive job statuses.

Added support for report retries and batch reporting in the scheduler
database.

Updated obsolete wording in MigrationReportPacker log messages and error
counts.

"ToTransfer" are to be picked up by tape sessions.
"ToReport" Includes both successes and failures to report, as the mechanism to report is the same.
   They will be handled by the reporter, which shares the single thread of the garbage collector.
"Failed" Will be a (possibly non-queue) container which will contain the failed requests. The operators
   will be able to examine, relaunch or abandon those requests.

The states and lifecycles of the requests have been reworked to reflect this lifecycle too.
The container algorithmes have been adapted to handle the multiple queue/container types.

We now have live (to be executed), failed and to be reported queues.
Archive jobs have all three types, retrieve jobs do not have a to be reported
queue. The RootEntry interface interface now provides the choice between the types.
All uses are currently hardcoded to LiveJobs.

The error(s) gets recorded at failure time, and the list is printed at
job deletion time.

Fixed various bugs detected through it.

Updated locking of ObjetOps in order to allow locking of sub-objects.
Make cta-objectstore-dump-object lockfree.

This will remove contention on the drive register as drives uipdate their statuses.
Also simplified structures in OStoreDB implementation (less references with added friend relations).

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).