Global Grid User Support Global Grid User Support (GGUS) (GGUS)

Status and ProspectsStatus and ProspectsGDB-Meeting 2004-01-13

Rainer Kupsch GridKa Karlsruhe

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 2

Support in the Grid EnvironmentSupport in the Grid EnvironmentCern User Support (CUS)

Experiment integration? Solves deployment problems (LCG)

Experiment Specific User Support (ESUS) Solves experiment specific user problems

Grid Operations Centre (GOC) at RAL Monitoring, Security, Accounting of Grid Co-operates with system administrators Doesn‘t want direct contact with users

Global Grid User Support (GGUS) Solves Grid specific problems Co-operates with users Started with support for GridKa Users (2003-10-02) Interacts with CUS, ESUS and GOC

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 3

Objectives and Status of GGUSObjectives and Status of GGUS Uses a problem management tool (Remedy in FZK) to support problem

tracking (+)

Provides an entry point for GRID related questions and problems (FAQs) (+)

Provides Grid users with news, information on temporary problems, bottlenecks and down times (+)

Provides support for GRID users via web portal with secure access (+ ,-) Provides status & diagnostic information about GRID resources (+,-) Provides access to documentation and information (+) Builds an open knowledge base to optimize GRID-support (-) Provides support for CUS, ESUS and GOC (-) Interacts with CUS, ESUS, GOC and possibly local operations (-) Provides 7*24 hours support, therefore we have to find 2 partners in 2

different time zones (-)

+ : established - : to be established

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 4

To Do (1)To Do (1)

Integration of a universal Authentication and Authorization (A&A) system for internal use of GGUS-Portal for registered Grid users

Web access to non public areas via browser certificates with additional Authorization and user information (e.g. email, phone, experiment)

Therefore a (logical) central LDAP directory with a unique structure for A&A and for every VO has to be defined and established

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 5

To Do (2)To Do (2) Integration of Cern User Support (CUS),

GGUS could be first line of support Needed is at least one contact person from

CUS who feels responsible for: Review of GGUS Portal for the needs of CUS Characterization of the 2 CUS groups and integration in

our problem management tool for filtered problem transmission from GGUS to CUS

Delivery of information on deployment dates and news about CERN software to GGUS

Definition and implementation of interfaces and workflows between CUS tools and GGUS tools in co-operation with GOC

Making affected CERN users familiar with new procedures

First contact with Andrea Sciaba and Markus Schulz

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 6

To Do (3)To Do (3)Closer co-operation with GOC, system and

user related problems are transmitted from

GOC to GGUS Review of GGUS Portal for the needs (e.g.

problem categorization and escalation) of GOC Further definition of responsibilities (e.g. who

develops what kind of tools) Definition of interfaces and workflows between

existing GOC tools and GGUS tools Implementation and tests of the proposed

interfaces and workflows

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 7

To Do (4)To Do (4) Co-operation with Experiment Specific User Support

(ESUS) Groups, GGUS will be second line of support Needed is at least one contact person for each

experiment who feels responsible for: Review of GGUS Portal for the needs of ESUS Definition of responsibilities Definition of interfaces and workflows between ESUS

tools and GGUS tools Implementation and tests of the proposed interfaces

and workflows Training of ESUS people in new procedures Making experiment users familiar with new procedures

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 8

To Do (5)To Do (5) Integration of further Tier1 Centres,

GGUS first line of supportNeeded is at least one contact person for each

Tier1 who feels responsible for: Review of GGUS Portal for the needs of Tier1 Definition and implementation of interfaces

and workflows between Tier1 tools and GGUS tools in co-operation with GOC

Making Tier1 users familiar with new procedures

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 9

To Do (6.1)To Do (6.1)Finding 2 partners

in 2 different time zones

• First contact with Computing Centre, Academia Sinica, Taiwan

• potential partners: Fermilab in Batavia, Illinois, USA orSLAC in Stanford,

USA

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 10

To Do (6.2)To Do (6.2)

Co-operation with 2 partners

Concept and implementation for replication and distribution, world-wide universal access point to GGUS portal, single email address and phone number

Definition of responsibilities within GGUS portal Definition and implementation of failover

procedures

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 11

GGUS Team GGUS Team will be extended (hopefully) by 1 more person at 2004/07/01will be extended (hopefully) by 1 more person at 2004/07/01

Günter Grein, computer scientist support

Helmut Dres, geo physicistsupport

Roland Pietschmann, mathematiciancoordinator and instructor

Rainer Kupsch, GridKa GDB-Meeting 2004-01-13 12

Access and LinksAccess and Links

Support time:

Monday to Friday 8:00 am to 4:00 pm

Email: Support@ggus.org

Phone: 0049/(0)7247/82-8383

GGUS-Portal: Address: www.ggus.org

Link from www.gridka.de

User Access to non-public areas:

Login: gridka Password: ******