30 likes | 152 Vues
This document provides an overview of the current status of tools deployed under ATF WP7, including the Pinger, Iperf, and Udpmon on TB1 sites like CERN and NIKHEF. It details the publication of network metrics into the MDS and the delivery of an LDAP backend for the Pinger. It also outlines dependencies between work packages, emphasizing the necessity for WP7 to offer network closeness functions for resource brokers and replica managers. Furthermore, it addresses provisioning challenges, streams identification, and traffic measurement issues related to TB1 functionality and TB2 performances.
E N D
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 • 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 ?)
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)