Home
Altair Allocator Administrators Guide
Allocator works in conjunction with license monitoring and workload scheduling solutions such as Monitor and Accelerator.
Resource Groups
The notion of a "resource group" in Allocator is useful when you have a resource that is derived from multiple sources.

Welcome
What's New
View new features for Allocator 2025.1.0.
Allocator Overview
Discover the available Altair Allocator guides.
Allocator Tutorials
Examine the Case Study for a complex Allocator example.
Altair Allocator Administrators Guide
Allocator works in conjunction with license monitoring and workload scheduling solutions such as Monitor and Accelerator.
- Introduction
  Allocator works in conjunction with license monitoring and workload scheduling solutions such as Monitor and Accelerator.
- Start, Stop and Monitor Allocator
- Sharing Licenses Across Multiple Sites
- Configure Allocator
  To configure Allocator, you need to create a file called config.tcl. This is the only file required for configuring Allocator.
- Allocator Procedures
  In this section, the procedures that may be used in the Allocator configuration file are described.
- Procedures Backward Compatibility
  The previous section described the procedures that may be used in the Allocator configuration file. The new procedures are under the Tcl namespace LA; they should be prefixed with LA::
- Allocator Usage Examples
  This section contains simple examples about using Allocator to solve common problems of sharing licenses between sites.
- Map Host Names
  In several points in the systems, it is useful to get the host name for a checkout, for a job, for a daemon, etc. Since every machine may be known by different names, it is important to provide the expert user with the ability to map host names to some canonical form of the host name.
- Resource Groups
  The notion of a "resource group" in Allocator is useful when you have a resource that is derived from multiple sources.
- Allocator and TIMEVAR
  To make the weights of Allocator change as a function of time, you can use the procedure TIMEVAR.
- Passive Mode
- License Overbooking
- Overbooking in Allocator
- Debugging
- View Allocation Details
- Multiple Queues
- PBS and Other Queues
  Allocator can allocate licenses across multiple schedulers, including Accelerator queues, PBS clusters and others. In this section we discuss how to integrate Allocator and PBS.

View All Altair Accelerator Help

Resource Groups

The notion of a "resource group" in Allocator is useful when you have a resource that is derived from multiple sources.

For example, you have some licenses of spice in India and some other license of the same spice in Russia, and you want to manage the aggregate of those license through Allocator.

Continuing the example, we are defining a resource group called "WAN:Spice" consisting of the two resources from the two servers, as follows:

#
# Fragment of vovlad/config.tcl 
#

LA::DefineResourceGroup "WAN:Spice" {
    #
    # Two components in this group.
    #
    LA::AddResource "India:spice"  FLEXLM/IN/spice ""
    LA::AddResource "Russia:spice" FLEXLM/RU/spice ""
}

This results in a resource map called "WAN:Spice" which is derived from the "OR'ing" of the licenses from India and the licenses from Russia, in addition to the individual resources called India:spice and Russia:spice.

By defining resource groups, Allocator can take into account the out-of-queue usage for the components when computing the allocation of the group.

It is possible to restrict distribution of a component to specific sites, such as geographically, by setting their weights to DO_NOT_SHARE.

#
# Fragment of vovlad/config.tcl 
#

LA::SetResourceWeight "RU" "India:spice" DO_NOT_SHARE