From EGIWiki
Jump to: navigation, search
Main operations services Support Documentation Tools Activities Performance Technology Catch-all Services Resource Allocation Security

Detailed agenda: Grid Operations Meeting 22 October 2012

EVO direct link Pwd: gridops
EVO details Indico page

1. Middleware releases and staged rollout

1.1. Update on the status of EMI updates

Cristina Aiftimiei (EMI) reports on the EMI updates, twiki link

1.2. Staged Rollout

UMD 2.3.0 preparation. Release due 19 November, freeze date 12 November.

2. Operational Issues

2.1 Unsupported middleware update

Most of the sites have replied to the tickets opened by COD about the unsupported middleware still deployed at the site, providing a reasonable upgrade plan for their middleware.

Currently the problematic sites can be grouped in two categories

Next steps:

Note: Not all the sites listed now as problematic will be suspended, EGI Operations will evaluate the single cases before any suspension.

2.2 Updates from DMSU

problem in retrieving the job output after EMI2 update 4 (WMS)

for details see GGUS 87802

it seems that if an user never used the myproxy and he isn't currently using it, she can retrieve the output without any problem. For the other kind of users, the problem occurrs (see the details in that ticket).

Moreover it was also noticed that if in the jdl there isn't the variable related to myproxy, in the jdl stored in the Sandboxdir it is wrongly contained that variable set to the myproxy hostname that is set by default on the UI. Instead if in the jdl it is present an empy variable like the following:

  MyProxyServer = "";

the jdl stored on the WMS will properly contain it, the proxy is stored in the SandBoxDir (no symlink to proxy renewal dir) and the user is able to retrieve the output when the job ends.

3. AOB

From NGI_IT: problems after applying the patch released for org.sam.WN* issue on SL6: all the CREAMCE tests are in unknown status

4. Minutes

Minutes available online, here: on indico page

Personal tools