Skip to content

Execution Profiles

An Execution Profile is required to run any workload on a worker node in the Altair SLC Hub cluster. A profile can be used to limit the worker nodes on which that workload is executed by specifying constraints and resource config groups. An execution profile can be used to control:

  • Access to specific worker nodes.
    For example to determine which nodes are used to execute production or development workloads.
  • The required operating system.
  • The minimum resource requirements that must be met to begin execution.

If an execution profile specifies no constraints, a workload that uses the profile can run on any node in the cluster. Constraining where a workload can run will enable efficient use of hub resources and balancing of workloads throughout all available nodes.

Execution profiles can be constrained to run on worker nodes through the use of labels or operating system requirements. Additionally, defining a resource requirements config groups or specifying Altair SLC system option through an SLC config group can further constrain where a workload can run when started with a given profile.

Setup guide

Instruction for setting up an Execution Profile can be found in the configuration section.

In the Execution Profiles page, you can filter the listing by name, and order the list of profiles using the date created or modified columns.

Clicking more (...) to the right of each execution profile enables the deletion or renaming of an existing profile.

Execution Profiles and Namespaces

When first defined, an execution profile is a global entity, which means the profile is not defined within a namespace. To use an execution profile, you must specify a namespace binding in the execution profile configuration.

A profile can be bound to one or more namespaces, and a profile can be specified as the default for a namespace. Normal access control rules apply to use the execution profile. That is, a successful access control check to the profile is required for that user. Creating this binding enables use of the execution profile for workloads such as pipelines in that namespace.