Skip Menu | Logged in as guest | Logout
 
Ticket metadata
Id: 3209
Status: resolved
Priority: 3/0
Queue: vdt-internal

Fixed in: 1.8.1i
Fix scheduled: CUR

Owner: Scot Kronenfeld
Requestors: Alain Roy
Cc:
AdminCc:

New reminder:

Created: Tue Jan 08 16:27:08 2008
Starts: Not set
Started: Not set
Last Contact: Fri Jan 11 12:30:03 2008
Due: Not set
Closed: Fri Feb 15 15:24:44 2008
Updated: Fri Feb 15 15:24:57 2008 by kronenfe



History Brief headersFull headers
Subject: Add dCache SRM V2 Client to VDT 1.8.1
Download (untitled) / with headers
text/plain 1.1k
We have a confusing situation in the VDT. Today we have two SRM clients:

SRM-V1-Client. This is the official dCache client, I think. It was
written at Fermilab. I called it V1 because I mistakenly thought it was
only ever going to be an SRM V1 client.

SRM-V2-Client. This is the Bestman SRM client. It was written to work
with SRM V2 servers.

Well, the dCache client is being upgraded to support SRM V2, and we need
to upgrade it in the VDT at the same time the VDT version of dCache 1.8
is released. So where do we put it?

I propose we do the following:

1) Leave SRM-V1-Client alone
2) Add SRM-Fermi-Client. (Note, this isn't the final name--we'll know it
soon)

Note that the OSG Worker Node package contains a reference to
SRM-V1-Client. When we upgrade, it will change from SRM-V1-Client to
SRM-Fermi-Client. I'm worried about making sure that Pacman will do the
right thing in this case. So the majority of work in this upgrade is
making sure that the upgrade process itself works smoothly.

The current version of the new client can be found at:

http://www.dcache.org/downloads/1.8.0/index.shtml

On that page, it's labeled as the dCache client. (but not dcap)

-alain
Download (untitled) / with headers
text/plain 495b
We have a configure-srm script that changes some of the config values in
the old SRM-V1-Client. There is no config file that matches this in
this newer version (SRM-Fermi-Client). The only thing that the
configure script does is change three variables in the config.xml file.
The first two appear to not apply to SRM-Fermi-Client. The third is to
turn off debugging, which appears to be turned off by default in
SRM-Fermi-Client anyways.

I'm going to remove the dependency on Configure-SRM.