Whole site: How to remove a VO

Consider for example to enable the VO ”<voname>”.

You have to handle the following configuration files.

• Remove <voname> from VOS and <QUEUE>_GROUP_ENABLE variables.

• Remove any other reference to ”<voname>” VO.

• Remove from your services/ or nodes/ files any reference to ”<voname>” VO.

• Remove from <your-users.conf> the users for the ”<voname>” VO.

• Remove from <your-groups.conf> the VOMS FQANs for the ”<voname>” VO.

• In order to remove ”<voname>” VO from the information published by your DPM SE, you have to manually remove the DPNS home directory (<domain> is your site domain, e.g. pd.infn.it):

# . /opt/glite/etc/profile.d/grid-env.sh
# /opt/lcg/bin/dpns-rm -r /dpm/<domain>/home/<voname>

In case of problem on removing you have to previously act on database with the following MySQL commands:

mysql> use cns_db;
mysql> delete from Cns_file_replica where sfn like '%<voname_storage_area_path>%;

where ”<voname_storage_area_path>” is e.g. /flatfiles/SE00/<voname>.

If you want to clean your nodetypes, you may perform the following optional steps (in any case the ”<voname>” will not be published anymore by your site):

• Remove the storage areas (on the SEs) related to ”<voname>” VO.

• Remove the users (and their homes) as explained here at point 5).

• In order to disable the removed ”<voname>” VO on your site you have to reconfigure your nodetypes:

# /opt/glite/yaim/bin/ig_yaim -c -s <confdir>/<your-site-info.def> -n <profile>