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

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.

Changed 'catch (cta::exception::Exception ex)' to 'catch (cta::exception::Exception &ex)' in order to avoid error: catching polymorphic type ‘class cta::exception::Exception’

Changed 'catch (cta::exception::Exception ex)' to 'catch (cta::exception::Exception &ex)' in order to avoid error: catching polymorphic type ‘class cta::exception::Exception’ by value

Changed 'catch (exception::Exception ex)' to 'catch (exception::Exception &ex)' in order to avoid error: catching polymorphic type ‘class cta::exception::Exception’ by value

Status of repack retrieve request changed to RJS_Succeeded, started to insert the repack retrieve request into RetrieveQueueToReportToRepackForSuccess

Repack RetrieveRequest reported as success after mount and retrieve successful (expandRepackRequest)

(see 'ps -ax -o "pid comm cmd"  | grep /usr/bin/cta-taped').

of VO and Density"

Added MEDIA_TYPE and VENDOR columns to TAPE table and upgraded xrootd-ssi-protobuf-interface to v0.29

DataTransferSessionTapeFullMigration and DataTransferSessionTapeFullOnFlushMigration now count the first files archived to tape as opposed to relying on the values of the archive file IDs

Sub request support to be added.

Because ToReport queues need to construct RetrieveJob objects which are
not associated with a mount

The maintenance process replaces the garbage collector process. It now
runs both garbage collection and disk reports.

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.

This class will handle reporting like the GarbageCollector class
does for garbage collection.

Adapted the interface of scheduler and ArchiveRequests to allow delegating
reporting to the disk report runner.

This commit is not functionnal. We still need to:
- Implement the ToReport/Failed queues interface.
- Adapt the queueing in the scheduler/ArchiveMount
- Implement the popping of jobs to report.
- Implement the async reporter for the files.
- Develop the user interface for failed requests.

The tape write task not lister anymore to the memory manager for zero length files.

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

We now leave a placeholder on the tape and carry on in this case. The errors will eventually clear the
archive request.