Changes in charge policies in Moab/MAM 9.1


Issue:  There were changes to the way charge policies are handled in Moab 9.1.  In Moab 9.0 and previous versions, you would tell Moab how you want jobs to be charged and it would pass that information to MAM.  In 9.1 Moab passes all relevant data about a job to MAM, which then has it's own configuration to control how the charge is handled.

 

Solution:  This example will show how to change a charge policy of DEBITALLBLOCKED to the equivalent with the new policies.

You would want to set the charge policy to ALL:

AMCFG[mam]  JOBCHARGEPOLICY ALL


This tells Moab to send details to MAM about all the resources that were used and blocked whether the job completed successfully or not. Once it's been received by MAM you can define how the job gets charged with a charge rate. You can tell MAM to charge for all blocked processor time like this:

mam-create-chargerate -n BlockedProcessors -x Type=Job? -z 1/s -d "1 credit per blocked processor second"


There is one thing to be mindful of. If you are upgrading this instance of MAM from an older version you will probably have an existing charge rate that looks for the number of processors. If you leave this in place your jobs will be over-charged. MAM will calculate the charge based on the number of processors blocked and then add a charge for the number used. To avoid this you would want to make sure you remove the old charge rate, which you should be able to do like this:

mam-delete-chargerate -n Processors

Tags: chargepolicy, chargerate, DEBITALLBLOCKED, DEBITALLCPU, DEBITALLPE, DEBITALLWC, DEBITSUCCESSFULBLOCKED, DEBITSUCCESSFULCPU, DEBITSUCCESSFULPE, DEBITSUCCESSFULWC
Last update:
2017-03-17 22:42
Author:
Ben Roberts
Revision:
1.0
Average rating:0 (0 Votes)

You cannot comment on this entry

Chuck Norris has counted to infinity. Twice.

Records in this category

Tags