Home
Altair Accelerator Administrator Guide
Configure and manage the use of Accelerator after it is installed.
Resource Management
Altair Accelerator includes a subsystem for managing computing resources. This allows the design team to factor in various constraints regarding hardware and software resources, as well as site policy constraints.
License Sharing Support
With license sharing, the same license can be shared by multiple jobs. Depending on the policy selected by the vendor, there are licenses that can be shared among different jobs provided that some characteristics are the same, for example the execution host, the user or the display.

Welcome
What's New
View new features for Accelerator 2025.1.0.
Accelerator Overview
Discover the available Altair Accelerator guides.
Accelerator Tutorials
Discover Accelerator functionality with interactive tutorials.
Altair Accelerator User Guide
Basic tasks in Accelerator, including submitting jobs, tracking job information, and analyzing and solving common problems.
Altair Accelerator Administrator Guide
Configure and manage the use of Accelerator after it is installed.
- Use Accelerator Help
  Accelerator documentation is available in HTML and PDF format.
- Accelerator Quick Start
  Accelerator has two main commands, nc and ncmgr.
- Command Line Interface
- Quick Reference
- Accelerator Server and System Customization
- Start and Stop Accelerator
- Job Management
- Log Files
- Database
  Accelerator stores historical information about jobs in a relational database. As of version 2015.09, the database is fully integrated and managed as part of Accelerator. This section provides an overview of the components that run and manage the database.
- FairShare
- Jobclasses
- Preemption
  Preemption is the process of reserving or revoking resources from other jobs in order to help "important jobs" finish quickly.
- Resource Management
  Altair Accelerator includes a subsystem for managing computing resources. This allows the design team to factor in various constraints regarding hardware and software resources, as well as site policy constraints.
  - Hardware Resources
    All taskers offer a predefined set of hardware resources that can be requested by jobs.
  - Wildcard Tasker Resources
  - Resource Mapping
    As the vovservers determines which tasker is most suited to execute a particular job, it performs a mapping of the job resources, followed by a matching of the mapped resources.
  - Resources Representing the Sum of Others
  - Commas vs. ORs in Resources
  - Automatic Resource Limits
  - Resource Daemon Configuration
  - Manage Resources with the CLI
    vovresourcemgr is a utility for managing VOV resource maps. It may be used to create, modify, forget, and reserve resource maps.
  - Reconciliation Daemon Configuration
  - Add Resources
  - License-based Resources
    This section describes the Accelerator interface to Monitor, an application that monitors license servers and makes the in-use information available to Accelerator.
  - License Sharing Support
    With license sharing, the same license can be shared by multiple jobs. Depending on the policy selected by the vendor, there are licenses that can be shared among different jobs provided that some characteristics are the same, for example the execution host, the user or the display.
  - Automatic Setting of LM_LICENSE_FILE
    The capability described in this section is useful when the same license is provided by more than license server.
  - Limit Users
    Limiting users is typically not the best choice, as alternative approaches may be used to enforce policies without incurring low resource utilization issues. However, in some cases, limiting users may be the best solution and this section discusses several ways in which an administrator can limit the number of jobs that a user can run.
  - License Overbooking
  - License Overbooking in vovresourced
- Resource Management with RDS
  This is a usage guide for the Resource Data Service (RDS), an alternative service for managing License resources and License-first scheduling in Accelerator.
- Configure Container Integration
- Streaming Data Service
  The Streaming Data Service (SDS) publishes a time series data stream that can be consumed by existing Kafka systems and compatible reporting tools to monitor VOV projects.
- Environment Management
  To ensure the correct and repeatable behavior of the tools, the environment must be controlled. This chapter explains how VOV supports multiple reusable environments.
- Directories and Files
- Alerts and Notifications
- System Tasks
- Upgrade Accelerator
  This section provides instructions to change the software version on which Accelerator runs.
- Storage Aware Scheduling
  This daemon vovfilerd replaces older daemons like vovisilond, vovnetappd and vovregulatord. Also the utility vovfiler_setup is no longer needed. The visualization of the filer information is now done either via the vovfilerd.cgi page or via the utility vovfilerdgui.
- Frequently Asked Questions and Troubleshooting Tips
- Backwards Compatibility and Migrating from Previous Versions
  This chapter provides information about deprecated features that are still supported. This information is provided should you see older commands in use after a software upgrade or migrating to a newer Accelerator.

View All Altair Accelerator Help

License Sharing Support

With license sharing, the same license can be shared by multiple jobs. Depending on the policy selected by the vendor, there are licenses that can be shared among different jobs provided that some characteristics are the same, for example the execution host, the user or the display.

Host + User Sharing

With this type of sharing, if a user is already running a job on a machine, that same user is allowed to run any number of jobs on the same machine without consuming another license. This can be very advantageous for the end user especially when using machines with 8 or more CPUS.

This configuration is supported with two steps:

Define a jobclass for the jobs that should take advantage of license sharing.

# This is file   vnc.swd/jobclass/spectrerf.tcl
set classDescription "SpectreRF class"
set VOV_JOB_DESC(resources) "Share:spectrerf_[vtk_logname] OR License:spectreRF"

Add a procedure to resources.tcl to dynamically create the resource maps represent what licenses can be shared.
```
source $env(VOVDIR)/tcl/vtcl/vovsharedresourcesproc.tcl
# Configuration of the procedure for shared licenses.
SHRaddRule spectrerf  Share:spectrerf_@USER@
```