_qbupdateresource | _qbupdateresource | _qbupdateresource | _qbupdateresource | _qbupdateresource | _qbupdateresource
| Excerpt | ||
|---|---|---|
| ||
inform the supervisor of license usage counts from external license managers |
Description
qbupdateresource is used to inform the Supervisor of license usage counts from external license managers (FlexLM, RLM, MP, etc.). When Qube competes for licenses or other resources with an "external entity", (be that users or another queuing system), the Qube Supervisor can reconcile it's internal license or resource usage counts with the values retrieved from that license manager.
The Qube system administrator needs to write a script that runs on a periodic basis, queries the license server for the current usage, and if the license count has changed since the last time the script was run, calls qbupdateresources to inform the Supervisor of the new counts.
For example:
- you own 100 prman licenses
- Qube is configured to allow up to 100 prman job instances to be running at any one time by defining license.prman=100 (see Resource Tracking and License Resources).
All well and good, until end-users also start consuming prman licenses. Here's how this gets reconciled:
- Qube is currently running 60 job instances that are consuming a prman license (via the job being submitted with a reservation of license.prman=1 - see Job Reservations)
- The scripts gets the count from the external licenser server, and finds that now there are actually 80 prman licenses in use according to the prman license server. The script calls:
qbupdateresource --name license.prman=1 --total 100 --used 80
- The supervisor will then assume that there are 20 licenses in use by some external entity, will set the resource usage for
license.prmanto 80, and the only dispatch up to
Usage
Options
Notes
Examples
See also
NAME
qbupdateresource - sets the external resource values of the supervisor
...