Repackage MVHTL with common CTA tape configuration

Needs to discuss with Vlado about a common configuration for the CTA tapes in MHVTL. This should replace the current configuration (that uses Oracle tapes) and provide a testing setup that matches more closely our production setup.

This can be configuration could be repackaged together with thew most recent version of MHVTL (1.7.0).

added Building and Packaging Continuous Integration + 1 deleted label

assigned to @jcamarer

added workflowIn Progress label and removed 1 deleted label

created branch 177-repackage-mvhtl-with-common-cta-tape-configuration to address this issue

marked this issue as related to cta-dependencies#2 (closed)

marked this issue as related to #233 (closed)

mentioned in merge request !146

More work needs to be done on this branch.

CTA/continuousintegration/buildtree_runner tools must work with both ULTRIUM and STK libraries: everything here is hardcoded for STK in ugly old scripts. Refactoring this is not funny and testing it worse.

cta-dependecies mhvtl packaged configuration is not compatible with CTA implementation as Vendor identification: MHVTL is not configured on the drives

Our CI scripts should be inspected too: STK is burnt in there too, replacing with burnt in ULT/LTO is not nice neither.

This is is quite a bit of work to just change a few strings with no functional impact on the software we deliver.

marked this issue as related to #257 (closed)

On the dev meeting of 13 Jan 2023, we decided to stick to STK until we can afford a full review and refactoring of all the tests and tools (CI, container generation, etc.) that have STK components hardcoded.

Ideally, we should decouple the MHVTL parameters used by these components from the place where they are used (for example by keeping them in a separate - and easily editable - json file),

added workflowBlocked label and removed workflowIn Progress label

changed milestone to %CI update push

This is blocked until MHVTL 1.7.0 is deployed on all runners (will come with Alma9 runners). Not a high priority task.

marked this issue as related to #283 (closed)

added mhVTL label

created branch 177-repackage-mvhtl-with-common-cta-tape-configuration-2 to address this issue

created branch 177-repackage-mvhtl-with-common-cta-tape-configuration-3 to address this issue

mentioned in merge request !375 (closed)

added 1 deleted label and removed workflowBlocked label

added prioritymedium label

assigned to @jleduc and unassigned @jcamarer

This issue is no longer blocked and we can move forward. The configuration of the virtual hardware has been, partially, decoupled from the RPMs installation/upgrade process. We should aim for a to have procedure, without changing the RPM, to change the underlying deployed virtual hardware, there are commands in mhvtl to generate config files according to some parameters and the the make_vtl_media to create the needed things from these config files.

To be more precise, this issue is no longer relevant as the mhvtl config should not be coupled with the RPM. That should be two different steps. Closing. And linking to the relevant CI ticket for this.

closed

mentioned in issue #868

assigned to @poliverc

unassigned @jleduc