From c8dd370a5e2b7eacd2f5a8eb0393836302010722 Mon Sep 17 00:00:00 2001 From: Timothy Noble Date: Thu, 12 Dec 2024 14:44:12 +0000 Subject: [PATCH] Update docs/operator/multi_vo_rucio.md Co-authored-by: Riccardo Di Maio <35903974+rdimaio@users.noreply.github.com> --- docs/operator/multi_vo_rucio.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/operator/multi_vo_rucio.md b/docs/operator/multi_vo_rucio.md index a49fb04299..d9234f227c 100644 --- a/docs/operator/multi_vo_rucio.md +++ b/docs/operator/multi_vo_rucio.md @@ -8,7 +8,7 @@ Multi-VO Rucio configuration allows a single instance of Rucio to support multiple experiments or Virtual Organisations (VOs). Multi-VO Rucio are run by a "super_root" which administers the Rucio instance, creating VOs within Rucio, each VO is then administered by VO specific "root" accounts created with the VO -that deal with the VO requirements and needs. Each VO use Rucio as a normal or +that deal with the VO requirements and needs. Each VO uses Rucio as a normal or "Single-VO" instance, meaning a Rucio instance can transition to support more VOs without significant disruption. Each VO's accounts, scopes and RSEs are associated with their VO which ensures all rules and replicas are kept separate