Manual steps in the configuration of some nodes to remove a VO

Removing a VO implies reconfiguration of the site removing the VO related variables from the site-info.def file. When removing a VO, YAIM doesn't perform some actions that sysadmin consider necessary and currently need to be done manually. AEGIS01-PHY-SCL, EGEE SEE ROC and SEE-GRID have prepared the following list of manual steps after their experience removing a VO.

On service nodes (CE/UI, gCE, SE_classic, RB, WMSLB):

1. To remove pool accounts from /etc/passwd, /etc/shadow, /etc/group and /etc/gshadow
2. To remove pool account entries from /etc/grid-security/gridmpadir
3. To remove pool account home directories
4. To remove VO-specific shell variables from /etc/profile.d/lcgenv.[c]sh
5. To remove VOMS certificate from /etc/grid-security/vomsdir and VOMS-configuration from /opt/edg/etc/vomses and/or /opt/glite/etc/vomses (deponding on the node type).

Additional manual steps are necessary for some node types:

1. On CE, we had to manually remove the queue used for this VO, and to adjust maui.cfg (to remove all traces of VO from it in definitions of fairshares, reservations etc.).
2. On WMSLB we had to manually remove VO from /opt/glite/etc/glite_wms_wmproxy.gacl
3. On SE, we had to manually remove VO-related directories from storage area.

More specifically on WNs, the following manual steps are needed:

1. To remove pool accounts from /etc/passwd, /etc/shadow, /etc/group and /etc/gshadow.
2. To remove pool account home directories.
3. To remove VO-specific shell variables from /etc/profile.d/lcgenv.[c]sh.

-- MariaALANDESPRADILLO - 08 Aug 2007