Edit the scaling_config.json file.
In the "compute_resource_sets" section, locate the "available_applications" section.
Define the application using the descriptions and example below as a guide:
Property in web UI Property in scaling_config.json file Description Name "name" The name of the application Version "version" The application version Installation Path "install_path" The path of the Ansys installation (not applicable if using Kubernetes plugin) Executable "executable" The path of the application executable (not applicable if using Kubernetes plugin) Queue "queue" A default queue to request when starting this application on a scheduler Exclusive "exclusive" If set to "true", the scheduler will be asked to hold the node(s) exclusively for one request Distributed "distributed" Allows the scheduler to provide multiple machines to fulfill the request Local Scratch "use_local_scratch" Whether a scratch directory local to the compute node(s) should be used as the job working directory ("true" or "false"). Local Scratch Directory "local_scratch_dir" The path of the local scratch directory (for example, /tmp/scratch). Resource Name "resource_name" Specifies the Kubernetes object (deployment/statefulset) name to be used as the target resource by KEDA.
This corresponds to the Target Resource Kind ("target_resource_kind") specified in the configuration file.
If "target_resource_kind"="deployment", specify the deployment name.
If "target_resource_kind"="statefulset", specify the StatefulSet name.
If "target_resource_kind"="job", specify the image name with tag.
See also: Autoscaling with KEDA
Maximum Evaluator Instances "scaling_max_eval_instances" Maximum number of instances that can be created when scaling up Minimum Evaluator Instances "scaling_min_eval_instances" Minimum number of instances than can be terminated when scaling down Scaling Threshold "scaling_threshold" Threshold value to determine when Kubernetes deployments should be scaled up/down Cool Down Period "cool_down_period" The period to wait after the last trigger reported active before scaling the resource back to 0 Environment "environment" Environment variables to be used (not applicable if using Kubernetes plugin) "available_applications": [ { "name": "Ansys Mechanical APDL", "version": "2024 R1", "install_path": "/ansys_inc/v241", "executable": "/ansys_inc/v241/ansys/bin/ansys241", "environment": {}, "capabilities": null, "customization_hook": null, "resource_name": null, "use_local_scratch": {} "local_scratch_dir": "/tmp/scratch", "exclusive": {}, "distributed": {}, "queue": {}, "scaling_max_eval_instances": 1, "scaling_min_eval_instances": 0, "scaling_threshold": 1, "cool_down_period": 60 } ],Note: Properties such as Local Scratch, Exclusive, and Distributed are also available in the "backend" section of the configuration file (as global defaults) and in job definitions.
Property values specified in the job definition take precedence over values specified in application settings. If values have not been specified in either of those places, the global default values are used.