The wiki is deprecated and due to be decommissioned by the end of September 2022.
The content is being migrated to other supports, new updates will be ignored and lost.
If needed you can get in touch with EGI SDIS team using operations @ egi.eu.
Difference between revisions of "Agenda-11-02-2013"
| Line 36: | Line 36: | ||
==== 2.1 Status of unsupported middleware update ==== | ==== 2.1 Status of unsupported middleware update ==== | ||
==== 2.2 Updates from DMSU ==== | ==== 2.2 Updates from DMSU ==== | ||
===== list-match problem with EMI2 WMS ===== | |||
Details [https://ggus.eu/tech/ticket_show.php?ticket=90240 GGUS #90240] | |||
Some CEs have enabled only a group or a role in their queues, not the entire VO: | |||
GlueCEAccessControlBaseRule: VOMS:/gridit/ansys | |||
GlueCEAccessControlBaseRule: VOMS:/gridit/ansys/Role=SoftwareManager | |||
so, when your primary attribute is: | |||
attribute : /gridit/ansys/Role=NULL/Capability=NULL | |||
if you use an EMI-2 WMS, you cannot match those resources (instead you can if use EMI-1 WMS) | |||
It seems that the problem is in the value of ''WmsRequirements'' contained the file ''/etc/glite-wms/glite_wms.conf'': the filter set in that variable is different from the one used in the EMI-1 WMS. The developers are investigating on it | |||
'''UPDATE Jan 31st''': the fix will be released in EMI-3. However, the developers provided us a rpm, ''glite-wms-classad_plugin-3.4.99-0.sl5.x86_64.rpm'', which we have installed on our EMI-2 WMS servers, and the issue has been fixed | |||
=== 3. AOB === | === 3. AOB === | ||
Revision as of 11:38, 11 February 2013
| Main | EGI.eu operations services | Support | Documentation | Tools | Activities | Performance | Technology | Catch-all Services | Resource Allocation | Security |
Detailed agenda: Grid Operations Meeting 07 January 2013
| Audio conference link | Pass: gridops |
| Audio conference details | Indico page |
1. Middleware releases and staged rollout
1.1. Update on the status of EMI updates
1.2. Staged Rollout
- Final preparation of the UMD 2.4.0
- Over 15 products will be ready to be released Full list
- Some important security vulnerabilities
- VOMS: vulnerability in VOMS Java APIs
- DPM & LFC, high vulnerability
- UNICORE/X6 -> still in verification
- GFAL 1.14.0 will solve the ATLAS data transfer problems: timeout issues in lcg_util and/or GFAL commands. In particular: lcg-cp fails with files over 5 GB GGUS ticket
- Some important security vulnerabilities
- Over 15 products will be ready to be released Full list
- updates for UMD-1
- L&B 3.2.9
- Security updates for UMD-1
- DPM & LFC 1.8.6 and VOMS 2.0.10-1
2. Operational Issues
2.1 Status of unsupported middleware update
2.2 Updates from DMSU
list-match problem with EMI2 WMS
Details GGUS #90240
Some CEs have enabled only a group or a role in their queues, not the entire VO:
GlueCEAccessControlBaseRule: VOMS:/gridit/ansys GlueCEAccessControlBaseRule: VOMS:/gridit/ansys/Role=SoftwareManager
so, when your primary attribute is:
attribute : /gridit/ansys/Role=NULL/Capability=NULL
if you use an EMI-2 WMS, you cannot match those resources (instead you can if use EMI-1 WMS)
It seems that the problem is in the value of WmsRequirements contained the file /etc/glite-wms/glite_wms.conf: the filter set in that variable is different from the one used in the EMI-1 WMS. The developers are investigating on it
UPDATE Jan 31st: the fix will be released in EMI-3. However, the developers provided us a rpm, glite-wms-classad_plugin-3.4.99-0.sl5.x86_64.rpm, which we have installed on our EMI-2 WMS servers, and the issue has been fixed