Metadata can be used for short replies (less overhead than a full reply)
or to provide information about the reply which will follow (e.g. number
of records, response size, etc.)

Alerts can be used to signal the client about the server state.

Created an objectstore utility cleaning up the root entry after deleting archive or retrieve queues.

This utility is to be used for cleaning up the pre-prod environement following a schema change in the archive queues.

Protobufs for different message types will now be handled by template
specialization

Like in ArchiveQueue, added per file cache of parameters, summary rebuilds and rebuild count.

If not, eos would refuse to use the space after finding the .eosfsid file.

Fixed missing decrement of size total when dequeueing ArchiveRequest.

Changed ArchiveQueue's schema in object store so the per-job values are cached locally in the queue.
Added a sanity check on commit() so the summary are rebuilt if incoherent.

This object (with thread) already reports data movement to the main process, and will
also store it in the object store (interface will be added to TapeMount.

Returned some formatting to the output of the "cta archivefile ls" command

Changed the type of the ListArchiveFilesCmd::m_readBuffer
member-variable from std::string to std::ostringstream. This
modification will make it much easier to add output
formatting for the "cta archivefile ls" command in the
future.

Moved the path column of the output of the "cta archivefile ls"
command to the very end of the line.  This was done because the
path column is the only real random width column.

The "cta af ls" command now sends several rows back to the client
in a single reply.

Set the header colour of the "cta af ls -h" command back to red

Everything is now merged in the standard `ctafrontend` docker tree completely removing file duplication.

The clean solution would have been to add cta to the `tape` group.
Unfortunately this does not work as groups are not refreshed within a bash process.
Therefore the short answer was to `chmod 666` SCSI devices (`sg` `st` and `nst`).
Now everything works fine in buildtree but this step could be improved.

Creating /var/log/cta as well because it is needed by taped.

added a /CANSTART file so that eos waits for all keys to be OK before starting.
/bin/sh -> /bin/bash to allow function names with `-`...
yum and yum-config-manager overridden when in BUILDTREE environment
ctafrontend not booting needs further work

First version of a streaming "cta archivefile ls" command.

when I modified it to read results back in a
"read until end of file" loop.

The bug was that instead of trying to read 1 KiB chunks of data
from the cta front-end, the chunk size was only 8 bytes (the size
of 64-bit pointer).  The calculation of the chunk size was
incorrectly:

   sizeof(buf - 1)

instead of:

   sizeof(buf) - 1

This branch is a workaround as buildtree runner does not work in master.

Typicaly updated every few seconds.