LHCOPN The Optical Private Network for the Large Hadron Collider

1
LHCOPN The Optical Private Network for the
Large Hadron Collider
Kors Bos NIKHEF, Amsterdam
2
Tier-1
Tier-1
Tier-1
Tier-1
Experiment computing models define specific data
flows between Tier-1s and Tier-2s
3
ATLAS average Tier-1 Data Flow (2008)
Tape
Real data storage, reprocessing and distribution
Tier-0
diskbuffer
CPUfarm
Plus simulation analysis data flow
diskstorage
4
ALICE data transfers
5
(No Transcript)
6
Data Distribution TestsTier-0?Tier-1s

• Disk to disk
• July 2005 600 MB/sec
• January 2006 1 GB/sec
• April 16 2006 1.6 GB/sec

7
Goal reached on Easter Sunday
Easter w/e
Target 10 day period
8
(No Transcript)
9
LHCOPN Architecture
10
LHCOPN Architecture
11
LHCOPN Architecture
12
Geant2 footprint
13
FARMS
Computer Center Network Topology
Internet
WHO
C3
C4
C5
LC3
LC4
GPN
sw6506-isp
LV1
BB3
BB4
BB13
RB14
rci76-1
V1
C2
BB12
RB4
RB5
BL3
RL4
BL4
BL7
RB3
cernh2
LB1
RL3
BB2
RB13
FIREWALL
V2
C1
BB11
rci72-4
RB2
rca80-1
RB12
gate3
RL7
BB1
cernh8
PG1
BC1
BC2
B513-E
rca80-2
PL1
rci65-3
rci76-2
PG2
E513-E
EXT
SG1
gate-bkup
LB2
BL1
BL2
RL2
RL1
SL1
BB1
BB2
LC1
LC2
Meyrin
CNIC
LCG
T513
IB1
BT15
BB5
2-S
RB6
CCR-513
Prevessin
IB2
BB7
BB6
T874
RB8
10-1
887-R
RB7
CCC-874
BB9
BB8
RB10
BB10
RB11
RB9
LHC
Tier1s
40-S
376-R
874-R
TN
14
(No Transcript)
15
ESNET/I2 IP
UltraLight Router
US T2s
Canada
Taipei
NetherLight
US LHCNet
ManLan
BNL
VCAT/LCAS
European T1s
CERN
European T2s
Starlight
FNAL
NREN/GN2 IP
US T1s
16
OPN Status Summary
17
CBF Status Summary
Other Links Summary
18
Organisation

• LHCOPN Meetings 4 times a year
• Organised as a sub-activity of the GDB
• Current Working groups
• Operations (Dante)
• Monitoring (USA)
• Routing (CERN)
• Security (UK)
• Working group evolution
• Routing will become a long term technical body
• Monitoring will evolve to become more technical
  network management including tool selection and
  deployment
• Operations will continue to be the problem
  determination and resolution
• Security will continue to be an advisory and
  policy body.

19
Operational Status

• Several links in production but coherent
  operational management across organisational
  domains must be organised.
• Agreement has been reached to deploy one initial
  monitoring tool Perfsonar across all domains.
• Workshops have been held (Dante)
• Munich 19 July 06 DANTE, DFN, REDIRIS, GARR,
  SURFnet, NORDUnet, RENATER, CERN (and LRZ-Munich)
• Toronto 18-19 September 06 DANTE, I2, ESnet,
  TRIUMF, Canarie, FNAL, USLHCNET
• End-to-End coordination unit (E2ECU) being
  implemented by Dante as part of the overall NOC
  Full Operation January 2007.
• ENOC providing information integration with Grid
  Operations (EGEE-SA2) working closely with E2ECU
• All operational information documented on the
  LHCOPN Twiki http//lhcopn.cern.ch

20
Current Monitoring Activities

• VCs every two weeks to discuss progress, issues
  and timetable for e2e monitoring data being made
  available
• CNAF-CERN (T1-T0) monitored e2e
• CNAF-GRIDKa (T1-T1) partly done
• Most EU NRENs expect to be ready before end of
  2006
• Non-EU networks TBC

21
Perfsonar Status
22
Ongoing Activities

• LHCOPN Meeting will continue (frequency is every
  3-4 months)
• Need to provide advice on performance tests to
  T2s that prove to be inadequate.
• Evolution towards long term support is ongoing
• Long term technical working group
• E2ECU and ENOC functions

23
Risks/Uncertainties

• Network infrastructure for LHC relies on multiple
  funding sources
• CERN (LCG), EU (GEANT), DOE( USLHCNET, ESNET),
  NSF (Internet2), Governments (NRENS)
• Data Models presented (MegaTable) fit with the
  physical infrastructures so far, but are they
  right?
• NOC infrastructures are not strictly 24x7 so we
  will rely on backup strategies for outages.

24
The End