Difference between revisions of "Agenda-03-04-2013"
Line 15: | Line 15: | ||
==== 1.2. Staged Rollout ==== | ==== 1.2. Staged Rollout ==== | ||
* UMD-1 releases: | |||
* UMD-2 releases: | |||
** EMI-2 [http://www.eu-emi.eu/emi-2-matterhorn/updates/-/asset_publisher/9AgN/content/update-9-21-02-2013-v-2-6-1-1 update 9] | |||
*** Still under SR: Cream-torque, | |||
*** Ready for production: Cream 1.14.3 ; Wms 3.4.1. | |||
** IGE 3.1 and - 3.0: Gsisshterm - 1.3.4; Gram5 - 5.2.3 | |||
** EMI-2 [http://www.eu-emi.eu/emi-2-matterhorn/updates/-/asset_publisher/9AgN/content/update-10-02-04-2013-v-2-6-2-1 update 10] | |||
*** Contains security updates for CREAM | |||
* Staged rollout finished for EMI WN tarball [https://rt.egi.eu/rt/Ticket/Display.html?id=4927 RT] | |||
* UMD-3 releases: | |||
** Contains all the EMI-3 products (50 products) released on the 11th MaArch [http://www.eu-emi.eu/emi-3-montebianco Release] | |||
*** Priorities according to [https://wiki.egi.eu/wiki/Agenda-04-03-2013 table] | |||
* Wiki with the issues found during SR activities regarding the upgrades from EMI-2 to EMI-3 | |||
=== 2. Operational Issues === | === 2. Operational Issues === |
Revision as of 12:19, 3 April 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. Update on the status of EMI updates
1.2. Staged Rollout
- UMD-1 releases:
- UMD-2 releases:
- Staged rollout finished for EMI WN tarball RT
- UMD-3 releases:
- Wiki with the issues found during SR activities regarding the upgrades from EMI-2 to EMI-3
2. Operational Issues
2.2 Updates from DMSU
problems with EMI-3 STORM
see details in GGUS #92819
For the moment we recommended NOT to upgrade STORM to EMI-3 (or the clean installation) because when you launch consecutive lcg-gt calls, they fail with a Requested file is busy error. For example:
$ lcg-cp -b file:/home/enol/std.out -U srmv2 srm://test27.egi.cesga.es:8444/srm/managerv2?SFN=/dteam/t1 $ lcg-gt -b -T srmv2 srm://test27.egi.cesga.es:8444/srm/managerv2?SFN=/dteam/t1 gsiftp gsiftp://test27.egi.cesga.es:2811//storage/dteam/t1 ee152752-020f-4598-b19e-a4bc56dcb5b8 $ lcg-gt -b -T srmv2 srm://test27.egi.cesga.es:8444/srm/managerv2?SFN=/dteam/t1 gsiftp srm://test27.egi.cesga.es:8444/srm/managerv2?SFN=/dteam/t1: [SE][StatusOfGetRequest][SRM_FILE_BUSY] Requested file is busy (in an incompatible state with PTG) lcg_gt: Invalid argument"
For each protocol published by the SE, the nagios SRM probes do a lcg-gt which will return a CRITICAL state.
WMS on sl6 doesn't work with ARGUS
see details in GGUS #92773
WMS on sl6 cannot use ARGUS as authorization system: because SL6 uses the NSS library instead of OpenSSL, the proxy are not correctly handled. It is a known problem in NSS, and will not be corrected soon.
critical issues on EMI-3 VOMS: wait for the release of EMI-3 first update
We have found some issues that affect the service functionality and in particular make the installation and operation of the service problematic for deployments with large number of VOs:
VOMSES startup script fails in restarting VOMSES web app
VOMS Admin service incorrectly parses truststore refresh period from configuration
These issues have already been acknowledged by the developers and are being currently fixed. A new version of voms-admin-service fixing the above issues is scheduled for release on April 18th. For this reason, and given the stability of the EMI 2 VOMS services, we recommend NOT to upgrade now and wait for the version that will be released in the first EMI-3 update.