(Click to open topic with navigation)
Some sites may want to use Moab Accounting Manager to calculate and record charges, but not to impose allocation limits or prevent any workload from running. With notional charging, charge rates will be used to calculate a cost for using resources, but there is no need to make deposits, debit funds or keep track of allocation limits. Although it would be possible to set up accounts and assign users to specific accounts, this chapter will assume that account membership is not going to be enforced. If you would prefer to enforce account membership, you can continue to use the notional charging accounting setup as described in this chapter, but you will need to additionally define accounts and account memberships as well as configure Moab to synchronize account information from Moab Accounting Manager as described in Chapter 5 Fast Allocation Setup Guide. Liens, balance queries and quotes are not needed. Our main task is to define charge rates.
At the end of a job, Moab Workload Manager will send usage information to the accounting manager. Moab Accounting Manager will calculate a charge and store this with the job usage record.
You will need to be a Moab Accounting Manager System Administrator to perform many of the tasks in this chapter. It is assumed that you have already installed Moab Workload Manager and installed, bootstrapped, and started Moab Accounting Manager before performing the steps discussed in this chapter.
For testing or demo purposes, an initialization script is available that provides a similar affect to running the example commands in this chapter to minimally set up MAM for the notional-charging accounting mode with a small amount of dummy sample data. It will not perform the Moab configuration steps described in this chapter. It can be cleaned up by running the hpc-cleanup.sh script.
$ ./hpc-notional-charging.sh