Alert.png 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-13-02-2012"

From EGIWiki
Jump to navigation Jump to search
Line 19: Line 19:
=== 1.2 Staged Rollout  ===
=== 1.2 Staged Rollout  ===


==== glite 3.2 ====
==== UMD-1 ====
==== UMD-1 ====
Next UMD release - UMD1.6 26 March 2012, candidates: https://wiki.egi.eu/wiki/UMD_1.6.0_Contents
Current status:
*In staged rollout (from EMI)
**UNICORE XUUDB
**UNICORE Gateway
**UNICORE UVOS
*In verification (from EMI):
**UNICORE TSI
**UNICORE X/6
**dCache
*In verification (from IGE):
**GridSAM
**GridWay
**GridFTP
**GRAM5
**RLS
**MyPROXY
**GSISSH
**GSISSHTerm
**SAGA
Other information:
*https://www.egi.eu/earlyAdopters/table and https://www.egi.eu/earlyAdopters/teams have been updated/reshufled - it takes into account EMI1 and EMI2 products seperatelly, most IGE products added (not under Globus).
*IGE products have only 1 EA, since more products are coming, we are looking for more EAs both for the already covered products as well as the new ones.


== 2. Operational Issues  ==
== 2. Operational Issues  ==

Revision as of 12:56, 13 February 2012

Main EGI.eu operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security



Detailed agenda: Grid Operations Meeting 20 January 2012 14h00 Amsterdam time

EVO direct link Pwd: gridops
EVO details Indico page


1. Middleware releases and staged rollout

1.1 EMI-1 release status

1.2 Staged Rollout

UMD-1

Next UMD release - UMD1.6 26 March 2012, candidates: https://wiki.egi.eu/wiki/UMD_1.6.0_Contents

Current status:

  • In staged rollout (from EMI)
    • UNICORE XUUDB
    • UNICORE Gateway
    • UNICORE UVOS
  • In verification (from EMI):
    • UNICORE TSI
    • UNICORE X/6
    • dCache
  • In verification (from IGE):
    • GridSAM
    • GridWay
    • GridFTP
    • GRAM5
    • RLS
    • MyPROXY
    • GSISSH
    • GSISSHTerm
    • SAGA

Other information:

2. Operational Issues

2.1 WMS 3.3.4 issues

WMproxy does not support wildcards in the .gacl file anymore

WMproxy is the user authentication module of the WMS. The VOs allowed to access the WMS service are listed in the /etc/glite-wms/glite_wms_wmproxy.gacl file. With the new release there must be exact match between the FQAN expressed in the .gacl file and the one of the user's proxy.

  • In the previous releases: the usage of wildcards was allowed, for example: <fqan>cms/*</fqan> (not anymore)
  • With the WMS released in the UMD the .gacl configuration file must contain all the FQANs explicitly listed.
  • This means that VO managers who define a new vo-role or vo-group must communicate this to WMS administrator and ask them to add the new FQAN to the service configuration.

WMS proxy renewal problem

3. AOB

3.2 Next meetings