Hi everyone,
I've finally got round to installing the new DPM plugin on our production
DPM. Looking through the README, there is the section:
If you have a YAIM "out of the box" setup then values like:
GlueSARoot: VO:/dpm/DOMAIN/home/VO
GlueSAPath: /dpm/DOMAIN/home/VO
I remember seeing some discussion about this at the time when the plugin
came out, but didn't manage to comment. Anyway, I think "YAIM out of the
box" gives:
GlueSARoot: VO:/dpm/DOMAIN/home/VO
GlueSAPath: VO:/dpm/DOMAIN/home/VO
You can see this from the following section of the
/opt/lcg/yaim/functions/config_gip function:
--
for VO in $VOS; do
if ( echo "${NODE_TYPE_LIST}" | grep SE_dpm > /dev/null ); then
storage_root="${VO}:/dpm/`hostname -d`/home/${VO}"
storage_path=${storage_root}
elif ( echo "${NODE_TYPE_LIST}" | grep SE_dcache > /dev/null ); then
storage_root="${VO}:/pnfs/`hostname -d`/data/${VO}"
storage_path=${storage_root}
else
storage_path=$( eval echo '$'VO_`echo ${VO} | tr '[:lower:]'
'[:upper:]'`_STORAGE_DIR )
# This will probably be wrong for multiple SEs - for the future...
#
storage_root="${VO}:${storage_path#${CE_CLOSE_SE1_ACCESS_POINT}/}"
storage_root="${VO}:${storage_path#${CLASSIC_STORAGE_DIR}}"
fi
cat <<EOF >> $outfile
dn: GlueSALocalID=$VO,GlueSEUniqueID=${se_host}
GlueSARoot: $storage_root
GlueSAPath: $storage_path
--
I have has to hack the config_gip to give the desired output in the README
file. Performing some ldap searches on other sites shows the same issue is
being experienced elsewhere.
Cheers,
Greig
--
=======================================================================
Dr Greig A Cowan http://www.ph.ed.ac.uk/~gcowan1
School of Physics, University of Edinburgh, James Clerk Maxwell Building
TIER-2 STORAGE SUPPORT PAGES: http://wiki.gridpp.ac.uk/wiki/Grid_Storage
=======================================================================
|