 |
 |
Hi Chris, > I think expecting that all sites are happy to take the responsibility of > permanently storing critical experimental data is naïve but that is what the true, and of course we as the users don't require a tiny site to serve as a [semi-]permanent ATLAS data storage. But we have no way to differentiate! As soon as a tiny 20GB disk appears in the BDII as a "StorageElement", we have almost no way to figure it's not quite a storage element. Does anybody modify the FileLifeTime attribute? Is there any tool that makes use of it? Is there an option in lcg-cr that specifies requested file life time? > current model has signed us up to. Sorry, but how can a _model_ "sign up" anybody? The system is fairly configurable, and if you don't want your SE to accept large files or long-living files, or ATLAS files, please configure it that way. I wonder though whether lcg-cr makes any use of those extra attributes, but even this is not a model problem but an implementation issue. Oxana