ggus operations model

EGEE-III INFSO-RI-222667

Enabling Grids for E-sciencE

www.eu-egee.org

EGEE and gLite are registered trademarks

GGUS Operations Model

Torsten Antoni

KIT-SCC

SA1 face-to-face meeting - Abingdon 03/12/2008 - Torsten Antoni 2



Outline

• GGUS operations model (technical)

• GGUS operations model (processes)

• Discussion




Outline



• Discussion




RC A

RC B

RC C

RC A

RC B

RC CROC CROC BROC N

RC A

RC B

RC C

TPM

VO Support CVO Support B

VO Support A

GGUS

Central

System

MiddlewareMiddleware

supportsupportMiddlewareMiddleware

supportsupportMiddlewareMiddleware

supportsupport

Deployment

supportMiddleware

supportDeployment

support

VO Support

CVO Support

BVO Support

A

Middleware

supportMiddleware

supportMiddleware

support

ROC CROC BROC N

Network Support

Network Support

ENOC/OPNOther GridsOther GridsOther Grids

Other GridsOther GridsOther Grids

CODCIC

Portal

GGUS operations model




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




Distributed model

GGUS

VO

cCOD

RC

ROCrCOD

rCOD

rCOD

rCOD

rCOD

rCOD

rCOD

Summarising the possible

scenarios in one sketch




Distributed model

GGUS

VO

cCOD

RC

ROC

rCOD

rCOD

rCOD

Current draft




Outline



• Discussion

WLCG Data Taking Readiness WS - CERN 13/11/2008 - Torsten Antoni 9



TPM+

VO SupportVO Support

UnitsROC

Support Units

Services Support Units

First Line Support

Middleware Support Units

Deployment Support Units

Network Support

Software Support Units

Other GridInfrastructures

External Support Units

Standard support workflow




ALARM Tickets TEAM Tickets

Ticket processing Alarming tier-1 site admins at any time (365*24*7)

Notifying tier-1 site admins; actions will only be taken during office hours

Possible submitters

„Alarmers“; these are 3-4 experts of each LHC VO

„Team“ members; these are a number of VO members with expertise

GGUS mail ALARM mails are signed with the GGUS certificate

Notification mails are not signed

Summary of ‘old’ new features




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)




Workflow for direct notification

• Will be available on the training system soon

Start End

07/11/2008V10 - Draft Guenter Grein

GGUS Direct USER Ticket Routing

Send notification mail

to site

Ticket routed to ROC

automatically

Site name specified?

yes

no

TPM routes ticket to ROC

Submit via web portal?

yes

no

Assign to TPM




Transition to EGI

RC

GGUS

RC

RC

NGI

RC

RC

ROC

EGEE NGIEGEE NGI




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




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




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

WLCG Data Taking Readiness WS - CERN 13/11/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/

ggus operations model

Documents