To regulate access to Accelerator, the security file vnc.swd/security.tcl must be edited. To deploy the changes after editing the file, Accelerator must be reset.
An important feature of Accelerator is job persistence. After a job completes, its information remains in vovserver's memory until the job is forgotten, manually or automatically.
The autoforget flag sets up a job to automatically be forgotten by the system after a certain time, (not including
suspension time) if and only if the job is done, failed, or idle. Jobs that are scheduled, running, suspended or transfer
are never autoforgotten.
vovserver configuration parameter values may be changed in a running vovserver using the CLI, or prior to the starting the server via the policy.tcl file. An administator can configure the parameters in the running vovserver using the vovservermgr command or the vtk_server_config procedure.
VOV and the jobs it runs depend on external resources such as available licenses, RAM, swap, tmp and disk space, which
may become exhausted, damaged or otherwise unavailable. When users are subject to disk quotas, writes may fail when
the disk is not completely full.
The job submission behavior of Accelerator or Accelerator Plus can be controlled by the file vnc_policy.tcl, which resides in the vovserver configuration directory.
The nc run command has built-in default features that include checking the validity of the run directory, enabling job
profiling, etc. This section describes how the Accelerator administrator can use the file $VOVDIR/local/vncrun.config.tcl to modify some defaults.
The overhead in the nc run commands consists mostly in the on-demand compilation of Tcl code and secondarily on the number of round-trips to
vovserver.
This section describes how the Accelerator administrator can use the file $VOVDIR/local/vnclist.config.tcl to modify some defaults for the nc list command. This file does not exist by default; it must be created when needed.
VOV issues an "alert" when an event requires attention. An alert can range from information that does not require
action to an urgent fault that requires immediate action.
An Access Control List (ACL) is a list of permissions that are attached to an object. The list defines who can access
the object (an agent) and what actions the agent can perform on the object.
The maximum number of clients - the combination of vovtaskers, user interfaces and proxies, that can be concurrently connected to a vovserver is limited by the number of file descriptors available.
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.
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.
The Introduction page provide an overview of the available
information. As indicated in the left column, menus and guidelines are available for
setting up and using the Accelerator features. More detailed
information and advanced methods are provided in this document in other
chapters. Figure 1.