Naming scheme for repositories

[bedroge]

We have to come up with / agree on a naming scheme that we will use for our repository layout. Currently we only have

• cvmfs-config.eessi-hpc.org -> contains the config of all repositories and our eessi-hpc.org CVMFS "domain"
• pilot.eessi-hpc.org -> pilot repository for playing around with CVMFS, Easybuild, etc

In the future we will need at least repositories for production and development/testing, so it could be something like (as suggested by @boegel):

• prod.eessi-hpc.org (or perhaps soft(ware).eessi-hpc.org / repo.eessi-hpc.org)
• dev.eessi-hpc.org

More ideas are welcome!

[boegel]

I like pilot/prod/test (last one instead of dev).

soft(ware) is too generic for me (pilot and test also provide software).

It's probably worth proposing a specific naming scheme during the next meeting, and then take into account the feedback to make a final decision?

Ideally, we end up with something that makes it blatantely obvious which purpose each of the repos has (not sure if prod is clear enough with that in mind).

[rptaylor]

Having a good naming scheme always helps for comprehensibility. In terms of technical function, repo names are largely arbitrary - except when it comes to matching config files in domain.d/.

If you have separate stacks of servers for separate purposes (e.g. for prod, dev, maybe different servers with more storage that are intended for large data repositories, some other side project, etc) I strongly recommend using a subdomain for each stack.

I know you're focusing on just HPC software for now, but just as an example suppose you have separate servers for hosting data repos. Using names like genomics.data.eessi-hpc.org , images.data.eessi-hpc.org allows all the *.data.eessi-hpc.org repos hosted on the same servers to inherit the same config file domain.d/data.eessi-hpc.org.conf .

Or say if you have multiple kinds of testing repos that are all hosted on a group of "dev" servers, name them e.g. software.dev.eessi-hpc.org, test.dev.eessi-hpc.org, cvmfs-config.dev.eessi-hpc.org , so they match *.dev.eessi-hpc.org. Do not use dev.*.eessi-hpc.org or the config will be a mess.

If all your repos are going to be hosted on the same stack of servers, this doesn't matter (but it never hurts to plan ahead just in case).