On 09/01/14 14:28, Ewan MacMahon wrote:
>> -----Original Message-----
>> From: Testbed Support for GridPP member institutes [mailto:TB-
>> [log in to unmask]] On Behalf Of Jeremy Coles
>>
>> The latest WLCG position on this was given by Maarten at the WLCG ops
>> meeting on Monday
>> (https://twiki.cern.ch/twiki/bin/view/LCG/WLCGDailyMeetingsWeek140106#Monday):
>>
>
> What's not in Maarten's summary though, is a recommendation of what to
> actually do about it. My inclination is that everyone should upgrade,
> and any intermediate services (like WMSes) that are then broken because
> they've not upgraded, should just be fixed.
>
> I think it made sense to hold off before Christmas, given that it was
> then less likely that such broken services would be fixed quickly, but
> that doesn't apply any more.
I've done some tests on UK WMSs/CEs using dteam based on Maarten's
scripts at:
https://www.jiscmail.ac.uk/cgi-bin/webadmin?A2=ind1401&L=LCG-ROLLOUT&F=&S=&P=7211
Executive summary: at the moment, only Imperial's WMSs are OK.
RAL's WMSs are not returning me any output
(https://ggus.eu/ws/ticket_info.php?ticket=100086).
Jobs submitted via svr023.gla.scotgrid.ac.uk: all the jobs that have
returned output end up with a 512 bit proxy somewhere in the chain.
Glasgow's other WMS was down for upgrading yesterday to address this
problem.
Jobs submitted via Imperial's WMSs: all the jobs that have returned
output have a minimum of 1024 bit certificates.
Chris
|