Transcript The ENOC When, Who, What?

Enabling Grids for E-sciencE
The ENOC
When, Who, What?
Mathieu Goutelle (EGEE-SA2) – CNRS UREC (FR)
[email protected]
T0/T1 meeting – Amsterdam, 2006-01-31
www.eu-egee.org
INFSO-RI-508833
Outline
Enabling Grids for E-sciencE
• Why the ENOC?
• How does it work?
– Support model in EGEE,
– The network support,
– The interface with providers NOCs.
•
•
•
•
The ENOC in EGEE,
The ENOC in EGEE-II,
The ENOC and LCG?
Conclusion
INFSO-RI-508833
T0/T1 meeting – Amsterdam, 2006-01-31
2
The roots in a nutshell
Enabling Grids for E-sciencE
• EGEE Technical Annex:
“The operational management of EGEE must integrate seamlessly
with the operations of the existing GEANT and NRENs. […] The
interfaces between the Grid operations centres and the network
operations centres are critical.”
• EGEE needed an interface with networks:
– To contact the networks ;
– To be contacted by the networks ;
• The ENOC:
– Operational interface between EGEE and the networks involved
in the infrastructures (mainly, but not limited to, NRENs):
 Support unit for grid users for all network related issues,
 Point of contact for a NOC to provide operational information (TT)
and contact EGEE for operational issues,
 Handle SLA installations.
INFSO-RI-508833
T0/T1 meeting – Amsterdam, 2006-01-31
3
The Support Model in EGEE
Enabling Grids for E-sciencE
The support model in EGEE can be described as
“Regional Support with Central Coordination"
The ROCs and
VOs and the
other project
wide groups such
as the Core
Infrastructure
Center (CIC),
middleware
groups (JRA),
network groups
(NA), service
groups (SA) are
connected via a
central
integration
platform provided
byCourtesy
GGUS. of
RC 1
RC X
RC 1
…
RC X
RC 1
…
RC X
DS 1
ROC 1
Operations
Support
TPM
Network
Support
Ian Bird (EGEE-SA1)
INFSO-RI-508833
…
ROC…
…
ROC 12
DS 5
Deployment
Support
Central
Application
(GGUS)
MS 1
Middleware
Support
VO
Support
…
MS 8
ALICE BIOMED ESR
…..
Interface
Webportal
T0/T1 meeting – Amsterdam, 2006-01-31
4
Support Workflow
Enabling Grids for E-sciencE
Courtesy of
Ian Bird (EGEE-SA1)
Mail to
[email protected]
g
For general Grid problems: beginners,
Operations, Deployment, etc.
Automatic
Ticket Creation
TPM
- Solves
- Classifies
- Monitors
Central GGUS
Application
VO Support
ROC
Operations Middleware Deployment
Units
Support Units
Support Support Units Support Units
INFSO-RI-508833
Network
Support
T0/T1 meeting – Amsterdam, 2006-01-31
5
Troubleshooting workflow
Enabling Grids for E-sciencE
Problem
problem
assignment
essiment
ENOC
TTM
Feedback
Feedback
Problem
Problem
signalisation
signalling
NOC B
USER
PERT
Problem
resolution
failure
RC
NREN A
GEANT
NREN B
RC
TTM: Trouble Ticket manager
ENOC: EGEE Network Operation Center
INFSO-RI-508833
T0/T1 meeting – Amsterdam, 2006-01-31
6
GGUS Portal: user services
Enabling Grids for E-sciencE
Browseable tickets
Search through solved tickets
Useful links (Wiki FAQ)
Latest News
GGUS Search Engine
Updated documentation (Wiki FAQ)
Courtesy of
Ian Bird (EGEE-SA1)
INFSO-RI-508833
T0/T1 meeting – Amsterdam, 2006-01-31
7
GEANT/NRENs notification handling
Enabling Grids for E-sciencE
E-mail notifications
NREN
GEANT
NREN
NREN
Handling
Procedure
ENOC
Filtering
Impact on the grid
TTS
INFSO-RI-508833
Create an
assigned ticket
T0/T1 meeting – Amsterdam, 2006-01-31
8
The ENOC in EGEE
Enabling Grids for E-sciencE
• Only a model…
– A trial has “proven” that the processes work,
– The trial still continue: the ENOC is currently alive but on a best
effort basis:
 Extension to more NRENs (3 now, 4 soon),
 Not staffed during the lifetime of EGEE,
– Integration in the whole support structure
 Integration in GGUS,
 Integration in the “grid” support.
– Software development:
 Filtering tool seems OK,
 Needs for other tools (monitoring): ongoing work.
• To be ready for EGEE-II!
INFSO-RI-508833
T0/T1 meeting – Amsterdam, 2006-01-31
9
The ENOC in EGEE-II
Enabling Grids for E-sciencE
• Staffed right from the beginning:
– 2 FTE in EGEE-II (SA2) dedicated to the ENOC,
– Monday to Friday, 9h-17h service,
– Hosted at CC-IN2P3 (Lyon, France).
• Schedule:
– Start of EGEE-II: April 2006,
– ENOC “operational”: foreseen end of May 2006 (MSA2.1).
• Future Work:
– TT normalization and distribution,
– Largely outside the context and scope of EGEE…
– … but NRENs seem very interested in putting efforts in such an
action, also for their own interest (inter-domain operational
management).
INFSO-RI-508833
T0/T1 meeting – Amsterdam, 2006-01-31
10
The ENOC and LCG
Enabling Grids for E-sciencE
• From the discussion, LCG needs for the LHC-OPN
something similar to the ENOC:
– Small team supervising the network,
– Point of contact for LCG to the networks,
– Operational interface with the network.
• Why duplicating things?
– LCG and EGEE share GGUS: network related tickets will be
assigned to ENOC even when coming from LCG users,
– ENOC hosted in a Tier-1,
– EGEE/LCG separation always a little blurred…
• What ENOC misses?
– A tool to monitor the OPN: PerfSonar may provide the data,
– Contacts with the NOCs (no difference between Europe and
others),
– Maybe, extra staff if needed…
INFSO-RI-508833
T0/T1 meeting – Amsterdam, 2006-01-31
11
Conclusion
Enabling Grids for E-sciencE
• Avoid duplicating things:
– If EGEE and LCG share the same model, why not sharing the same
team?
– Looks like a good story to tell about projects concertation…
• EGEE future? (quote from the EGEE-II ESR):
“EGEE−II will pave the way for a long−term sustainable Grid infrastructure to
ensure the resources and knowledge developed during EGEE and EGEE−II
are available to researchers in Europe and beyond in years to come.”
• Operational issue:
– ENOC needs to be operational,
– The monitoring tool are an issue that can prevent the ENOC to handle
the OPN,
– No problem with non-European lightpaths: no difference regarding the
procedures for European IP networks!
• Questions?
INFSO-RI-508833
T0/T1 meeting – Amsterdam, 2006-01-31
12