1 / 7

SA1 Status Report D/CH

SA1 Status Report D/CH. Holger Marten, Sven Hermann Forschungszentrum Karlsruhe. Production Service in D/CH. Resource Centres (EGEE partners). Planned resources D/CH: PM 14 (June ‘04 = 400 CPUs, 64 TB disk, 115 TB Tape. Additional Centres (non-EGEE partners).

rafer
Download Presentation

SA1 Status Report D/CH

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. SA1 Status Report D/CH Holger Marten, Sven Hermann Forschungszentrum Karlsruhe

  2. Production Service in D/CH Resource Centres (EGEE partners) Planned resources D/CH: PM 14 (June ‘04 = 400 CPUs, 64 TB disk, 115 TB Tape Additional Centres (non-EGEE partners) No detailed resources committed but wish to follow mw installation/certification procedures D/CH meeting, GSI, 7 March 2005

  3. Production & other services in D/CH • production service • FZK • 4.2 Million user hours, 1.5 Million Jobs in 2004 • 65% of resources used by non-LHC (BaBar, CDF, Dzero, Compass) • 35% of resources used for contributions to LCG DCs (partly via LCG) • DESY • running Monte Carlo simulations for ZEUS in collaboration with 22 sites, 1800 CPUs, 100 Mio events simulated • H1 preparing MC production as well • FhG/SCAI • users run applications for BioMed & ESR • pre-production service at FZK • LCG 2.3.0 under SLC3; moving to LCG 2.4.0, then gLite • prototype service (testbed) at FZK • installation of gLite for demo together with GSI • Global Grid User Support GGUS at FZK • see talk by Torsten Antoni • rotating mw installation support in D/CH • FZK (Apr – Aug’04) • FhG/SCAI (Sept, Oct’04) • DESY (Nov – Jan’05) • To be re-organized; see further transparancies D/CH meeting, GSI, 7 March 2005

  4. D/CH resource allocation policy 19 supported VOs, number unchanged since QR2 about 97% of resources for HEP D/CH meeting, GSI, 7 March 2005

  5. Organisational Matters • Current most important SA1 Documents: • “User Registration and VO Membership Management Requirements” • Procedures for registration of new users • “Site Registration Policy & Procedure”; Doc 503198 • Procedures for registration of new sites within EGEE • “EGEE Operations Manual” • The basis for problem solving and daily support work • Deliverables • DSA1.4: "assessment of initial infrastructure operation & plan for next 12 months" • Due by end of March; written by R.Rummler (IN2P3); based on information about the current infrastructure and operations, and main input from ROCs taken from QRs • Next Meetings & Conferences • 17-18 March: All ROC Managers Meeting (ARM-3) in Lyon • Any input for D/CH? Pse contact Sven • 18-22 April: 3rd EGEE Conference in Athens • Any input for D/CH? Pse contact Holger & Sven D/CH meeting, GSI, 7 March 2005

  6. Open Issues SA1 • Accounting info in GOC DB is essential for the project • Currently only 4 sites in D/CH provide data (DESY, FhG SCAI, GSI Dteam only, U Wuppertal) • Certification of new sites is a project target according to TA • How many of them can we certify and support? • How to organize this? • 24x7 operations is a project target according to TA • How to organize this in a distributed ROC? Do we have the manpower? • SA1 Web pages • Have been updated by FZK. Any further input for D/CH? • mw releases • LCG 2.3.1 available (security updates!) • LCG 2.4.0 planned for April’04 • Needs a rollout plan for D/CH. • General Problems: • Monitoring web pages not very stable • Information on available storage inconsistent D/CH meeting, GSI, 7 March 2005

  7. Open Issues SA1 Support • ROC Operations Support D/CH • Handle tickets created in CERN/Savannah • FZK did this from 17-nov-04 to 27-feb-05, now FhG SCAI • Planned: CERN/Savannah to be moved to GGUS/Web-Service. Until then: • Create contact Mail “ROC-on-duty” with auto-forward to support group • Support group changes every two weeks Project Week Calendar Week Week start date On Duty Site / Contact 46/47 7/8 14/02/2005 - 27/2/2005 FZK 48/49 9/10 28/02/2005 - 13/3/2005 FhG 50/51 11/12 14/03/2005 - 27/3/2005 GSI 52/53 13/14 28/03/2005 - 10/4/2005 DESY 54/55 15/16 11/04/2005 - 24/4/2005 FZK • General EGEE 2nd Level Support • Requested by Alistair Mills (Executive Support Committee) • To have a last resort for Tickets that didn‘t find a support group • To set up the GGUS knowledge base • To ensure that all problems are attacked • To learn more about distributed support work flow in EGEE • Flexible instead of formal procedure: solve ticket or find a „guru“ • How to handle this request for D/CH? D/CH meeting, GSI, 7 March 2005

More Related