service activity 1 operational issues jules wolfrat per oster

6
EGEE is a project funded by the European Union under contract IST-2003-508833 Service Activity 1 Operational issues Jules Wolfrat Per Oster NE ROC meeting October 28-29, 2004 www.eu-egee.org

Upload: ura

Post on 14-Jan-2016

19 views

Category:

Documents


0 download

DESCRIPTION

Service Activity 1 Operational issues Jules Wolfrat Per Oster. NE ROC meeting October 28-29, 2004. www.eu-egee.org. EGEE is a project funded by the European Union under contract IST-2003-508833. Mail lists. General SA1 list - open - project-egee-sa1cern.c h - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Service Activity 1 Operational issues Jules Wolfrat Per Oster

EGEE is a project funded by the European Union under contract IST-2003-508833

Service Activity 1Operational issues

Jules Wolfrat

Per Oster

NE ROC meeting October 28-29, 2004

www.eu-egee.org

Page 2: Service Activity 1 Operational issues Jules Wolfrat Per Oster

NE ROC meeting, October, 2004 - 2

Mail lists

• General SA1 list - open - project-egee-sa1cern.ch

• project-eu-egee-sa1 – general list – only ROC managers and SA1 managers can send e-mail – regional e-mail list are subscribed – for NE?

[email protected] – technical discussion list NE – subscribe by sending e-mail to "[email protected]" with "subscribe neroc-tech" in the body.

[email protected] – information list NL ROC - subscription request to Jules

Page 3: Service Activity 1 Operational issues Jules Wolfrat Per Oster

NE ROC meeting, October, 2004 - 3

Web site

• http://www.egee-ne.org/

Page 4: Service Activity 1 Operational issues Jules Wolfrat Per Oster

NE ROC meeting, October, 2004 - 4

Questions (Davide) (1)

• How can we share expertise for e.g. monitoring, or batch systems, or system/farm configurations? (w/ and w/o firewalls) But is everybody using the same tools? Probably not, not even within the same

region. Need inventory

• Many answers can be found (for LCG) in the LCG-ROLLOUT archives About 4000 messages in the last 10 months – can we consolidate? Another interesting (and probably less used) problem database is Savannah There are things that will not be answered, or fixed (e.g. because of dependencies,

people that left, politics, etc): what do we do in that case?

• Accounting: how is this currently done across the region?

Page 5: Service Activity 1 Operational issues Jules Wolfrat Per Oster

NE ROC meeting, October, 2004 - 5

Questions (Davide) (2)

• How does one keep current with e.g. pbs and maui? Good-will? Or should we explicitly suggest (at least within a region) to upgrade? A potential problem is to identify dependencies when we talk about upgrades to non-

middleware software (or even to middleware software, actually – GridKA had a good example)

Eventually, an issue for SLA

• Applications: do we care about what they do to our nodes? In theory, no. In practice, we may want to think about this But this is “Grid”™, so it may well involve extra-region considerations

• Future of the GOC? Need to make better use of the monitoring infrastructure soon Given the complexity of some problems, we can’t rely on reactive monitoring only – it

just doesn’t work well in a complex 24x7 environment

Page 6: Service Activity 1 Operational issues Jules Wolfrat Per Oster

NE ROC meeting, October, 2004 - 6

NEROC Support (Ron)

• How are we going to organise our local user and RC support? We are a distributed ROC, even distributed in Amsterdam

(SARA/NIKHEF). Are we going to implement a single user support application

accessible by everyone of us or not? What application are we going to use, RT, Remedy …? User support policies, can we have one policy for the region?