2016.09 Release Notes

Logical "or" operations in selection rules are available via the | operator.

Logical operations may be grouped with parentheses.

AND operations always take precedence over OR operations in the absence of parentheses.

The words and, or and not can now be used in place of &, | and ! respectively; this makes shell-level scripting easier. These words are case-insensitive; they may also be typed as AND, OR and NOT.

The = operator is now supported, which is equivalent to the == operator.

Spaces are now allowed in non-quoted string values if they are preceded by a backslash '\' character. Example: command^sleep\ 60 is now a valid rule.

To send 16-bit integer, packing size is changed from 8 bytes to 3 bytes. to send 32-bit integer, packing size is changed from 8 bytes to 5 bytes.

To send 64bit integer, packing size is changed from 16 bytes to 10 bytes.

By removing 4-byte alignment packing and reducing data type encoding method, encoding of string and double types is also more efficient.

 vovsh -x &vtk_server_config liverecorder.logsize N

or for the slave via: vovslavemgr configure -liverecorder.logsize N SLAVENAME where N is any number between 256 and 8192, which represents the size of the log file in megabytes. This setting must be applied before turning Live Recorder on.

nc run -r CGROUP:/sys/fs/cgroup/cpuset/my_cgroup1 -r
                  CGROUP:/sys/fs/cgroup/memory/my_cgroup2 -- sleep 120

will assign a "sleep 120" job to the cgroups my_cgroup1 and my_cgroup2

If the user specifies multiple conflicting cgroups (such as 2 cgroups under the /memory hierarchy), the cgroup that is specified last is the one that the process will be assigned to.

The special resource CGROUP:RAM can be used to limit memory usage of a job within a cgroup.

Example:

<path to cgroup root directory >/memory/ <queue name>_ <slave name>_ <job slot number>

To see slave resource for cgroups, use nc hosts -r and look for CGROUP: entries. If they are not present, ensure that they are set up on the slaves with lscgroups and check the slave logs for errors.

This parameter can be set in the policy.tcl configuration file.

The default value (1) provides identical behavior to previous releases. Increasing the parameter increases the number of samples to be used in the calculation of the cpuprogress statistic.

The accepted range of values is 1-1440. 1440 signifies one full day, assuming the sample time is 60 seconds.

Summary:

The new -failover option to vtk_slave_define now sets the capacity to 0, which prevents the slave 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 ensure the slave host is in the list.

Passing in the new -descriptors as well as the -failover option to vovslavestartup triggers a check to ensure the host has at least as many descriptors as vovserver, which ensures it can operate at full capacity in the event of failover. It also checks that the server_election directory is empty.

resuserDisableMatchingThreshold provides a threshold that disables matching if the sum of LicenseMonitor handles and FlowTracer jobs exceed that threshold.

The range is 0 - 10000; the default value is 1000.

This parameter can be specifed in policy.tcl.

set config(resuserDisableMatchingThreshold) 1000

This parameter can also be set using the VTK API.

vtk_server_config resuserDisableMatchingThreshold 1000

set config(clientConnectionQueue.mode) multi
set config(clientConnectionQueue.size) 512

The mode can be "single" or "multi" (default=multi). The size can be any integer in the range of 25-1024 (default=512).

Summary:

The default value can be over-riden with the VOV_MIN_DESCRIPTORS environment variable.

An attempt is made to raise the default limit if needed.

If the target's limit is higher than the system's hard limit, an error is displayed and the product start will be aborted.

Summary:

Resource groups can be defined that are a logical OR of components that are hosted on different license servers.

Licenses from specific servers can be excluded from distribution to specific sites.

Summary:

The automatically captured environment is saved as a file under the server working directory, which can be used to set the SNAPSHOT environment at any time.

The new standalone utility vovenvcapture is for saving the environment on demand, either into a file or as a property on a Vov object.

Summary:

When a job is stuck due to barrier invalid node in upcone, a balloon message appears and shows "barrier invalid".

On NodeEditor, the "Why" tab shows barrier invalid messages on the associated node(s).

Trouble-shooting methods:

(1) An aggressive retrace flag can be done in the main console window or by using vsr.

(2) Find the invalid jobs in the upcone and retrace them to validate the barrier.

If there are no invalid jobs in the upcone, fix the barrier invalid flag by running sanity.

Previously, if the environment variable VOV_VW_NFS_PROTECTION was set to 1 (or if the -n option is used with vw), vw added a delay when waiting for inputs to allow for Network File System (NFS) latency. By default, the wait duration was 60 seconds that could be overridden by setting the environment variable VOV_VW_NFS_WAIT.

In this release, in addition to the above behavior, if VOV_VW_NFS_PROTECTION is specified as 2 (or the -N option is used), vw also applies the same delay to allow for latency on outputs.

Overview:

Under certain conditions, for both inputs and outputs, vw will attempt to trigger a cache update sooner if possible. Note: for this to work, nfsdelay must be enabled in the vovserver settings in the policy.tcl file, and also applied to any currently running vovserver (by doing vovproject sanity). Example: set config(nfsdelay) 60

It is also recommended to specify a small time tolerance in policy.tcl to compensate for minor time discrepancies among machines and/or the filer. Example: set config(timeTolerance) 3

Note: This should also be applied to any currently running vovserver using vovproject sanity.

Summary:

For default sets that only contain files, such as System:files, System:filesToCheck, System:zippable, Predefined:missing files, and Predefined:blocking files, files are always displayed regardless of the setting of the flag.

However, for user defined sets, Show files must be turned on to view the files.

Summary:

When there are many slaves, Slave Monitor will not occupy the vovconsole area and show only one row and rest of them can be seen at floating Slave Monitor

If there are more than 20 slaves, grouping options are displayed.

Users can group slaves by state, arch, group(=slavegroup)

Summary of the changes:

After a predefined set is deleted, the vovconsole keeps the set names.

When the predefined sets are double-clicked, the predefined sets are recreated: the predefined set is recomputed and the up-to-date set is drawn on the set viewer.

Summary of features:

By default, the capacity follows the core count.

The capacity can be manually set via the -T option, or by defining the SLOTS/N consumable resource via the -r option. N is a positive integer.

In all cases, the capacity directly affects the number of slot licenses that will be requested.