So, I'm glad...
By the way, please repeat the configuration process here because the
dteam jobs run on a new WN on which I had forgotten to mount /opt/exp_soft.
Afterwards I have rsync-ed by hand the local copy of /opt/exp_soft/dteam
to the central location but I might have done it during a (long) dteam
job...
Maarten Litmaath, CERN wrote:
>On Sat, 27 Aug 2005, Dan Schrager wrote:
>
>
>
>>Hi Judit,
>>
>>I have noticed that you run lengthy dteam jobs and that you have
>>installed 616Mb of software that seems 2.6.0 software here at our site.
>>Should I be glad or just worried about this ? (we still subsist at
>>2.4.0 level...)
>>
>>
>
>We are testing a centralized upgrade procedure for WNs.
>
>As of LCG-2_4_0 a standard WN installation can be superseded by a newer
>release located in the shared software area for "dteam". To get such a
>non-default release set up for a job, the user would have to put a new
>attribute in the JDL file like this:
>
> MWVersion = "2.6.0";
>
>If the release is found on the WN, it will be used instead of the default,
>else the job aborts with the reason shown by edg-job-get-logging-info.
>
>Once a site's WNs have been successfully augmented and tested this way,
>an extra run-time tag would show the availability of the newer release:
>
> VO-dteam-2.6.0
>
>(It cannot simply be "LCG-2_6_0" in this example, because the default
>still is an older release.)
>
>This scheme still is experimental; we will announce it when we think
>it is sufficiently usable. It would mainly be for users interested in
>getting the latest client code at sites whose default release is older.
>
>
|