Presentation is loading. Please wait.

Presentation is loading. Please wait.

Applications Requirements Working Group HENP Networking Meeting June 1-2, 2001 Participants Larry Price Steven Wallace (co-ch)

Similar presentations


Presentation on theme: "Applications Requirements Working Group HENP Networking Meeting June 1-2, 2001 Participants Larry Price Steven Wallace (co-ch)"— Presentation transcript:

1 Applications Requirements Working Group HENP Networking Meeting June 1-2, 2001 Participants Larry Price (co-ch)lprice@anl.gov Steven Wallace (co-ch) ssw@iu.edu Eric Myersmyers@umich.edu Doug Olsondlolson@lbl.gov Andy Kowalskikowalski@jlab.org Wade Hongxiong@physics.carleton.edu Mike Hannonhannon@physics.ucdavis.edu Ed Maymay@anl.gov Horst Severiniseverini@ou.edu Shawn McKeesmckee@umich.edu

2 What does HENP need to do with the network? Raw data storage and access Computation –Reconstruction –Monte Carlo –Theory Hierarchical distribution of data Physics analysis –Access to data objects –Independence of physicist location –Transparency of analysis resource location –Adaptability to changing resources and resource location Communication and conferencing Remote operation of experiments

3 Operational Requirements Bulk transfer –FTP type Guaranteed delivery on longer time scale –File system type (AFS, NFS,…) –Subscription data (via multicast?) –Protect other services from this –Scavenger service approach? Data Management –Transaction Processing Short term high rate Data Grids: remote access to data –Bulk transfer Requires resource scheduling –Bandwidth, start time, duration –User reconfiguration Guarantee bandwidth to match cpu allocated. Time scale 10-60 min Availability of information about the network –Characterize path between any two nodes –Object level data access –Metadata: access; updating –Transaction processing Be specific about time frames

4 Operational Requirements Remote control of experiments –Security! –Low latency, including effect of packet loss Look at ANL-MCS table –Reliability Remote conferencing –Low jitter –HENP needs this more than many fields: what part should we play in development? –Scheduling of resources Connectivity and local infrastructure –Minimum institutional requirements Depends on Tier level and other roles in experiment Bandwidth to workgroup/desktop –Specify required bandwidth to play as Tier 2, 3, 4 vs time Guarantees of service Use of advanced services and protocols –List the required services (jumbo frames?) –Flexibility as new services emerge Will be function of time

5 Operational Requirements Remote visualization and tele-immersion –Use to visualize system itself Worldwide HENP accounts/profiles –Access to home computing/storage resources –“Synchronization”

6 Network Requirements by Category Bandwidth –Transatlantic and transpacific –National backbones in US –Local Connections to backbone Campus issues Network Services –Information, monitoring, discovery about network characteristics and performance –Have control of the network parameters for a specific use Network Management –Cordinate across administrative domains Network Performance –Latency, jitter, packet loss –Instrument Tier 1, Tier 2 centers to monitor performance Available to NOC and users (or special users) Architecture –Single vs multiple I/O streams


Download ppt "Applications Requirements Working Group HENP Networking Meeting June 1-2, 2001 Participants Larry Price Steven Wallace (co-ch)"

Similar presentations


Ads by Google