Difference between revisions of "Agenda-28-10-2013"
Line 33: | Line 33: | ||
=== 1.3 Issue with the latest release of BDII in UMD-2 === | === 1.3 Issue with the latest release of BDII in UMD-2 === | ||
=== 1. | === 1.4 Proposal: UMD-2 security support === | ||
* UMD-2 - formally - would end security support on April 2014. | * UMD-2 - formally - would end security support on April 2014. |
Revision as of 12:53, 28 October 2013
Audio conference link | Conference system is Adobe Connect, no password required. |
Audio conference details | Indico page |
1. Middleware releases and staged rollout
1.1 News from URT
- ARC: Major release on November 9th. There are small backward incompatibilities, ARC release team is changing the name of the rpms to mark that the new release is not backward compatible, and release in EPEL the new packages.
- INFN, new release of several products expected at the end of October
- CREAM core, SLURM plugin, Torque plugin and BLAH
- Information system fix and other bug fixes
- StoRM 1.11.3 bug fix release
- VOMS server and client. CAnL support for the API, several bugs and issues fixed for the server.
- CREAM core, SLURM plugin, Torque plugin and BLAH
- EGCF: new release expected, 5.2.5. Mainly bug fixes, fix for the hanging gridftp server processes issue.
- QCG: New release expected on November 15th featuring: SHA-2 support and information system integration with EGI. Several improvements in the clients.
1.2 Staged rollout updates
- SAM update 22 is ready to be moved into production
- Emergency release of BDII in UMD-2 due to some missing rpm's in repository GGUS
- The UMD-2.7.0 update comes with a newer version of the glite-info-provider-ldap which changes the location of the glite-info-provider-ldap to /usr/libexec. Unfortunately some rpms haven't been updated (in contrast to UMD-3) to a version that can cope with that change resulting in a empty bdii!
- Solution: Update to UMD-3.
- The UMD-2.7.0 update comes with a newer version of the glite-info-provider-ldap which changes the location of the glite-info-provider-ldap to /usr/libexec. Unfortunately some rpms haven't been updated (in contrast to UMD-3) to a version that can cope with that change resulting in a empty bdii!
1.3 Issue with the latest release of BDII in UMD-2
1.4 Proposal: UMD-2 security support
- UMD-2 - formally - would end security support on April 2014.
- SA2 proposes, starting from November 2013 to release only security updates for UMD-2
- The number of early adopters deploying UMD-2 is reducing.
- Updates from PT are less frequent for UMD-2.
2 Operational issues
2.1 Updates from DMSU
Unable to retrieve the output sandbox in a custom dir from a CREAM CE
see details in GGUS #98368
The command glite-ce-job-output with --dir option fails when the specified path contains 'special' chars, such as '=' or '.' .
$ glite-ce-job-output --dir /var/lib/gridprobes/lhcb.Role=production/emi.cream/CREAMCEDJS/ce208.cern.ch/jobOutput https://ce206.cern.ch:8443/CREAM023339075 2013-10-24 10:10:04,637 FATAL - Failed creation of directory [/var/lib/gridprobes/lhcb.Role=production/emi.cream/CREAMCEDJS/ce208.cern.ch/jobOutput/ce206.cern.ch_8443_CREAM023339075]: boost::filesystem::path: invalid name "lhcb.Role=production" in path: "/var/lib/gridprobes/lhcb.Role=production/emi.cream/CREAMCEDJS/ce208.cern.ch/jobOutput/ce206.cern.ch_8443_CREAM023339075"
This bug is present on EMI-2 UI and sl5 EMI-3 UI; the developers are investigating #CREAM-128
2.2 Glue validator alarms
ROD teams have been notified about the new probe that will generate alarms in the Operations Dashboard.
Peter has generated an Excel file containing the Site-BDIIs failing the probe on midmon, mapped into sites and NGIs. The real time status can be checked on midmon.
The possible date to turn on alarms is November 22nd, please contact sites who are failing the test and ask them to debug the problems and provide feedback if there are problems with the results. More information on glue-validator can be found in the manual page maintained by the developer. Remember to run it with the -k option to skip the known issues that cannot be solved at site level.
3. AOB
3.2 Next meeting
Proposed date for the next meeting is November 11th 2013, 14:00 CEST