Mechanism to support multiple object stores

Problem to solve

We are moving into a setup were we will have two object stores one for normal operation and one for repack. Currently drives pick their work from one single object store. This poses a problem on swaping between the multi objectstore configuration.

Stakeholders

• CTA Team

Proposal

Configure both backends on process start through the config file. When scheduling, poll both of the objectstores keeping the same logic we have now.

This is not the way we are going to do it as this does not work for postgresql backed schedulerDB (this would work on both backends, even at the same time) as we will be managing which drive is servicing which backend, please refer to operations#1254 for the details.

Requirements

• Make the configuration file a required argument when launching cta-taped.

Side effects

The removal of the "static" cta-taped.conf file will also require changes from the following tools as they read some information from it:

• cta-tapelabel
• cta-readtp
• cta-admin