Abstract
The Hawkeye Information Provider gathers Hawkeye data about Condor pool resources using the XML mapping of the GLUE schema and reports it to a GRAM4 service, which publishes it as resource properties. The official Condor site states the following:
Hawkeye utilizes the technologies already present in Condor and ClassAds to provide rich mechanisms for collecting, storing, and using information about computers. A Hawkeye system can be used to monitor various attributes of a collection of systems. The monitoring mechanism may also be used then to further the management of systems.
This information includes:
basic host data (name, ID)
processor information
memory size
OS name and version
file system data
processor load data
other basic Condor host data
You can download a PDF version of Hawkeye Information Provider information here.
Table of Contents
Table of Contents
The Hawkeye Information Provider gathers Hawkeye data about Condor pool resources using the XML mapping of the GLUE schema and reports it to a GRAM4 service, which publishes it as resource properties. The official Condor site states the following:
Hawkeye utilizes the technologies already present in Condor and ClassAds to provide rich mechanisms for collecting, storing, and using information about computers. A Hawkeye system can be used to monitor various attributes of a collection of systems. The monitoring mechanism may also be used then to further the management of systems.
This information includes:
basic host data (name, ID)
processor information
memory size
OS name and version
file system data
processor load data
other basic Condor host data
Features new in release 4.2.1:
This provider publishes information such as the following: basic host data (name, ID), processor information, memory size, OS name and version, file system data, processor load data, other basic Condor host data.
- There may currently be bugs for this information provider (see Bugzilla).
This information provider depends on the following GT components:
This information provider depends on the following 3rd party software:
- A working Perl installation
- A working Condor installation
Tested Platforms for this information provider:
- N/A
Tested containers for this information provider
- Java WS Core container
See Chapter 2, GT 4.2.1: Hawkeye Information Provider Reference for more information about this information provider.
Table of Contents
The Hawkeye Information Provider gathers Hawkeye data about Condor pool resources using the XML mapping of the GLUE schema and reports it to a GRAM4 service, which publishes it as resource properties. The official Condor site states the following:
Hawkeye utilizes the technologies already present in Condor and ClassAds to provide rich mechanisms for collecting, storing, and using information about computers. A Hawkeye system can be used to monitor various attributes of a collection of systems. The monitoring mechanism may also be used then to further the management of systems.
This information includes:
basic host data (name, ID)
processor information
memory size
OS name and version
file system data
processor load data
other basic Condor host data
This information provider is included in the GT4 toolkit and is used for reporting GLUE Computing Element (CE) information. The GLUE resource property (as used by GRAM) collects information from two sources: the scheduler and the cluster information system (for example Ganglia or Hawkeye). These will be merged to form a single output resource property in the GLUE schema.
The following configuration is required for this information provider:
This section describes configuring for use in GRAM. The scheduler does not need to be configured, as GRAM already knows the scheduler bundle to use through other means. GT4.0 comes with providers which collect data from two cluster monitoring systems: * Ganglia * Hawkeye These are configured in
$GLOBUS_LOCATION/etc/globus_wsrf_mds_usefulrp/gluerp.xmlTo collect data from Hawkeye, set the defaultProvider option in this file to:
<defaultProvider>shell /scratch/gt4b/I/libexec/globus-mds-cluster-hawkeye</defaultProvider>If no cluster monitoring in this file is available, set the defaultProvider as follows: (this is the way the toolkit comes as installed)
<defaultProvider>none</defaultProvider>
The data gathered is published as part of the GLUECE RP
General security considerations associated with the container and all MDS services apply. See: Aggregator Framework.
By default, the aggregator sources do not use authentication credentials -- they retrieve information using anonymous SSL authentication or no authentication at all, and thus retrieve only publicly-available information. If a user or administrator changes that configuration so that a service's aggregator source uses credentials to acquire non-privileged data, then that user or administrator must configure the service's aggregator sink to limit access to authorized users.