Using a dump tool and jq, the objectstore can be easily explored.
This README.md presents the methods.

add declaration of the fully specialised getElementSummary() method
for archive queues

During the July datachallenge the archiveJobTransferForUser queue for the r_atlas_test_datachallenge
tapepool became full of ArchiveJobs whose bytes field became zero after popped from the queue.
This caused the tape servers to pop ~5TB of work from the queue. To prevent this from happening in
the future, instead of summing the sizes of the individual elements popped from the queue, we now
subtract them from the total size popped. This way, if there are popped jobs that have incorrectly
set their bytes field to zero, the algorithm will consume less data than expected, not exponencially
more

Remove the looping through the retrieve queue jobs while holding the global lock in OStoreDB::fetchMountInfo.
This was done when a tape was disabled, since we mount disabled tapes if they have pending retrieve requests.
Instead we now mount the tape if the queue object info as in the mount policy map a mount policy whose name
starts with "repack".

With this change, cta-admin now forces repacks added with the --disabledtape to have a mount policy
prefixed with repack (without the --disabledtape flag, the mount policy can have any name)

Also Removed the criteria that a disabled/broken tape is mounted if the queue is filled with deleted
retrieved jobs. Eventually the maxrequestage for the queue will expire, the tape will be mounted
and the queue flushed

CTA frontend now logs the following configuration values at startup

* cta.catalogue.numberofconnections
* cta.objectstore.backendpath
* cta.schedulerdb.numberofthreads
* cta.archivefile.max_size_gb
* cta.repack.repack_buffer_url
* cta.ns.config

Made the dotted line surrounding the wrapper::rdbms classes within cta_rdbms_class_diagram.svg more visible

* Add clientHost to the cta::common::dataStructures::SecurityIdentity struct, defining the machine the cta command was submitted from
* cta::comon::dataStructures::SecurityIdentity::host now represents the frontend machine the commands were executed on, and is set by the server