Show Children Hide Children

Main FTS Pages
FtsRelease22
Install
Configuration
Administration
Procedures
Operations
Development
Previous FTSes
FtsRelease21
FtsRelease21
All FTS Pages
FtsWikiPages
Last Page Update
GavinMcCance
2008-03-18

This procedure is obsolete. You should use the glite-sd2cache tool now - see FtsServicesXmlGliteSd2Cache.

Obsoleted by Gavin McCance, March 2008.

FTS services.xml cache file at CERN.

What is it?

This is the procedure for creating or updating the services.xml information service cache file on the CERN FTS instance. There is a general procedure as well. FtsServerServicesXml20.

When to use it?

When a new SRM server has been added to EGEE.BDII and you want to include it in the cache. The script is not run by cron due to the high load it generates on the EGEE.BDII.

Updating the services.xml file.

Start on one of the agent boxes and take the current services.xml file and make local copy.

cp -f /opt/glite/etc/services.xml /root/services.xml.old

Make sure you have the latest make-services.sh script from FtsServerServicesXml20.

Source the gLite environment:

. /etc/profile

Run the script:

./make-services.sh --ftshost prod-fts-ws.cern.ch --oldxml /root/services.xml.old --serxml /root/services.xml --addvo ops --verbose

this will use the default global LCG EGEE.BDII (lcg-bdii.cern.ch) and the default MyProxy server myproxy-fts.cern.ch. It will add in the ops VO to all SRMs (if not published properly by the storage elements).

If this command fails, run it again (likely issue is BDII timeout).

Verification

First count the number of SRMs:

grep "<type>SRM</type>" /root/services.xml | wc -l
grep "<type>SRM</type>" /root/services.xml.old | wc -l

the first number (from the new file) should be greater (or equal) than the second (because the script always adds SRMs keeping the old definitions at the end of the file; it will never remove them).

export GLITE_SD_SERVICES_XML=/root/services.xml
glite-sd-query -t SRM

If this succeeds, then the file is correctly formatted. Otherwise, repeat the whole operation or contact fts-support@cern.ch.

Deployment

The following files are the master services.xml files for prod, tiertwo and pilot FTS clusters.

  • /afs/cern.ch/project/gd/SC3/SC4/services.xml/services-prod-cluster.xml
  • /afs/cern.ch/project/gd/SC3/SC4/services.xml/services-tiertwo-cluster.xml
  • /afs/cern.ch/project/gd/SC3/SC4/services.xml/services-pilot-cluster.xml

A Quattor managed cron runs on each of the agents /etc/cron.d/fts-cron-in-services-xml.ncm-cron.cron that copies in this file to /opt/glite/etc/services.xml if the destination is missing or older than the source. The cron currently runs once per hour.

Make the backup of the new file in AFS:

cp -f /root/services.xml /afs/cern.ch/project/gd/SC3/SC4/services.xml/services-<cluster>-cluster.xml

where is the cluster you are working with, i.e prod, pilot or tiertwo

wait one hour for the cron job above to run.

Update the Wiki page example file

Put the new file as an attachement on FtsServerServicesXml20. This will make sure that the example file is always up to date.

Notes

The general description of the make-services.xml tool is in FtsServerServicesXml20.


Maintainer: GavinMcCance


Edit | Attach | Watch | Print version | History: r5 < r4 < r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r5 - 2008-03-18 - GavinMcCance
 
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    LCG All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback