Difference between revisions of "NDPF TODO List"
| Line 13: | Line 13: | ||
== LFC and DPM Updates == | == LFC and DPM Updates == | ||
After we get a DPM, we need to install [http://www.listserv.rl.ac.uk/cgi-bin/webadmin?A2=ind0510&L=lcg-rollout&F=&S=&P=43649 these updates ] | After we get a DPM, we need to install [http://www.listserv.rl.ac.uk/cgi-bin/webadmin?A2=ind0510&L=lcg-rollout&F=&S=&P=43649 these updates ] | ||
| + | == FTS client == | ||
| + | Once we get a DPM we can start doing service challenge stuff. For this we will need an | ||
| + | FTS client. Here is some info from Gavin McCance: | ||
| + | <nowiki> | ||
| + | Clients: | ||
| + | |||
| + | Either manually: </nowiki>[ https://uimon.cern.ch/twiki/bin/view/LCG/FtsClientInstall13 Link] | ||
| + | <nowiki> | ||
| + | or with whatever comes with LCG-2.6.0 (yaim?) | ||
| + | |||
| + | The difficulty is the FTS server URL (i.e. "where does my client commandline | ||
| + | tool point to"). Currently, we have not finished our integration with the | ||
| + | BDII (or indeed any information system) so we use a file in the local | ||
| + | filesystem. An XML file as well. | ||
| + | </nowiki> | ||
| + | [ https://uimon.cern.ch/twiki/bin/view/LCG/FtsClientInstall13 Link] | ||
| + | <nowiki> | ||
| + | describes the format of this services.xml file - but it really only suitable | ||
| + | to point to client commandline tool to *one* FTS server. It is possible to | ||
| + | point it to multiple servers and use the "-s" option of the commandlinme | ||
| + | tool to select between them, but it's a hack that will have to go away once | ||
| + | we do it properly with the BDII, so I wouldn't rely on it. | ||
| + | |||
| + | Clients at NIKHEF: point to the SARA server. | ||
| + | |||
| + | Clients at SARA: point to either CERN T0 server or the local SARA server. If | ||
| + | the same client on a given machine needs to point to both servers (the CERN | ||
| + | one to manage the T0-T1 and the SARA on to manage the T1-T2) then use the | ||
| + | "-s" option with two entries in the service.xml file. | ||
| + | |||
| + | hope this helps, | ||
| + | cheers, | ||
| + | gav | ||
| + | </nowiki> | ||
Revision as of 13:42, 21 October 2005
Fixes needed for information published to BDII
There are a number of new attributes in the GlueVOView blocks that are not yet being published, like the software dir and data dir. This is going to require some serious quattor work and is not a task to be taken lightly.
Also there is a warning in the GIIS monitor that our publishing of teras.sara.nl as a close SE is failing some sanity checks. This last one may be a fault in the test, someone needs to looks carefully at this.
Update of Resource Broker
R-GMA GIN Update
LFC and DPM Updates
After we get a DPM, we need to install these updates
FTS client
Once we get a DPM we can start doing service challenge stuff. For this we will need an FTS client. Here is some info from Gavin McCance: Clients: Either manually: [ https://uimon.cern.ch/twiki/bin/view/LCG/FtsClientInstall13 Link] or with whatever comes with LCG-2.6.0 (yaim?) The difficulty is the FTS server URL (i.e. "where does my client commandline tool point to"). Currently, we have not finished our integration with the BDII (or indeed any information system) so we use a file in the local filesystem. An XML file as well. [ https://uimon.cern.ch/twiki/bin/view/LCG/FtsClientInstall13 Link] describes the format of this services.xml file - but it really only suitable to point to client commandline tool to *one* FTS server. It is possible to point it to multiple servers and use the "-s" option of the commandlinme tool to select between them, but it's a hack that will have to go away once we do it properly with the BDII, so I wouldn't rely on it. Clients at NIKHEF: point to the SARA server. Clients at SARA: point to either CERN T0 server or the local SARA server. If the same client on a given machine needs to point to both servers (the CERN one to manage the T0-T1 and the SARA on to manage the T1-T2) then use the "-s" option with two entries in the service.xml file. hope this helps, cheers, gav
