SUPReMM module configuration guide
Ensure that Open XDMoD is installed and configured correctly and the shredder and ingestor scripts have been run successfully before installing and configuring the SUPReMM module.
Run Configuration Script
# xdmod-setup
There should be a new section titled “SUPReMM” in the list. Select that option to show the SUPReMM module configuration menu. The options in the menu are listed below:
Setup database
This option creates the necessary SUPReMM-module specific database schemas
and tables in the XDMoD datawarehouse. You will
need to provide the credentials for your MySQL root user, or another
user that has privileges to create databases. Two database schemas will be
created, modw_etl
and modw_supremm
. The database user that is
specified in your portal_settings.ini
will be granted access to these
databases.
In addition to the databases, the setup script will also install the necessary Node.js packages that are required. (The list of required packages can be found on the license notices page.) If you prefer to install these packages manually, you may do so with the following commands:
# cd /usr/share/xdmod/etl/js
# npm install
The script also prompts for the location of the document database that contains the job summary data. I.e. the mongodb instance. Enter the uri in the standard mongodb connection string format (see the mongo documentation for the syntax). You must specify the database name in the connection URI. If the database is not specifed then the mongo driver defaults to the ‘test’ database, which will not contain the job summary data.
Configure resources
The setup script automatically detects the resources that exist in the XDMoD datawarehouse and lists them. If no “Edit resource” options show in the list then quit the setup and complete the steps listed in the shredder and ingestor guides before re-running the setup script.
By default all the resources are disabled. You must select the “Edit resource” option for each resource that you wish to configure to appear in the SUPReMM realm and follow the prompt to enable the resource and set the correct options. The “Dataset mapping” should be set to pcp if processing job summaries generated from PCP data.
SUPReMM configuration files
The SUPReMM module configuration files are located in the etc
directory of
the installation prefix or /etc/xdmod
for the RPM distribution.
supremm_resources.json
Defines all of the resources that have SUPReMM data that will be ingested and
displayed in XDMoD. Each object in the array represents the configuration for a
single resource. All resources listed in this file must also have entries in
the resources.json
and resource_specs.json
main configuration files
(described in the main configuration guide).
{
"resources": [
{
"resource": "resource1",
"resource_id": 1,
"enabled": true,
"datasetmap": "pcp",
"hardware": {
"gpfs": ""
}
}
]
}
The value of the resource
parameter should be identical to the resource
parameter in the resources.json
main configuration file.
The value of the resource_id
must be the id of the resource in the XDMoD
datawarehouse. This value is obtained automatically by the interactive setup
script. It can be manually obtained by running the following SQL query:
mysql> SELECT id FROM `modw`.`resourcefact` WHERE code = "%resource%";
where %resource%
should be replaced with the resource
parameter from the
resources.json
main configuration file.
The datasetmap
option allows the ingestion of SUPReMM data from different
data sources. Currently PCP is the only supported data source.
The hardware
property is used by the dataset mapping code to process PCP
metrics that have device-specific names. The only configurable mapping
in this release is the name of the GPFS mount point. If the resource has
a GPFS filesystem then set hardware.gpfs
to the name of the GPFS mount point.
Set this to an empty string if there is no GPFS filesystem for the resource.
portal_settings.d/supremm.ini
Contains the configuration settings to allow XDMoD to connect to the job summary document database. The only supported db_engine is MongoDB.
[jobsummarydb]
db_engine = "MongoDB"
uri = "mongodb://localhost:27017/supremm"
db = "supremm"
The uri syntax is described in the mongo documentation. You must specify the database name in the connection URI. If the database is not specifed then the mongo driver defaults to the ‘test’ database, which will not contain the job summary data.
Advanced Configuration Options
The resource configuration file supremm_resources.json
has optional advanced
configuration settings for each resource.
The $.resources[*].collection
option overrides the collection name in the
MongoDB. This option can be used to set a non default collection name.
The $.resources[*].db
option specifies the name of the section in the
portal_settings file that contains the database configuration settings. This
setting can be used to support an XDMoD instance ingesting data from multiple
MongoDB databases.