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.
A normal vovtasker has the privileges and limitations of the account in which it runs. When a normal vovtasker executes a command, the effect is the same as when the vovtasker's owner runs the command.
A tasker is characterized by several attributes. These attributes are controllable by means of the command line arguments
to the vovtasker binary as well as by means of the procedure vtk_tasker_define in the taskers.tcl configuration file for a VOV project.
For cases where the vovtaskers are started by submitting the binary to a separate batch queue system such as LSF or SGE, the system administrator
may decide to use vovagent, which is a special copy of the vovtasker binary.
vovtasker continuously logs 1 minute, 5 minute and 10 minute load averages of the machine where the tasker is running. Tasker load reports are available on the Tasker Load page.
Time-variant taskers resources can be configured using Tcl. Any procedure can be defined in the namespace VovResources and then used to compute the resource list.
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.
To ensure the correct and repeatable behavior of the tools, the environment must be controlled. This chapter explains
how VOV supports multiple reusable environments.
If a server crashes suddenly, VOV has the capability to start a replacement server on a pre-selected host. This capability
requires that the pre-selected host is configured as a failover server.
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.
UNIX User Impersonation
A normal vovtasker has the privileges and limitations of the account in which it runs. When a normal vovtasker executes a command, the effect is the same as when the vovtasker's owner runs the command.
vtk_tasker_define
There are many options that can be used with vtk_tasker_define and vtk_tasker_set_default.
Tasker Attributes
A tasker is characterized by several attributes. These attributes are controllable by means of the command line arguments to the vovtasker binary as well as by means of the procedure vtk_tasker_define in the taskers.tcl configuration file for a VOV project.
Manage Tasker Lists
A tasker list is a named, ordered list of taskers. Tasker lists can be used to enhance performance or restrict usage.
Tasker Health Checks
By default, the vovtasker does not perform many health checks. If the jobs can be executed successfully, that is normally enough of a check.
Configuration File for vovagent
For cases where the vovtaskers are started by submitting the binary to a separate batch queue system such as LSF or SGE, the system administrator may decide to use vovagent, which is a special copy of the vovtasker binary.
Tasker Load Reports vovtasker continuously logs 1 minute, 5 minute and 10 minute load averages of the machine where the tasker is running. Tasker load reports are available on the Tasker Load page.
Time-Variant Taskers
Time-variant taskers resources can be configured using Tcl. Any procedure can be defined in the namespace VovResources and then used to compute the resource list.
SGE Style Load Sensors vovtaskers also support SGE style load sensors. Use option -L in vovtasker/vovtaskerroot to define the command line for the load sensor.