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.
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.
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.
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.
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.
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.
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.
Server Configuration 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.
Browser-based Setup
Once the Acceleratorvovserver has been started, you can view and manage it using your web browser.
Regulate Access to Accelerator
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.
Autostart Directory
With the command vovautostart, on vovserver startup, scripts can be specified to execute automatically.
Autostop Directory
With the command vovautostop, on vovserver shutdown, scripts can be specified to execute automatically.
Test Altair Accelerator
You may wish to run a few simple jobs to confirm that the system is running properly.