Jump to: navigation, search

PTP/designs/rm framework/LLview data access tool

llview_da, LLview data access tool


This tool is part of the new LLview modules of PTP displaying the status and the batch system usage of the remote system used from within PTP to run parallel programs.

llview_da extracts from the resource management system of the remote system information from the batch system and store it in a XML file in LML-Format. Depending on the availability and access rules following information will be obtained by llview_da:

  • nodes managed by batch system
  • batch jobs running and waiting in queues
  • information about reservation, rules for job-queue mapping and queue-node mapping
  • system state (failed components, ...)
  •  additional information, e.g. power usage,  I/O-throughput, ... (depending on system)  
  •  ...

llview_da is a (set of) Perl scripts which uses the standard batch system query functions to get the above described information. It depends on the access right given to the user's account under which llview_da is executed, which information could be obtained. 

For large system the queries could take a long time because information about ALL jobs and ALL nodes of the system are requested. To prevent an  overload of the batch system management daemons llview_da should be installed by system administrator and ran only in one instance on the system via crontab (e.g. one a minute).

The following sections will describe the LML-format created by llview_da, the internal structure of llview_da, the format of the input files needed to run llview_da, and some remarks about integrating it into PTP .

The LML format

LML is the XML format used to describe the machine status of the remote system. A more detailed description of that format can be found under: http://llview.zam.kfa-juelich.de/LML/OnlineDocumentation/lmldoc.html

The structure of LML is specified with a XML schema definition file which is also available on that web page. In addition, also a validation tool for LML is available which allows to check LML files during development of new system adapters. LML can be used to store different kind of data. llview_da uses the LML format in two steps. In the first step LML will be used to store information in raw format, including only objects and info-data elements.  In the second step the LML files will also have display  elements like tables and node displays containing the information in form which can directly be used by the view windows of the LLview client.

Structure of llview_da

The generation of the LML data is processed in a sequence of steps, executed by the main script llview_da.pl:

 ./llview_da.pl <config-file>

The main steps are the calling the driver scripts, combining the output files and generating of the LML intended to use by the llview client.


To support different types of batch systems llview_da has a general and batch system related layer:

  • driver scripts for Torque:
  • driver scripts for LoadLeveler:
  • driver scripts for BlueGene/P running Loadleveler:

  • ...      

Each of the driver scripts could are executed from llview_da.pl and collects typically one kind of data.  For example, ./TORQUE/da_jobs_info_LML.pl runs the torque utility 'qstat -f' to get information about running and queued jobs of all users.  Each script  will store the resulting data in a separate LML file, using LML objects and info-data elements.

Remark: An advantage of separating the queries to individual scripts is that they are simple to implement and adapt to other or newer version of batch systems. For supported batch-systems the script has to be adapted marginally, e.g. if the batch system is not installed in the default location. Also, if the batch system attributes are changed or added on a specific system, it could be adapted in the driver scripts directly. For this, each script contains at table defining the mapping between attribute names given by batch system and those accepted by LML.


Next, these LML output files of the driver scripts will be combined to one LML file. This will be done by the LMLcombiner, called from llview_da:

    ./LMLcombiner/LML_combine_obj.pl -o LML_rawfile.xml <files>

Depending on the system type the combiner will also combine or adjust attributes and check if all mandatory attributes for jobs and nodes are available.


In this step the LML file for the LLview client will be generated. This will be done by the LML2LML utility:

     ./LML2LML/LML2LML.pl -v -layout layout.xml -output LML_file.xml LML_rawfile.xml

This file will contain for each view a separate element, like <table> or <nodedisplay>.

Input Files of llview_da

There are two input files needed to process the LML data. The first one is the input file of llview_da.pl describing the steps which should be executed.
llview_da.pl can handle workflows described by steps and dependencies between those steps. A simple example is default configuration script for Torque, defining the thre main steps described above.


<!--- predefined vars: 
      $stepinfile                 # file in $tmpdir filename contains id of predecessor step
      $stepoutfile                # file in $tmpdir filename contains current id
  <var   key="tmpdir"        value="./LMLtmp" />              
  <var   key="permdir"       value="./LMLperm" />             

   id           = "getdata" 
   active       = "0"
   exec_after   = ""            
   type         = "execute" 
  <cmd exec="TORQUE/da_system_info_LML.pl               $tmpdir/sysinfo_LML.xml" />
  <cmd exec="TORQUE/da_jobs_info_LML.pl                 $tmpdir/jobs_LML.xml" />
  <cmd exec="TORQUE/da_nodes_info_LML.pl                $tmpdir/nodes_LML.xml" />

   id           = "combineLML" 
   active       = "1"
   exec_after   = "getdata"               
   type         = "execute" 
  <cmd exec="$instdir/LMLcombiner/LML_combine_obj.pl -dbdir $permdir/db -v -o $stepoutfile 
                                                            $tmpdir/nodes_LML.xml "

   id           = "genLML_std" 
   active       = "1"
   exec_after   = "combineLML"        
   type         = "execute" 
  <cmd exec="$instdir/LML2LML/LML2LML.pl -v -layout $permdir/layout_std.xml -output $stepoutfile $stepinfile" />

   id           = "cppermfile1" 
   active       = "1"
   exec_after   = "genLML_std"          
   type         = "execute" 
  <cmd exec="cp $stepinfile  $permdir/llview_LML.xml" />
  <cmd exec="/usr/bin/gzip -c -9 $stepinfile > $permdir/llview_LML.xml.gz" />


