1 / 3

ATF - WP7 - Status

ATF - WP7 - Status. 3 tools deployed on TB1 (CERN, NIKHEF, CNAF, CC-LYON, …) Pinger Iperf Udpmon Publication of network metrics in MDS LDAP backend delivered for pinger. ATF - WP7 - Dependencies. WP1 WP 7 must provide a network closeness function for resource broker CE <-> SE ?? WP 2

haile
Download Presentation

ATF - WP7 - Status

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. ATF - WP7 - Status • 3 tools deployed on TB1 (CERN, NIKHEF, CNAF, CC-LYON, …) • Pinger • Iperf • Udpmon • Publication of network metrics in MDS • LDAP backend delivered for pinger

  2. ATF - WP7 - Dependencies • WP1 • WP 7 must provide a network closeness function for resource broker • CE <-> SE ?? • WP 2 • WP 7 must provide a network closeness function for replica manager • SE <-> SE ?? • WP 3 • Provider of information for MDS / R-GMA • Consumer for MapCenter / NetSaint • Consumer for elaborated functions (closeness ?)

  3. ATF - WP7 - Vagueness • Provisioning • Streams identification (CE, SE, MS, RB, II, MDS….) • What is a SE (node, mass storage, service ??) • Traffic measurement issues (e.g. CERN) TB1 functional issues TB2 performances ?? • Presentation layer : metrics / availability • MapCenter • NetSaint • Usage of networks metrics • Publication to MDS, R-GMA ??? • WP1 (through II ?), WP2 • E.g. : networkcost (SE1, SE2, Filesize)

More Related