Dear All
For those not following the GDB, you may be interested in some of the talks at http://indico.cern.ch/conferenceDisplay.py?confId=155074.
Peter Solagna has just given an update on the middleware decommisioning timelines. Slide 9 is worth sharing:
•DPM, LFC and WN will be unsupported starting from Dec 1st
–No extension of the support expected
•DPM
–Raise alarms for DPM starting from Dec 1st
–Deadline for upgrading DPM: Jan 31, 2013
–Site managers must put unsupported DPM in downtime by Feb 1st, 2013
•LFC timeline can be aligned with DPM
•WN timeline to be defined in the coming few days
–WN 2.0.1-1 is planned to be released Next Monday in UMD
There is a discussion due on the latest WN release so the WN date may still change. For those sites dependent on the tarball, Matt is only just testing a general build which makes a 1st November deadline for the dependent sites rather unlikely.
It is also worth repeating the news from the 1st November WLCG Operations Coordination Team meeting: https://twiki.cern.ch/twiki/bin/view/LCG/WLCGOpsMinutes121101:
"Middleware news and baseline versions (Nicolò)
https://twiki.cern.ch/twiki/bin/view/LCG/WLCGBaselineVersions
Nicolò repeats some recommendations for sites:
• In general, if a site wants to upgrade a service, the EMI-2 version should be chosen
• Sites with a gLite WMS should upgrade to version 3.3.8, which fixes important bugs
• From today, EMI-1 gets only security updates: therefore, important bug fixes will be available only for EMI-2
• Now the baseline version for the WN is the EMI-2 one: sites are strongly encouraged to upgrade if they still have a gLite WN, but it's less urgent if they have EMI-1 (check the WLCG WN testing page for the most recent information)
• the EMI-2 UI has a serious bug affecting the submission to the gLite WMS; moreover the tar ball distribution is not yet available
Peter brings up the fact that the SAM/Nagios boxes still use the gLite UI. Anyway, this is not considered a problem because it's a very controlled environment and the required functionality works as needed with gLite."
regards,
Jeremy
|