On 4 August 2011 22:42, Ewan MacMahon <[log in to unmask]> wrote:
>> -----Original Message-----
>> From: Testbed Support for GridPP member institutes [mailto:TB-
>> [log in to unmask]] On Behalf Of Alastair Dewhurst
>>
>> ATLAS have decided that they are definitely going to switch to using CVMFS
>> for distributing their software across the grid. They have not set a
>> definite timeline yet but have asked each cloud to come up with a strategy
>> for migrating and testing sites. To start I think its best to find out
>> what the current state of deployment across the cloud is and how much
>> experience people have with it.
>>
> Can I just clarify what the intended configuration is? It would
> appear from some of the responses that the /opt stuff has gone
> away, but there's still a need for an ATLAS_LOCAL_AREA variable
> and space; is that
> - still the case now?
> - expected to remain the case?
>
> And if so, what is it for?
>
As Alessandra says, it's basically a place that contains your
setup.sh.local file for local ATLAS configuration. (Use of the CVMFS
copy of the conditions database is presently configured there, but the
rest is non-CVMFS local configuration you might have set up. So, if
you were using pcache, you'd have configured the alias for the pcache
transfer script here.)
I can't see a way to avoid having to use this, since CVMFS is a
read-only filesystem on the client end, and I don't see ATLAS wanting
to move away from site-local configuration options.
Sam
> Ewan
>
|