|
|
| Line 1: |
Line 1: |
| {{Template:Op menubar}} | | {{Template:Op menubar}} |
|
| |
|
| = Detailed agenda: Grid Operations Meeting 13 February 2012 14h00 Amsterdam time = | | = Detailed agenda: Grid Operations Meeting 27 February 2012 14h00 Amsterdam time = |
|
| |
|
| {| | | {| |
| |- | | |- |
| | [http://evo.caltech.edu/evoNext/koala.jnlp?meeting=vsvivIete2I8IDaia9Itas EVO direct link] | | | [http://evo.caltech.edu/evoNext/koala.jnlp?meeting=MvM2Ml2e2DDvDn9n9iDe9v EVO direct link] |
| | Pwd: '''gridops'''<br> | | | Pwd: '''gridops'''<br> |
| |- | | |- |
| | [https://www.egi.eu/indico/getFile.py/access?resId=0&materialId=2&confId=811 EVO details] | | | [https://www.egi.eu/indico/materialDisplay.py?materialId=1&confId=829 EVO details] |
| | [https://www.egi.eu/indico/conferenceDisplay.py?confId=811 Indico page] | | | [https://www.egi.eu/indico/conferenceDisplay.py?confId=829 Indico page] |
| |} | | |} |
|
| |
|
| Line 18: |
Line 18: |
| === 1.1 EMI-1 release status === | | === 1.1 EMI-1 release status === |
|
| |
|
| *EMI status update: [https://twiki.cern.ch/twiki/bin/view/EMI/EmiEgiGOM#Status_13_02_2012 link]
| | |
|
| |
|
| === 1.2 Staged Rollout === | | === 1.2 Staged Rollout === |
| Line 24: |
Line 24: |
| ==== 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.
| |
| *Mail sent last week to SA1 and NOC managers to ask for EAs interested in testing EMI2 products. EMI2 is due end of April, but we need to start plan well ahead of time.
| |
| **EMI2 will be supported for SL5, SL6 and Debian6 ('''squeeze'''), it's way important to know which sites plan for which OS, and that can volunteer for it.
| |
|
| |
|
| == 2. Operational Issues == | | == 2. Operational Issues == |
|
| |
| === 2.1 WMS 3.3.4 issues ===
| |
|
| |
| ==== WMproxy does not support wildcards in the .gacl file anymore ====
| |
|
| |
| *Related [https://ggus.eu/tech/ticket_show.php?ticket=74257 GGUS ticket]
| |
|
| |
| 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.
| |
|
| |
| ==== [bug] WMS proxy renewal problem ====
| |
|
| |
| *Related [https://ggus.eu/tech/ticket_show.php?ticket=78892 GGUS ticket]
| |
|
| |
| WMS cannot renew proxies for users who belong to multiple groups within the same VO.
| |
|
| |
| *It is a bug in the VOMS client
| |
| **VOMS developers have already accepted the bug and a fix will be released ([https://savannah.cern.ch/bugs/?91228 bug ticket])
| |
| **We will try to ask to have it released before EMI-2,possibly in time for '''UMD 1.6''' end of March 2012 (possibly before emi-2).
| |
| *This seems to be a '''serious bug''' that affects WMSes serving VOs with multiple groups (it is not unlikely that a user owns more than a role). We should warn site administrators that an upgrade to UMD WMS may brake the services, with a '''broadcast'''.
| |
| **Alessandro (who reported the problem in the GGUS ticket) removed from production the UMD WMS(es) leaving the gLite instances
| |
|
| |
|
| === 2.2 Service/Site decommissioning procedures === | | === 2.2 Service/Site decommissioning procedures === |
|
| |
| Following some feedback received during the review of the resource centre decommissioning procedure I recently split this procedure into two new ones:
| |
|
| |
| *[[PROC11draft|Resource Centre decommissioning procedure]]
| |
| *[[PROC13draft|Service decommissioning procedure]]
| |
| *The Site decommissioning procedure, now refers to the service decommissioning procedure for the steps that involve services decommission
| |
| **Splitting the procedure did not change the overall set of steps and actions, the comments you already provided are still valuable and most of them have been implemented in the two new procedures
| |
| **Now resource centres will have a procedure to follow as a service needs to be decommissioned
| |
|
| |
| ''Please provide feedback about the new procedures within this week''
| |
|
| |
|
| == 3. AOB == | | == 3. AOB == |
|
| |
|
| === 3.2 Next meetings === | | === 3.2 Next meetings === |
| | | 12 March 2012, h14:00 Amsterdam time. |
| [[Category:GridOpsMeeting]] | | [[Category:GridOpsMeeting]] |
The wiki is deprecated and due to be decommissioned by the end of September 2022.