1 / 11

GGUS Ticket review

GGUS Ticket review. T1 Service Coordination Meeting 2010/10/28. Summary. GGUS tickets of concern to the experiments: ATLAS: CNAF-BNL GGUS:61440 CNAF: transfer problems to BNL. Was presented at this meeting 3 times in 2months! CMS :

aretha
Download Presentation

GGUS Ticket review

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. GGUS Ticket review T1 Service Coordination Meeting 2010/10/28

  2. Summary GGUS tickets of concern to the experiments: • ATLAS: • CNAF-BNL GGUS:61440CNAF: transfer problems to BNL. Was presented at this meeting 3 times in 2months! • CMS: • GGUS:61706 CERN: Maradonaerror on CE. Was presented at this meeting also on 2010/10/07. • GGUS:62696 CERN: xrootd errors. Was presented at this meeting also on 2010/10/07. • GGUS:63450 CERN: SLS links missing from Critical Service map. • LHCb: • GGUS:59880 IN2P3: Shared area performance problems. • GGUS:62800 IN2P3: Shared area problems.

  3. ATLAS CNAF-BNL Transfer

  4. CMS CERN Maradona errors

  5. CMS xrootd errors

  6. CMS missing links to SLS

  7. LHCb jobs failing @ IN2P3 due to shared area problem

  8. LHCb software installation problems at IN2P3

  9. Other GGUS issues • 21 new GGUS Support Units entered operation with GGUS 8.0 on 2010/10/27. • No impact to GGUS ticket submitters who select to Notify a given Site, i.e.most of WLCG tickets. • But, if the problem is related to the product itself and not to the site, it is better to open a ticket and let the TPM assign it. • New project structures (EGI/EMI) require the assignment to middleware SUs only by the 2nd level (DMSU=Deployed Middleware SU). No impact to tickets in category 2 (above) but no more cross-assignment possible, for ex. for tickets that turn out to be for any gLite package. Planned for the next GGUS Rel. Details in savannah support #117155. Dimou M.

  10. New GGUS SUs New 2nd level SUs: - "VO Services" for questions by VO Managers on EGI services. - ARC_DEPLOY - SAGA-SD (will phase-out R-GMA eventually) New 3rd level SUs: Middleware clients: - gLite UI - gLite WN - gLite VOBOX Under 3rd level experts: - EMI Testbeds - EMI QA Tools Batch systems' integration (utils): - gLite Torque Utils - gLite SGE Utils - gLite Condor Utils - gLite LSF Utils

  11. More new GGUS 3rd level SUs Under project EMI: - ARC - UNICORE-Client - UNICORE-Server - Proxyrenewal - Gridsite - gLiteYaim Core - gLite Java Security - gLite Hydra - gLite Identity "Other projects": - IGE (Initiative for Globus in Europe)

More Related