1 / 17

GGUS Operations Model

GGUS Operations Model. Torsten Antoni KIT-SCC. Outline. GGUS operations model (technical) GGUS operations model (processes) Discussion. Outline. GGUS operations model (technical) GGUS operations model (processes) Discussion. ROC C. ROC B. RC A. VO Support C. ROC N. RC A.

gloria
Télécharger la présentation

GGUS Operations Model

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 Operations Model Torsten Antoni KIT-SCC

  2. Outline • GGUS operations model (technical) • GGUS operations model (processes) • Discussion SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  3. Outline • GGUS operations model (technical) • GGUS operations model (processes) • Discussion SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  4. ROC C ROC B RC A VO Support C ROC N RC A VO Support B RC A VO Support A RC B RC B RC B RC C RC C RC C VO Support C ROC C ROC B ROC N VO Support B VO Support A GGUS Central System CIC Portal COD Deployment support Middleware support Deployment support Network Support TPM Middleware support Network Support ENOC/OPN Middleware support Middleware support Other Grids Other Grids Other Grids Middleware support Middleware support Middleware support Other Grids Other Grids Other Grids GGUS operations model SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  5. GGUS operations model (technical) • user support model regional (almost) from the beginning • regional help desks • give support to sites • provide uplink to central coordination • Main concern is scalability from ROCs to NGIs • increasing number of interfaces • need for standardisation • moving to messaging could provide the solution • needed in other areas anyway • Correlation with COD model and OAT work • Middleware support: https://twiki.cern.ch/twiki/bin/view/EGEE/Egee3Jra1Support SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  6. Distributed model VO Summarising the possible scenarios in one sketch rCOD cCOD rCOD rCOD rCOD GGUS rCOD rCOD RC rCOD ROC SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  7. Distributed model VO Current draft cCOD rCOD rCOD GGUS rCOD RC ROC SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  8. Outline • GGUS operations model (technical) • GGUS operations model (processes) • Discussion SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  9. VO Support Units ROC Support Units Services Support Units Middleware Support Units Deployment Support Units Other Grid Infrastructures Network Support Software Support Units External Support Units Standard support workflow TPM + VO Support First Line Support WLCG Data Taking Readiness WS - CERN 13/11/2008 - Torsten Antoni

  10. Summary of ‘old’ new features SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  11. Expansion of direct routing • During EGEE’08 discussion on how to enable the extension of Team Tickets also to Tier-2 sites • Proposed solution: Interface between GOCDB and GGUS to allow retrieval of site names and contacts • Proposal to open up the direct ticket routing mechanism (as being used for the Alarm and Team Tickets) to ALL sites and ALL users • Met with broad agreement • If not used properly by the general user, the feature could in future be restricted to certain user groups (like the LHC VO shifters) SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  12. T P M r o u t e s Assign to TPM t i c k e t t o R O C S e n d n o t i f i c a t i o n m a i l n o n o t o s i t e S u b m i t v i a S i t e n a m e E n d y e s y e s S t a r t w e b p o r t a l ? s p e c i f i e d ? T i c k e t r o u t e d t o R O C a u t o m a t i c a l l y G G U S D i r e c t U S E R T i c k e t R o u t i n g 0 7 / 1 1 / 2 0 0 8 V 1 0 - D r a f t G u e n t e r G r e i n Workflow for direct notification • Will be available on the training system soon SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  13. Transition to EGI RC ROC RC GGUS RC NGI RC RC EGEE NGI SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  14. Effects on TPM • direct ticket routing frees some resources within the TPM effort • these will be used for: • aim at ticket assignment within one hour • TPM having now more time to dedicate to quality of support rather than assignment • First line support, focussed on debugging middleware issues • Monitoring of tickets • TPM being the second step in escalation for a ticket (SU, SU+TPM, SU+TPM+USAG) • Preparing the escalation reports • Further invitation, especially now that teams are beginning to use and contribute to the TPM wiki pages • Revising and contributing to the documentation SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  15. Plans, options & concerns • Plans • GOCDB interface / Direct routing (with GOCDB team) • Prototype Jan-2009 • Final Jun-2009 • Messaging as communication platform (with OAT) • Evaluation Mar-2009 • Standard defined Oct-2009 • VOMS interface (with VOMS team) May-2009 • Define and document new TPM role Apr-2009 SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  16. Plans, options & concerns • Options • Ticket distribution by origin of submitter • identify submitters’ region from DN • automatically assign ticket to ROC • TPM workload reduced further • Messaging for new interface or change also of old interfaces? • Move to the standard • TPM training for new role? • Yes • Concerns • Vagueness of EGI plans • Increase in interfaces • could be dealt with by strictly sticking to standard interface • promote federation of NGIs SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni

  17. Get and stay involved • USAG meeting • Monthly meetings usually on the last Thursday of the month • Participation from OCC,ROCs, VOs, … https://twiki.cern.ch/twiki/bin/view/EGEE/SA1_USAG • ‘Shopping list’ meeting • Sub-group of USAG • Weekly meeting to prioritise requests and define content of releases https://savannah.cern.ch/projects/esc/ WLCG Data Taking Readiness WS - CERN 13/11/2008 - Torsten Antoni

More Related