Difference between revisions of "Agenda-19-08-2013"
Jump to navigation
Jump to search
Line 59: | Line 59: | ||
* VOMS monitoring for SHA-2 support is going to be re-enabled today | * VOMS monitoring for SHA-2 support is going to be re-enabled today | ||
** VOMS monitoring was suspended because of a problem in the resource information provider, which was causing some false positives | ** VOMS monitoring was suspended because of a problem in the resource information provider, which was causing some false positives | ||
** The problem has been identified (was related to a sudo version), and information have been provided to ROD teams, and also the [ | ** The problem has been identified (was related to a sudo version), and information have been provided to ROD teams, and also the [https://wiki.egi.eu/wiki/ROD_MW_alarm_template#Decommissioning_of_non_SHA-2_compliant_services ticket template] has been edited to add more information about this issue. | ||
*** In case of a false positive with VOMS site administrators should be able to quickly solve the problem and make the service publish again itself. | *** In case of a false positive with VOMS site administrators should be able to quickly solve the problem and make the service publish again itself. | ||
Revision as of 13:46, 19 August 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
1.2 Staged rollout updates
- New in SR:
- emi-ui - 3.0.2
- gridsite - 2.1.2
- This is a hotfix for GridSite, allowing the previously disallowed dash character in delegation IDs. Delegation IDs containing non-alphanumeric characters other than a dot, coma, underscore or dash are rejected. It also properly sets the type of proxy before calling the signing function from caNl.
- canl - 2.1.2
- This is a hotfix for a bug whereby the type of proxy to sign whas erroneously hard-coded to a single value for different types of proxies, most importantly affecting RFC proxies.
- gridsite - 2.1.2
- cream - 1.16.1
- Authentication and authorization in the CREAM service now makes use of the CAnL library. The gLite security libraries are no more required.
- blah - 1.20.2
- Memory leak in BNotifier
- emi-ui - 3.0.2
- Already in SR:
- bdii-site - 1.2.1
- This new version of the site BDII contains a fix in the ldap info provider script to set to 'Unknown' cached GLUE state attributes. Bug fixes:BUG #101709: Set to 'Unknown' ldap info provider cached state attributes for the site BDII.
- bdii-top - 1.1.1
- This version of the top BDII fixes a bug in the publication of delayed delete GLUE entries. A new plugin is responsible for publishing cached entries with value 'Unknown' in the corresponding GLUE state attributes. This version also includes a bug fix in the glite-info-update-endpoints script.
- wms - 3.6.0
- This version solves the problem with Argus and WMS integration (SL6).
- voms - 3.2.0
- VOMS Admin now supports Group managers, a mechanism which allow the hierarchical dispatching of the notification resulting from user VO membership and group membership requests.
- apel - 2.2.0
- vulnerability bug fix
- bdii-site - 1.2.1
2 Operational issues
2.1 Updates from DMSU
Nothing to report
2.2 SHA-2 monitoring
The Nagios instance midmon continues to monitor the services not supporting SHA-2. An extensive overview will be part of next week's OMB meeting.
Currently there are two products not yet supporting SHA-2:
- dCache
- dCache version 2.6.5 has been released by the product team, and currently it is in the UMD software provisioning process.
- Important to find early adopters to quickly release it in UMD-3
- The SHA-2 supporting version for the 2.2.x golden release is expected, but not yest released by the product team
- The target for the 2.2.x version is UMD-2
- dCache version 2.6.5 has been released by the product team, and currently it is in the UMD software provisioning process.
- StoRM
- UMD-3 latest version is 1.11.1 It supports SHA-2 but has some critical load issues. It is recommended not to deploy this version.
- StoRM PT is testing a new release (1.11.2) which solves the critical issues of the current one.
- Currently midmon is not generating critical alarms for dCache and StoRM: there are no related alarms in the operations dashboard
- VOMS monitoring for SHA-2 support is going to be re-enabled today
- VOMS monitoring was suspended because of a problem in the resource information provider, which was causing some false positives
- The problem has been identified (was related to a sudo version), and information have been provided to ROD teams, and also the ticket template has been edited to add more information about this issue.
- In case of a false positive with VOMS site administrators should be able to quickly solve the problem and make the service publish again itself.