Skip to content
Snippets Groups Projects
John-Paul Robinson's avatar
John-Paul Robinson authored
The policy file has both a LIST generation rule and a EXTERNAL LIST
consumer rule.  It uses the ESCAPE term to URL encode the ouput
generated by the LIST.
The external target script simply concats LIST files sent to it.
The mmapplypolicy command adds an additonal variable JOBID to
allow that to be passed as an OPT to the external script.
This let's us distinguish the ouput of one job from the next.
741ae650

Information Lifecycle Managment (ILM) via GPFS policy engine

The GPFS policy engine is well described in this white paper. A good presentation overview of the policy file is here. The relavent documentation is available from IBM.

This project focuses on scheduled execution of lifecyle policies.

A policy is executed via the run_job

submit-pol-job

Where:

outdir - the directory for the policy and job output, should be global to cluster policy - path to the policy file nodecount - number of nodes in the cluster that will run the policy corespernode - number of cores on each node to reserve partition - the partition used to submit the job

The policy run can be scheduled automatically with the cronwrapper script. Simpley add append the above script and arguments to the crownwrapper in a crontab line. For example to run it every morning at 4 am you would add:

0 4 * * * /path/to/cronwrapper submit-pol-job