Title
| One network metric datastore to track them all: the OSG network metric service |
Author(s)
| Quick, Robert (Indiana U.) ; Babik, Marian (CERN) ; Fajardo, Edgar M (UC, San Diego) ; Gross, Kyle (Indiana U.) ; Hayashi, Soichi (Indiana U.) ; Krenz, Marina (Indiana U.) ; Lee, Thomas (Indiana U.) ; McKee, Shawn (Michigan U.) ; Pipes, Christopher (Indiana U.) ; Teige, Scott (Indiana U.) |
Publication
| 2017 |
Number of pages
| 8 |
In:
| J. Phys.: Conf. Ser. 898 (2017) 082044 |
In:
| 22nd International Conference on Computing in High Energy and Nuclear Physics, CHEP 2016, San Francisco, Usa, 10 - 14 Oct 2016, pp.082044 |
DOI
| 10.1088/1742-6596/898/8/082044
|
Subject category
| Computing and Computers |
Abstract
| The Open Science Grid (OSG) relies upon the network as a critical part of the distributed infrastructures it enables. In 2012, OSG added a new focus area in networking with a goal of becoming the primary source of network information for its members and collaborators. This includes gathering, organizing, and providing network metrics to guarantee effective network usage and prompt detection and resolution of any network issues, including connection failures, congestion, and traffic routing. In September of 2015, this service was deployed into the OSG production environment. We will report on the creation, implementation, testing, and deployment of the OSG Networking Service. Starting from organizing the deployment of perfSONAR toolkits within OSG and its partners, to the challenges of orchestrating regular testing between sites, to reliably gathering the resulting network metrics and making them available for users, virtual organizations, and higher level services, all aspects of implementation will be reviewed. In particular, several higher-level services were developed to bring the OSG network service to its full potential. These include a web-based mesh configuration system, which allows central scheduling and management of all the network tests performed by the instances; a set of probes to continually gather metrics from the remote instances and publish it to different sources; a central network datastore (esmond), which provides interfaces to access the network monitoring information in close to real time and historically (up to a year) giving the state of the tests; and a perfSONAR infrastructure monitor system, ensuring the current perfSONAR instances are correctly configured and operating as intended. We will also describe the challenges we encountered in ongoing operations of the network service and how we have evolved our procedures to address those challenges. Finally we will describe our plans for future extensions and improvements to the service. |
Copyright/License
| publication: (License: CC-BY-3.0) |