Due to the different call of the driver script this input file is batch system related. Therefore, a specific input file for each of the supported batch system is provided.
The advantage of describing the process of generating as a workflow is, that is allows to specify more complex workflows which stores for example the LML file directly on a web server, store the data in ahistory data base, or split the workflow in different part to execute some steps on another server.
A second input file is needed in the last step of the LML data generation (LML2LML). This input file (layout) describes the elements (tables, ...) which should be generated from the raw LMLdata.
The following short example shows the layout definition of a table, containing the list of running jobs. The layout definition itself is also defined according to the LML schema and will also be part of the resulting result LML file.

<tablelayout id="tl_RUN" gid="joblist_RUN">
 <column cid="1" pos="0" width="0.3" active="true" key="totalcores" />
 <column cid="2" pos="1" width="0.2" active="true" key="owner" />
 <column cid="3" pos="2" width="0.2" active="true" key="queue" />
 <column cid="4" pos="3" width="0.1" active="true" key="wall" />
 <column cid="5" pos="5" width="0.1" active="true" key="queuedate" />
 <column cid="6" pos="6" width="0.1" active="true" key="dispatchdate" />

For each batch system a default layout file is provided defining two tables (running and waiting jobs) and the node display. In future versions the layout definitions will be part of the request sent from the client to llview_da to support dynamic refinement of the view or selecting more table rows.

To display the nodes of the system (node display) LML2LML has to know the how the system is structured in sets of elements (e.g. in rack,nodes,cores, ...). This will be internally used to build a hierarchical data structures to storing these elements (tree). For some systems these structure is directly given, e.g. IBM Blue Gene/P and the position in the tree structure can obtained by evaluating the name of the  node. For other system, like clusters of SMP node, the arrangement of node into racks can typically not be obtained from the batch system information. Therefore LML2LML will accept besides the layout section of a node display also the scheme part of the node display, which describes the physical hierarchy of the system. If this scheme is given LML2LML will sort the nodes according this information into the tree. If the scheme is not specified (default), LML2LML will try to sort the nodes in a two-level tree, containing nodes in the first level and cores in the second level.

In the following example the scheme definition for a IBM Blue Gene/P is shown. In total, it spans up a tree of 6 levels.

      <el1 tagname="row" min="0" max="8" mask="R%01d">
          <el2 tagname="rack" min="0" max="7" mask="%01d">
              <el3 tagname="midplane" min="0" max="1" mask="-M%1d">
                  <el4 tagname="nodecard" min="0" max="15" mask="-N%02d">
                      <el5 tagname="computecard" min="4" max="35" mask="-C%02d">
                          <el6 tagname="core" min="0" max="3" mask="-%01d">

Modification needed to use within PTP

The integration/adaption of llview_da for PTP is planned as follows:

The Ressource manager UI for the control part will also provide an input field to specify the resource location of the LML data.
This location could be different:

  • If llview_da is installed by administrator and running under crontab control, the file will be typically available on a web server. In this case the resource location is an http- or https-address. The data could also be stored in file, residing on the remote system.
  • If llview_da is running in user space, it will be started under the control of control part of the resource manager. Then, the resource location will be the path to llview_da.pl on the remote system.

Especially in the second case, the control part should be responsible to transfer the LML data and/or call llview_da on the remote side, because the control part manages already a open connection to theremote side.
For future version of the LLview views inside PTP is also planed to integrate dynamic reloading of data to support level-detail and zoom function in the node display. Therfore, the connection to the LML resource has to support bi-directional transfer of (XML) data.

Internally, the LML2LML component of llview_da accepts as input files LML data containing layout section. The layout sections describes which elements (tables, nodedisplay, charts, ...) and in which level
of detail these elements should be included in the requested LML file. Currently, the layout is defined in a file residing in the installation directory of llview_da and defines some standard graphical elements , like tables for running and waiting jobs, and the nodedisplay. For future versions the layout definitions will be generated/modified by the LLview views and send as a request to the LML resource.  Depending on the kind of resource location, the transfer has to be implemented in different ways. For example, if llview_da.pl is directly called on the remote side, the data layout request could be send as a file to remote site.

This layout request structure could also be used to transfer the information about the batch system to llview_da. This information could the be used to select the corresponding input file for llview_da.  To support this, llview_da will be enhanced to read also layout request and extract the needed information from this data. And, if the resource manager has also information about the physical structure of the system, it could also be added to the request by using the nodedisplay scheme section.