vtk_tasker_define

There are many options that can be used with vtk_tasker_define and vtk_tasker_set_default.

Option	Argument	Description
-capabilities	`string`	The capabilities that the tasker has. This results in license checkout attempts for the specified capabilities. Possible values: FULL, NC, PROCINFO, NETINFO, EXEC, RT. FULL includes all capabilities. NC contains EXEC, PROCINFO and NETINFO capabilities. Altair Accelerator enables runtime tracing for FlowTracer. Default is FULL.
-capacity	`int`	The number of concurrent jobs (job slots) that the vovtasker can handle.
-cpus	`int`	The number of CPUs in the machine, without affecting maxload and capacity. On most platforms, the number of CPUs is computed automatically.
-CPUS	`int`	Convenience option, equivalent to setting -cpus, -maxload and -capacity at the same time. If N is the number of CPUs, this options sets -cpus to N, -maxload to N+0.5 and -capacity to N.
-coeff	`double`	The tasker coefficient. It is used as a divisor in computing the effective power of a vovtasker, e.g. a coefficient of 2.0 reduces the power by half.
-executable	`string`	The executable to use (default is vovtasker). For Accelerator, the default is vovtaskerroot.
-expiredate	`string`	Specifies the date and time after which the definition of this tasker is expired, and it cannot be started with vovtaskermgr command. The format of this parameter is year_month_day_hour_min_sec. Example: 2018_12_31_23_59_00
-failover		Passing this option will set the tasker's capacity to 0, which prevents the tasker from accepting jobs and pulling a license. This also acts as a flag to perform some failover configuration testing, such as checking servercandidates.tcl to make sure the tasker host is in the list, triggering a check to make sure the host has at least as many file descriptors as vovserver so it can operate at full capacity in the event of failover, and checking that the server_election directory is empty.
-host	`hostname`	The name to be used to connect to the vovserver (e.g. "localhost")
-indirect	`file`	Execute the jobs indirectly, using the Tasker* procedures described in the given file. This is used in indirect taskers.
-maxcapacity	`int`	The capacity of taskers can increase dynamically as a side effect of having suspended jobs. This limits the maximum capacity. The default value is twice the capacity.
-maxjobs	`int`	The maximum number of jobs a tasker can execute. Taskers will become suspended when the max is reached, and will exit once the last job is finished. Default: 0 (unlimited).
-maxidle	`timespec`	The maximum amount of time a tasker can be idle (having no jobs). Default: - (unlimited).
-maxlife	`timespec`	The maximum amount of time a tasker is allowed to run. Default: - (unlimited).
-maxload	`double`	The maximum load for the vovtasker. Above this, its power becomes zero, and the vovtasker does not accept new jobs until the load declines below this value. This helps avoid overloaded machines.
-message	`string`	Message to set on the vovtasker at startup. Should be brief.
-mindisk	`number`	Minimum disk space, in MB (for example, 100) or in percentage (0%-99%, for example, 10%) , on /usr/tmp below which the vovtasker will automatically be suspended.
-name	`string`	Name of the vovtasker. The default is the leaf name of the machine on which the vovtasker runs. May not contain the '.' (dot) character.
-nice	`int`	Run the tasker with niceness (reduced OS priority), for UNIX vovtasker only, ignored on Windows.
-power	`double`	The Tasker Power to be used for this vovtasker. The default for this is 0.0, which implies that the raw power is computed automatically upon startup. You can use this to make machines know to be identically- provisioned to have the same power.
-repeat	`int`	Number of identical vovtasker on a host (obsolete).
-reserve	`reserve expression`	Reserve the vovtasker upon startup. The argument is a . Example 1: `"-reserve /john/3w"` This means create a reservation for user john with a duration of three weeks at vovtasker startup. Example 2: `"-reserve memregr//4h"` This means create a reservation for group 'memregr' with a duration of 4h at vovtasker startup.
-resources	`string`	The tasker resources. This could be a list of literals like "bighost maingroup" or contain symbolic values like "@RAM@ @CPUS@". You must restart vovtaskers after changing values specified here. For a method that does not require restart, read about TaskerClass Table File.
-rshcmd	`string`	The command used to start a remote shell on the tasker machine. This is rsh by default, but it could be set, for example, to ssh. The known values for this option are: rsh, the default value ssh, the typical value vovtsd
-serverdir	`dir`	Explicit path to the server directory for the tasker.
-taskergroup	`group`	Define the taskergroup in taskers.tcl. Often this is used to group similarly-provisioned machines.
-update	`timespec`	The update cycle time (heart beat) of the vovtasker. The default value is 60s. You can use shorter values to cause resources to be updated more frequently when using resource procedures, being mindful of the CPU load this brings to the vovserver.
-vovdir	`dir`	Explicit path to the VOV installation for the tasker.
-vovtsdport	`port`	Port number to be used when connecting to the VOV tasker service daemon, vovtsd.