Hi @Mwai,
A VO is a Virtual Organization. It represents a group of users working with the same data/experiment. So for us each LHC experiment (ATLAS, …), as well as small and medium sized experiments (AMS, NA62, …), gets its dedicated VO with the same name. We use VOs to enforce quotas, such as an experiment’s number of dedicated drives, as well as to gather usage statistics and summaries for each experiments.
Disk Instance is generally a different term for “EOSCTA instance”, the ‘small EOS’ instance used to archive/retrieve files from tape. A Disk Instance can have one or multiple VOs assigned to it. So for instance, we have a dedicated Disk Instance for each of the large LHC experiments (eosctaatlas, …) , and then also instances shared by the small/medium sized experiments (eosctapublic, eosctapublicdisk), based on their archival needs.
Does this clear it up a bit?
Cheers,
- Richard