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

Fixed in: 1.10.1
Fix scheduled: NEW

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

New reminder:

Created: Fri Apr 25 15:38:39 2008
Starts: Not set
Started: Wed Apr 30 12:20:07 2008
Last Contact: Not set
Due: Not set
Closed: Wed Apr 30 13:40:41 2008
Updated: Wed Apr 30 13:40:59 2008 by kronenfe



History Brief headersFull headers
Subject: Rename SRM Clients
Download (untitled) / with headers
text/plain 1.1k
We have two SRM clients in the VDT, and they are named confusingly:

SRM-V1-Client
SRM-V2-Client

We will rename them for VDT 1.10.0. The community consensus appears to
rename them with the name of the organization that created them, not the
name of the software they are distributed with, because this will help
make it clear that these tools are supposed to work with any SRM
implementation.

So we will rename them like this:

SRM-V1-Client => SRM-Client-Fermi
SRM-V2-Client => SRM-Client-LBNL

I hope these names don't bring along their own confusion. "Can I only
use this version at Fermilab?" But until the developers provide
independent names for these things, this is what we'll do.

There are four things to do here:

1) Rename the packages.
2) Rename the directories they unpack into.
3) Rename any references to this from other VDT packages, like VDT or
VDT-Client.
4) Communicate with Suchandra Thapa and Rob Quick to update the VTB,
ITB, and Production caches to point at the new names, in case they
refer to them. I know the wn-client package refers to the SRM
clients, and perhaps others do too.