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.
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.
This is a usage guide for the Resource Data Service (RDS), an alternative service for managing License resources and
License-first scheduling in Accelerator.
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.
To ensure the correct and repeatable behavior of the tools, the environment must be controlled. This chapter explains
how VOV supports multiple reusable environments.
The UNIX utility crontab is used to perform regularly scheduled tasks such as retracing an entire project each night or storing a
back-up of the trace every Saturday. vovcrontab is a VOV utility that simplifies the creation of cron rules for a project. Directions are provided in this
section.
The program vovgetnetinfo is used with Accelerator and Monitor to fill in information about the hosts. vovgetnetinfo is to be run periodically from the scripts created by the vovcrontab command.
A utility related to vovgetnetinfo is vovinfo, which performs the same function as vovsh -s netinfo, but with a smaller binary. This binary can only get host and process information, and does not have Tcl/TK or
the VTK API.
This section describes how to use the command line and find all processes that are not currently managed by Accelerator. VOV can use a vovtasker to collect information about all processes from all hosts in a farm.
The vovselect command provides a way to retrieve specific data from the vovserver, with filtering done on the server side. This method is differs from some of the VTK calls, which get all data and
require processing on the client side to get the data of interest.
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.
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.
Run Periodic Tasks with vovliveness
If the directory "tasks" exist in the Server Working Directory, the server calls the vovliveness script once per minute.
Run Periodic Tasks with vovcrontab
The UNIX utility crontab is used to perform regularly scheduled tasks such as retracing an entire project each night or storing a back-up of the trace every Saturday. vovcrontab is a VOV utility that simplifies the creation of cron rules for a project. Directions are provided in this section.
vovgetnetinfo
The program vovgetnetinfo is used with Accelerator and Monitor to fill in information about the hosts. vovgetnetinfo is to be run periodically from the scripts created by the vovcrontab command.
vovinfo
A utility related to vovgetnetinfo is vovinfo, which performs the same function as vovsh -s netinfo, but with a smaller binary. This binary can only get host and process information, and does not have Tcl/TK or the VTK API.
Manage Processes
This section describes how to use the command line and find all processes that are not currently managed by Accelerator. VOV can use a vovtasker to collect information about all processes from all hosts in a farm.
Job Fostering
Job fostering is the processes of artificially consuming a job slot on a tasker in order to represent an externally running job or process.
Query the vovserver
The vovselect command provides a way to retrieve specific data from the vovserver, with filtering done on the server side. This method is differs from some of the VTK calls, which get all data and require processing on the client side to get the data of interest.