The PHP scripts providing the web-based GridMonitor GUI are configured using
the configuration file
This file holds an array in PHP syntax, defining all
configurable GridMonitor GUI parameters.
Comments are marked, as usual in PHP, with
// (until end of line) or with
The basic configuration section defines information about known collectors and therefore known clusters:
$Cluster = array ( (1) 'Cluster1' => array ( (2) 'pscollector' => array( 'server' => 'localhost', (3) 'port' => 4000 (4) ), 'PhView' => &$PhView_Cluster1, (5) … ), //'Cluster2' => array ( (6) // 'pscollector' => array( // 'server' => 'frontend2', (7) // 'port' => 4000 (8) // ), // 'PhView' => &$PhView_Cluster2, (9) // … //), );
Example 4.24. Basic cluster configuration for the GridMonitor GUI
This defines a list of known Clusters
having an entry for cluster
How to connect to the related collector is
pscollector, using the node
and TCP port
Most of the parameter info is read from the collector at startup, utilizing the parameter type subsystem of the collector. Therefore, only parameters local to the PHP scripts have to be defined at this place.
To add a second cluster, e.g.
uncomment or copy the
appropriate lines and modify the cluster name
server name ('
The TCP port ('
will most probably be the same.
the cluster name has to match the configured cluster name in the collector configuration file!
defines the physical
outline of the cluster, specifying how many racks, how many nodes
per rack and how many blades per blade chassis are installed.
This may be adjusted to match the actual cluster layout.
For more information, refer to the section called “Configuring GridMonitor GUI physical view”.
As mentioned in the previous section, the variable
PhView (5) within the cluster configuration (see the section called “Configuring the graphical user interface (GridMonitor GUI)”) refers to an array describing the
physical outline of the cluster.
$PhView_Cluster1 = array( 'Cluster1' => array( (1) 'row' => 1, 'uw' => 130, (2) 'uh' => 14, (3) 'free' => array('h' => 1, 't' => 'skip'), (4) 'blade01' => array( (5) 'h' => 6, 't' => 'Blade', (6) 'n' => array( (7) 'w' => 10, (8) 'skip' => array('h' => 1, 't' => 'skip'), (9) 'bnode-001' => array('h' => 1, 't' => 'Node'), (10) 'bnode-002' => array('h' => 1, 't' => 'Node'), … ), ), 'node-01' => array('h' => 2, 't' => 'skip'), (11) 'node-02' => array('h' => 2, 't' => 'skip'), … 'localhost' => array('h' => 2, 't' => 'Node'), (12) 'Switch-1' => array('h' => 1, 't' => 'Switch'), (13) ), );
Example 4.25. Configuring the physical cluster view for the GridMonitor GUI
The array variable
defines a single rack called
If more than a single rack is used, the array
Cluster1 must be duplicated and more
reasonable names like
Rack2, etc. should be used.
These names will also show up in the pull-down menu of the left hand navigation
area of the physical view page.
See also the section called “GridMonitor GUI: Cluster physical view page”.
The next entry (5) of type 'blade' represents a blade
chassis (holding vertical slots)
with a height of 6 units
defines the slots within the blade chassis.
Each slot is 10 pixels wide
The first slot
is empty ('skip').
The following slots
are filled with nodes
Unused entries ('skip') of height 2 ('h') are defined in
Whereas (12) defines a node entry
localhost ('Node') of height 2 ('h').
The last entry
defines a switch entry
('Switch') of height 1 ('h').
If an entry is marked as type node (
as switch (
'Switch'), the entry name equals
the node or switch name. Both types are animated showing their
current state using different colors.
Entries with type skip
'skip') are drawn, but not animated.
The height of each rack is computed automatically. Empty
space may be inserted using entries of type
'skip'. Multiple racks may be defined
within the array variable
To minimize typing, the scripts
are provided, located in
These scripts generate a prototype physical configuration
for typical server or blade racks by using information on how
many nodes are installed, how many nodes per rack are
installed, what size these nodes are, etc.
The output of these scripts may be saved into a file and
modified to suit the current physical layout.
A number of default values for the GridMonitor GUI can be configured for
each cluster independently using the array variable
.defaults within the global array
$Cluster, located in the file
$Cluster = array( 'Cluster1' => array( … '.defaults' => array( /* default icon state */ 'Match' => 'All', (1) /* default time frame */ 'Last' => 'hour', (2) /* default sort order */ 'Sort' => 'desc', (3) /* event groups ignored in cluster overview */ 'IgnoredEvents' => array( (4) 'default' => true, 'ok' => true, ), /* number of icons per line in cluster overview */ 'NbrOfIconsPerRow' => 10, (5) /* list of pre-defined rack views, */ /* e.g. 'Left' => 'rack0:rack1' */ 'PhView' => array( (6) ), /* default diagram size */ 'DiagramSize' => 'medium', (7) /* list of known PBS queues, */ /* e.g. 'large' => 'large' */ 'QueueList' => array( (8) ), ), … ), );
Example 4.26. Configuring default values for GridMonitor GUI
Match (1) defines
the default icons state shown when displaying the cluster
Valid entries are
none to suppress icons entirely,
all to show all icons,
idle to show icons for idle nodes only,
in use to show icons for nodes in use
ev.pnd to show icons for nodes having
dead to show icons for unavailable nodes
ev+de to show icons for nodes having
pending events and also unavailable nodes.
Last (2) defines
the default time frame for history charts and event lists.
Valid entries are
Sort entry (3) indicates
whether lists are sorted ascending (
or descending (
desc) by default.
IgnoreEvents (4) lists all
events which should not show up in the cluster overview event
With the variable
NbrOfIconsPerRow (5) the number
of icons per line within the cluster overview icon area is
PhView (6) defines
lists of racks selectable as groups within the
Physical view cluster page.
Each array entry consists of a label and a colon-separated
list of rack names, which are configured in the
See the section called “Configuring GridMonitor GUI physical view”, for details.
All particular rack entries configured within the physical view configuration (see the section called “Configuring GridMonitor GUI physical view” are selectable by default and should not be configured within this array.
DiagramSize (7) specifies
the default size of diagrams within the Diagram page.
Valid entries are
The array variable
QueueList (8) lists all
queues of a PBS batch queuing system. See also the section called “Configuring the collector – step by step” for information on how to
configure a PBS server.
The GridMonitor GUI displays small pictures of all configured
clusters within the left hand navigation area.
To show actual pictures of the systems, copy image files named
like the configured clusters to the default installation
The pictures are automatically scaled by the browser, but
for best results the picture size should be 180x120 pixels.
The pictures may be encoded as GIF using the filename suffix
.gif, as JPEG with suffix
.jpg or as PNG with suffix
Do not overwrite the default file
Cluster.jpg, otherwise the picture will
not link to the particular cluster, but to this section of