LCFG and the GridPP Virtual Organisation
The default EDG LCFG machine profiles contain configurations for a subset of VOs. Presently these are Alice, Atlas, CMS, LHCB, BioMedical, Earth Observation, WP6 and the Iteam.
This webpage collects the steps necessary to include the GridPP VO in a given site.
This page is valid for EDG Versions 1_3 and 1_4
Sites which previously included the GridPP VO, but configured for EDG Versions 1_2_x, will need to replace the LCFG configuration files with the new versions below.
LCFG Configuration Files
These configuration files should be placed in the directory /var/obj/conf/profile/source/gridpp on the LCFG server- Users-gpp-cfg.h
- UsersNoHome-gpp-cfg.h
- gridpp-ce-cfg.h
- gridpp-se-cfg.h
- gridpp-wn-cfg.h
- gridpp-ui-cfg.h
- To Compute Element nodes, add the line
#include "gridpp/gridpp-ce-cfg.h" - To Storage Element nodes add theline
#include "gridpp/gridpp-se-cfg.h" - To Worker Nodes add the line
#include "gridpp/gridpp-wn-cfg.h" - To User Interface nodes add theline
#include "gridpp/gridpp-ui-cfg.h"
The site configuration file site-cfg.h now needs to be modified to include the new VO in the SE.
- Two lines must be added:
#define SE_VO_GRIDPP
#define SE_GDMP_REP_CAT_GRIDPP_PWD !Top!Secret!To obtain a copy of the Replica Catalogue password, send an email to TB-Support.
- The line starting with #define SE_VO_ lists the locations of the shared disk space for the VO's on the Storage Element. This will usually be the subdirectory of the directory specified by #define SE_GDMP_AREA in the site-cfg.h file. The default directory is /flatfiles on the Storage Element.
NB. The default setting of SE_VO_ in site-cfg.h may be /gdmp/vo/path for all VO's. This should be changed to a specific location for each VO, usually /flatfiles/< VO> for each value of < VO>.
The location of the GridPP disk space on the Storage Element should be added to the end of the line:
#define SE_VO_ alice:/flatfiles/alice,...,wpsix:/flatfiles/wpsix,gridpp:/flatfiles/gridpp
After the LCFG profiles have been updated, they must be recompiled on the LCFG server:
mkxprof -v -A < node >
The client node should update automatically over the next 24 hours. However, to force an immediate update on the client nodes the new profile should be downloaded using:
rdxprofand then running the affected LCFG objects:
/etc/obj/YYY runwhere YYY is each of:
| LCFG Object | CE/WN/UI | SE | |
|---|---|---|---|
| auth | Yes | Yes | |
| gdmp | No | Yes | |
| gdmp_client | Yes | No | |
| rc | Yes | No | |
| voenv | Yes | No |
/etc/rc.d/init.d/lcfg.init stop /etc/rc.d/init.d/lcfg.init start
Post-LCFG Configuration Steps
Compute Element
- As described in GridPP VO, GridPP must be included with the VO's authorised to access the site. The /opt/edg/etc/mkgridmap.conf file contains the list of the LDAP servers of authorised VO's. The line
group ldap://vo.gridpp.ac.uk/ou=testbed,dc=gridpp,dc=ac,dc=uk .gridpp
should be uncommented, or added if not present. - The mkgridmap.conf file on the CE must be modified to authorise the gdmpserver VO's. Two lines are required for each of these. If they are not present or are commented out, they must be added or uncommented. For the GridPP gdmpservers VO, the two lines:
group ldap://vo.gridpp.ac.uk/ou=gdmpservers,dc=gridpp,dc=ac,dc=uk gdmp auth ldap://vo.gridpp.ac.uk/ou=gdmpservers,dc=gridpp,dc=ac,dc=uk
must be added.For the main application testbed gdmpserver VO, the two lines
auth ldap://grid-vo.nikhef.nl/ou=People,o=gdmpservers,dc=eu-datagrid,dc=org group ldap://grid-vo.nikhef.nl/ou=apptb,o=gdmpservers,dc=eu-datagrid,dc=org gdmp
should be uncommented.
NB. Be certain the application testbed gdmpservers group has ou=apptb as some the default mkgridmap.conf file may have ou=devtb. - Lockfiles must be created in the gridmap directory on the CE, one per pool account. If the GridPP VO is added after the steps in Post LCFG Installation Notes, then extra lockfiles must now be created on the CE for the GridPP accounts
cd /etc/grid-security/gridmapdir touch `grep '^gridpp[0-9][0-9][0-9]:' /etc/passwd | cut -f1 -d:` - When a GDMP client job is executed on the CE the environment variables
GDMP_CONFIG_FILE
RC_CONFIG_FILE
must be set to point to the correct configuration files for the VO. The method for this in EDG 1.4 is to require the user to include the lineeval `/opt/edg/bin/edg-vo-env < VO >`
in the job execution script, where < VO > is the VO name (in this case gridpp). This replaces the script gdmp-rc-values.sh in /etc/profile.d used in EDG 1.2.2, which should be removed.
Storage Element
The steps necessary for the SE to act as a GDMP server for the GridPP VO should all be included within the LCFG configuration and in the notes given in Post LCFG Installation Notes. If you have not already done so, the following steps are required:- The SE must be included in a VO specifically for GDMP servers. To be included in the main testbed gdmpservers VO, email Grid.Support@nikhef.nl with a copy of the SE host certificate (not key!) asking for the SE to be included in the application testbed gdmpservers VO.
You should also make sure your SE is included in the GridPP gdmpservers VO by emailing the certificate name of the SE (eg. /O=Grid/O=UKHEP/CN=host/gppse06.gridpp.rl.ac.uk) to the GridPP VO.
Worker Node
There are no extra steps for the WN. However, if the VO environment was previously set using the script gdmp-rc-values.sh in /etc/profiles.d, this script should be removed, and the environment set by the user calling eval `/opt/edg/bin/edg-vo-env < VO >` in the job execution script, as for the CE.User Interface
The steps to use the Replica Manager and GDMP Client commands on a user interface are given in the UI Installation Notes. Similarly to the CE and WN, before issuing a Replica Manager or GDMP Client command, the environment variables should be set by the user:eval `/opt/edg/bin/edg-vo-env < VO >`where < VO > is the VO name.
Testbed Support Mailing List, Testbed Installation Notes
Last modified Wed 26 November 2003 . View page history
Switch to HTTPS . Website Help . Print View . Built with GridSite 1.4.3