2025.1.1 Release Notes

To enable, use the LA configuration variable to set the percentage of available tokens that can be allocated to priority projects other than the regular licenses distribution: LA::EnablePriorityBasedAllocation and LA::PriorityBasedAllocationPercentage.

When running in a secure environment where comm.tls.enable=1 and comm.requireClientAuth=1, key based authentication is required for every command and client running in as part of the job, in the job environment. If the job environment has access to the job submitter's $HOME, this is normally straightforward. vov code and Python REST clients can access the user's key in $HOME/.vov/userkey and use that for authentication. However, the job may be running in a container or a cloud instance which doesn't have access to the job submitter's key from their $HOME directory.

In these cases, the -jk option to nc run can be used to create a job-specific security key that will only be valid in Accelerator for the lifetime of the job. When the job is executed, the execution environment will include a shared memory file owned by the job submission user and visible to the vov infrastructure. If this is present, this job specific key will be used to authenticate when communicating with vovserver. If you want to make REST API calls via a Python script, the authorizeWithJobKey() method in the vov_rest_v3.py library can be used to establish a valid REST connection with vovserver.

{ TYPE = "Burndown", NAME="<Pay-Per-Use Tag_Feature>", 
BURNDOWN_BUDGET_HOURS = <number>, BURNDOWN_PERIOD_DAYS = <number>}, 

Similarly, by default vovtsd will only accept client authentication using the public key in $HOME/.vov/userkey. However, when invoked, vovtsd will examine the environment variable VOVTSD_USERKEYS. If it is set, vovtsd will treat it as a list of space separated public keys that will be used to authenticate against vovtsd clients (aka vovtaskermgr).

• dajob
• INTERCEPT.start.csh
• INTERCEPT.end.csh
• mtff_config.csh
• mtff_setup.csh
• ncupgrade
• taskerdebug
• update_crontab_vovdir.csh
• vdkcheckcapsule
• vmake vov_diagnostics_chdir
• vov_diagnostics_setuid
• vovbarrier
• vovcompresslog
• vovcopyproject
• vovcrontab
• vovlalsf
• vovlanc
• vovlapbs
• vovloghandler
• vovmake
• vovmpi
• vovparallel
• vovplacetrace
• vovproject
• vovprotectwithcounter.csh
• vovrsh
• vovsetupuser
• vovsshsetup
• vovtaskerlaunch
• vovtaskerstartup
• vovxrsh

For set with status=VALID,FAILED,SLEEPING,RUNNING rule, the table will display MAXRAM, CPUTIME, DURATION and HOSTNAME as new columns by default.

For set with status=SCHEDULED bucketid>0 rule, the table will display WAITREASON, RESOURCES, SCHEDTIME and QUEUETIME as new columns by default.

Destination: postgresql.crt and postgresql.key

Source based on priority:

<local.>/ssl/wildcard.crt and key

<swd>/config/ssl/<host>-signed.crt and key

<swd.>/config/ssl/<host>-self-signed.crt and key

The files are used for PostgreSQL connection when secure SSL mode is configured.

1. Calculate the number of active users, that is, the users who have requested any services within the lookback window (default: the last 30 seconds). If there are fewer than 2 active users, or the time taken by user services is below the configured threshold (default: 40% of real-time), nothing further is done.
2. Calculate the time allocation per active user. This is the amount of time since the last hog calculation (typically 10 seconds) divided by the number of active users and multiplied by a configurable parameter (default: 1.0).
3. For each active user, if the amount of time taken by that user's service requests exceeds the time allocation per user, the user is marked as a "hog". The "root" user and the project owner are never considered hogs.
4. If a user is deemed a hog, any further requests from that user will be delayed. The length of the delay is calculated by multiplying the amount by which their service time exceeded the per-user allocation time, multiplied by a configurable parameter (default: 1.0).

• hog.protection.time.enable is a boolean 1/0 value; set to 1 to enable hog protection for users taking too much time with their service requests. Default: 1
• hog.protection.time.lookbackWindow is an integer value indicating the time window in which a user will be considered "active" for the purposes of hog detection. For example, a value of 30 would mean that only users with service requests in the last 30 seconds would be evaluated for "hog" status. Allowed range: 1 - 300, default: 30
• hog.protection.time.minServicePercentage is a floating-point value indicating the minimum percentage of real-time that must be taken by services in the last 10 seconds for hog protection to be enabled. For example, a value of 40.0 means that if services have taken less than 40% of real time for the last 10 seconds, hog detection computations will not be performed. Allowed range: 0.0 - 100.0, default: 40.0
• hog.protection.time.minActiveUserTimePercentage is a floating-point value indicating the minimum percentage of real-time in the last 10 seconds that a user's services must take up before they are considered an "active" user for the purposes of hog detection. Allowed range: 0.0 - 100.0, default: 2.0
• hog.protection.time.allocationThreshold is a floating-point value indicating the multiple of allocated service time a user must take with their service requests in the last 10 seconds before being considered a "hog". For example, a value of 2.0 would mean a user is considered a "hog" if they have taken at least twice as much time as the average user allocation in the last 10 seconds. Allowed range: 1.0 - 100.0, default: 1.0
• hog.protection.time.delayMultiplier is a floating-point value indicating the multiplier to be applied to the delay attributed to users who are deemed service hogs. For example, a value of 2.0 with a user who exceeded their allocation by 5 seconds would cause their further requests to be delayed by 5 * 2.0 = 10 seconds. Allowed range: 0.1 - 100.0, default: 1.0

• Fixed resource creation submission through the Accelerator web UI.
• Corrected the submit button name in the resource creation form
• Removed leading and trailing spaces from the "Add" button label
• Prevents URL encoding issues that were causing submission failures