The rollout is planned in phases. When a gateway is added to the redirector alias (managed by echo manager), it is put in the cmsd sandbox.
...
Current status
xrootd | webdav | cmsd | |
---|---|---|---|
yes | no | passive | |
gw4 | |||
gw5 | |||
gw6 | |||
gw7 | |||
gw14 | |||
gw15 | |||
gw16 | |||
svc01 | |||
svc02 | |||
svc97 | |||
svc98 | |||
svc99 | |||
rdr |
Phase 1
Single active gateway in the cmsd cluster, manager01 gets added to the xrootd alias . This substitutes gw14 in the xrootd and webdav aliases and ensures correctness of the initial change. any protocol/cmsd interaction unexpected behaviour should be caught here. Load behaviour and overheads should also become apparent.
...
For small scale testing, add additional gws to rdr, this is to test small scale load balancing. having 2 gateways might lead to instabilities (load ping-pong or fallback to single gw in case the other is loaded). The gateways are from different generations to evaluate impact on each. gws are kept within the xrootd/webdav aliases to evaluate the impact of cross-alias requests and for quick rollback capability. VOs/VO reps switch a part of the transfers to the rdr aliasAtlas sends some transfer to rdr
xrootd | webdav | cmsd | |
---|---|---|---|
yes | no | passive | |
gw4 | |||
gw5 | |||
gw6 | |||
gw7 | |||
gw14 | |||
gw15 | |||
gw16 | |||
svc01 | |||
svc02 | |||
svc97 | |||
svc98 | |||
svc99 | |||
rdr |
...
All gws are added to rdr and VOs switch all/most traffic to the rdr aliasone by one
xrootd | webdav | cmsd | |
---|---|---|---|
yes | no | passive | |
gw4 | |||
gw5 | |||
gw6 | |||
gw7 | |||
gw14 | |||
gw15 | |||
gw16 | |||
svc01 | |||
svc02 | |||
svc97 | |||
svc98 | |||
svc99 | |||
rdr |
...