Hi Phil,
you can declare it in the Glue schema. Then whoever puts important files
on your SE should be aware that they can be deleted.
The field is
GlueSAPolicyFileLifeTime
and can be set for each VO in
/opt/lcg/var/gip/lcg-info-generic.conf
Becareful that this is overridden if you run YAIM function config_gip
again. It is one of those things I asked to be changed in bug 8777 I keep
on talking about.
If you put it in the Glue schema you are declaring your SE policy (as the
name says) which means you can delete files whether the system can do it
automatically for you (SRM v2) or not (SRM v1, classic SE). At least this
is how I interpret it.
cheers
alessandra
On Fri, 1 Jul 2005, Philip Clark wrote:
>>> I seem to remember reading that the different
>>> storage types are not available until SRM v2?
>>
>> Yes but these storage types are with regard to the services we expect from the systems you guys run so at the moment the ideas are in our heads rather than formally specified as a computer query-able and job scheduling factor. If your service was in the future "permanent space type" we would address these issues in the Glue Schemer before we could expect you to provide the higher levels of service we rarely should have this in the Schemer now as how do you know that a site is tier 2 or tier 0-1 but its on the schemer groups to-do list. If no one is sure maybe I should check.
>
> is there a way to make sure the space is volatile at the moment?
>
> -Phil
>
--
********************************************
* Dr Alessandra Forti *
* Technical Coordinator - NorthGrid Tier2 *
* http://www.hep.man.ac.uk/u/aforti *
********************************************
|