Hi John,
Ok, that's fine then; we definitely keep tabs on where our files are.
It sounded like the site admins were expecting to know which catalogue
to go to to find out which files were 'owned'. If that responsibility
remains in our hands that's fine.
Thanks,
Tim
On 7 Oct 2005, at 18:04, Gordon, JC (John) wrote:
> Tim, the point is that YOU as the VO should know where your files are
> catalogued. Henry was saying we needed to support every physicist who
> squirreled away his own list of files. The site doesn't know where
> files
> are catalogued but we hope you do.
>
> John
>
>> -----Original Message-----
>> From: Testbed Support for GridPP member institutes
>> [mailto:[log in to unmask]] On Behalf Of Tim Barrass
>> Sent: 07 October 2005 17:42
>> To: [log in to unmask]
>> Subject: Removing VOs files if not in catalogue (was Re:
>> Storage Types (was Re: [TB-SUPPORT] Reminder of the next UKI meeting)
>>
>>> It is of course true that anyone can upload files to an SE, but it
>>> will always be tagged as belonging to a VO. Thus, if an SE
>> is taken
>>> off the Grid, the admins should (at least in principle)
>> contact the VO
>>> and say "Here is a list of your files, copy them off within
>> 60 days or
>>> lose them". If users have uploaded data and it's not in the VO's
>>> catalogues, well, tough. The alternative is to trawl
>> through the DNs
>>> of the owners, and somehow magically figure out the email
>> address, and
>>> then contact them, and then wait for them to get back to you, and
>>> check that you have found the owners of all the files and and and.
>>
>> Hi Jens,
>>
>> This comment worries me slightly-- could you clarify what you
>> mean by "in the VO's catalogues"? We register all our files
>> in a number of places. Specifically for CMS (as you know, I
>> think?) we register files for grid access via the PubDB
>> infrastructure. Does this count?
>>
>> In the future CMS will also be using a dataset location
>> service rather than file location: the specific location of
>> files will only be known as the job reaches the site, mapped
>> using a relatively independent local catalogue. Does this fit
>> into your scheme?
>>
>> Thanks,
>> Tim
>>
|