Steve, as the ldap query expert can you list all the non-permanent values
published?
John
> -----Original Message-----
> From: Testbed Support for GridPP member institutes
> [mailto:[log in to unmask]] On Behalf Of Burke, S (Stephen)
> Sent: 14 January 2005 13:31
> To: [log in to unmask]
> Subject: Re: Looking for LHCb files at Birmingham LCG site
>
>
> Testbed Support for GridPP member institutes
> > [mailto:[log in to unmask]] On Behalf Of Brew, CAJ (Chris)
> > said: When looking through the information published by my SE I
> > noticed that there's a line:
> >
> > GlueSAPolicyFileLifeTime: permanent
> >
> > What are the other available settings for this. Can sites
> change this
> > to 3 months and the delete stuff when it's been there three months?
>
> The schema currently says:
>
> Definition 2. Permanent file type: a file stored in a Storage
> Space that can be removed only by the owner or by the system
> administrator [1]
>
> Definition 3. Volatile file type: a file stored in a Storage
> Space that can be removed by the Storage Service when space
> is needed. A volatile file is pinned in the cache for a
> certain "lifetime" period. The length of the "lifetime" is
> the choice of the Storage Service Administrator or the
> Storage Service's policy. Usually, a file is expected to be
> "released" or "unpinned" by the client before its lifetime
> expires. Provisions can be made for extending the pinning of
> a file, but we felt that honoring pinning extension requests
> should be an implementation choice as well. [1]
>
> Definition 4. Durable file type: a file stored in a Storage
> Space that is intended to be removed as soon as possible, but
> should not be deleted by the Storage Service. It has a
> "lifetime" associated with it (perhaps longer than that of a
> volatile file), but when its lifetime expires a system
> administrator is alerted. Similar to a permanent file it can
> be only removed by the owner or the administrator. Thus, the
> concept of a "durable" file has the features of both volatile
> and permanent files.
>
> The need for a "durable" file status was inspired by the
> scenario of files generated by some compute resource, and
> there is a need to temporarily store them in a shared space
> before they are archived. Normally, the files are stored in
> the shared space as "durable", and then scheduled to be
> archived on some other archival storage system. After the
> files are archived, they are released either automatically by
> the archiving Storage Service or by the client. In case that
> the client neglects to release them, an administrator is
> alerted when the lifetime expires. [1]
>
> Stephen
>
|