Site Decommissioning
Introduction
Some sites may stop CMS support and ask for decommissioning of their sites. To stop all transfer activities to/from this site, some checks&updates should be made.
Procedure
Ex site: T2_BR_UERJ
1)
Clean up of the Production samples
-
Step 1
Get all the samples registered to this site
-
Step 2
Check whether all samples have at least one custodial replica (2 for RAWs), also make sure that these replicas "complete" or at least have the same size with the site which will be decommissioned
-
Step 3
Submit deletion request for all samples
2)
Clean up of Debug samples
-
Step 4
Remove all LoadTest injections to/from the site
-
Step 5
Find all debug source&injection datasets and invalidate them
3)
Agents&Links&Central info
-
Step 6
ask site admin to stop all PhEDEx agents in all instances (deletion requests must be completed before stopping agents).
-
Step 7
Disable all site links in all PhEDEx instances
- use PhEDEx DDTLinksManage script to disable, not remove links with LinkRemove script just disable them (decided against suppressing links etc since that could affect any history that we store.)
- to get the links to/from the site:
-
Step 8
Rename the node names to XT2_BR_UERJ in all instances. (if it's T1, update both MSS and Buffer)
- update t_adm_node set name='XT2_BR_UERJ' where name='T2_BR_UERJ';
--
MericTaze - 2014-11-11