The state of OSG resources includes the status, capabilities and configuration of those resources. As resources update software on independent schedules based on local preferences, version entropy ensues.
This document describes requirements for a tool to discover the configuration of the resources and get a realtime snapshot of the current state of OSG resources.
The health status of resources is reported to a central collector and packaged for display here
Capabilities of resources can be obtained from several sources, for example here
The configuration of a resource includes
are served by that resource,
it provides and the existence and version of any software installed on that resource.
Currently several tools partially address the need to determine the version of installed software. An internal GOC tool, currently unnamed and unsupported, produces XML
containing some version information. A similarly supported UC tool produces a table
containing OSG and VDT version numbers. The BDII information browser provides version information
for some installed software components but this service is likely to be deprecated in the future. Other sources of version information exist, for example, the CVMFS client version can be determined from the access logs on stratum 1 servers.
A need exists for a tool to discover the existence and version of installed software. This tool should:
- Automatically determine resources providing specific services
- Be configurable and flexible enough to determine the existence and version of a particular software package for resources providing a particular service. Packages currently of interest include (but are not limited to):
- OSG software stack
- VDT version
- CVMFS client version
- Have a light weight execution framework for use by multiple OSG Areas (Software, Operations, Security).
- Produce human and machine readable output summarizing the results.
- Create a minimal footprint on OSG resources.
- 23 Oct 2013
Topic revision: r2 - 23 Oct 2013 - 14:31:01 - RobQ