Dedicated cvmfs repositories for DUNEDAQ, and use of development cvmfs repo

Original request to cvmfs system admins:

We would like to request the following two repos for hosting DUNE DAQ software suite:

dunedaq.opensciencegrid.org dunedaq-development.opensciencegrid.org

We would use the development repository to host nightly releases and other things which may be deleted/overwritten often. This would be a repo requires more frequent garbage collection.

At the moment, we shared the repo with DUNE Offline, but the DUNE DAQ software suite is growing rapidly. With the nightly releases coming up soon, it's best to have dedicated repos for the DAQ world.

This will also give us flexibility in the future in case we plan to use cvmfs for online DAQ production use. In such case, the DAQ software suite will be self-contained in the repos without unnecessary files from offline.

Running garbage collection on the publisher node

To run garbage collection on the development repo, use cvmfs_server gc <repo name>.

It is recommended to run the garbage collection on the dev repo at least once every 10 days.

Proposed new layout of files

The current DUNE DAQ repo (under /cvmfs/dune.opensciencegrid.org/dunedaq) has the following layout:

dunedaq
├── DUNE
│   ├── products
│   ├── products_dev
│   ├── releases
│   └── sandbox
└── protoDUNE
    ├── products
    └── products_dev

8 directories, 0 files

With the creation of the two DAQ-dedicated repos, we plan to have the following layout:

dune.opensciencegrid.org

Keep current files existed but "frozen" to maintain backward compatibility for developers;
DUNE will be copied but separated over to the two new repos (details below);
protoDUNE will not be migrated to the two new repos.

dunedaq.opensciengrid.org

products (from DUNE/products)
releases (from DUNE/releases)
pypi-repo (from DUNE/sandbox/pypi-repo)
other things out of the sandbox directory once they become mature

dunedaq-development.opensciencegrid.org

products (from DUNE/products_dev)
nightly (from DUNE/sandbox/nightly), alternatively, we can rename it to releases, and produce releases using date as names, as oppose to the current choice of using weekday names. This will give us flexibility to retain as many nightly releases as we want, and reduce ambiguity of release names;
sandbox for other things left in DUNE/sandbox

DUNE-DAQ / daq-release