Adding a Dedicated Agent Node for Automation Suite Robots

Requirements

Before starting the Automation Suite Robot installation, make sure you meet the hardware requirements.

In a single-node evaluation installation, Automation Suite Robots run on the main server node. Cached packages are stored on the main node’s filesystem, in a folder that the interactive installer automatically provisions. Adding a dedicated agent node for Automation Suite Robots is optional in single-node evaluation installations.

Note: In a single-node evaluation installation, the number of concurrent serverless jobs is limited to 5.
In a multi-node HA-ready production environment, adding a dedicated node for Automation Suite Robots is mandatory. For details on the requirements the dedicated node must meet, see Hardware and software requirements.

Note: In a multi-node HA-ready production installation, the maximum number of concurrent serverless jobs is determined by the node’s resources (CPU/memory).
A minimum of 10GiB are required for package caching.

Adding an Automation Suite Agent Node to the Cluster

The following sections provide instructions on how to add a dedicated agent node for Automation Suite Robots.

Step 1: Configuring the Machine

Step 1.1: Partitioning the disk

To ensure the disk is partitioned correctly, see the instructions in Configuring the disk for a multi-node HA-ready production setup. Make sure to follow the steps for agent nodes.

Step 1.2: Configuring the disk for package caching

Option A

If you enabled package caching during installation, you must provision a folder on the filesystem of the host machine at the /uipath_asrobots_package_cache location or at the custom path configured via cluster_config.json/packagecachefolder. The folder must have at least 10GiB of free space available, otherwise the installation will fail.

Option B

Alternatively, you can provision a separate disk to the configureUiPathDisks script, which can configure the disk and the path:

~/configureUiPathDisks.sh --node-type agent --robot-package-disk-name [DISKNAME] --robot-package-path [PATH]~/configureUiPathDisks.sh --node-type agent --robot-package-disk-name [DISKNAME] --robot-package-path [PATH]

Note:

The --robot-package-path parameter is optional. If not set, the parameter defaults to /uipath_asrobots_package_cache.

If you modify the default value of cluster_config.json/packagecachefolder, make sure the value passed to the --robot-package-path parameter matches the configured value.

Step 2: Copying the Interactive Installer to the Target Machine

Online Installations

To copy the interactive installer to the target machine in an online installation, take the following steps:

SSH to the right machine:
- If you added Automation Suite Robots to a single-node evaluation installation, go to the main machine.
- If you added Automation Suite Robots to a multi-node HA-ready production installation, go to any of the server nodes.

Copy the contents of the UiPathAutomationSuite folder to the Automation Suite Robots node. Make sure to use the username and DNS specific to the Automation Suite Robots node.

sudo su -
scp -r /opt/UiPathAutomationSuite <username>@<node dns>:/opt/
scp -r ~/* <username>@<node dns>:/opt/UiPathAutomationSuite/sudo su -
scp -r /opt/UiPathAutomationSuite <username>@<node dns>:/opt/
scp -r ~/* <username>@<node dns>:/opt/UiPathAutomationSuite/

Offline Installations

To copy the interactive installer to the target machine in an offline installation, take the following steps:

SSH to the primary installation node.
Ensure that the UiPathAutomationSuite directory contains the sf-infra.tar.gz file. For download instructions, see sf-infra.tar.gz.
```
scp -r ~/opt/UiPathAutomationSuite <username>@<node dns>:/var/tmpscp -r ~/opt/UiPathAutomationSuite <username>@<node dns>:/var/tmp
```

Step 3: Running the Interactive Installer to Configure the Dedicated Node

Online Installations

To configure the dedicated node in an online installation, take the following steps:

SSH to the Automation Suite Robots node.

Run the Automation Suite interactive installer.

sudo su -
cd /opt/UiPathAutomationSuite
yum install unzip jq -y
CONFIG_PATH=/opt/UiPathAutomationSuite/cluster_config.json 

UNATTENDED_ACTION="accept_eula,download_bundle,extract_bundle,join_asrobots" ./installUiPathAS.shsudo su -
cd /opt/UiPathAutomationSuite
yum install unzip jq -y
CONFIG_PATH=/opt/UiPathAutomationSuite/cluster_config.json 

UNATTENDED_ACTION="accept_eula,download_bundle,extract_bundle,join_asrobots" ./installUiPathAS.sh

Offline Installations

To configure the dedicated node in an offline installation, take the following steps:

SSH to the Automation Suite Robots node.

Install the platform bundle using the following script:

sudo su 
mv /var/tmp/UiPathAutomationSuite /opt
cd /opt/UiPathAutomationSuite
sudo chmod -R 755 /opt/UiPathAutomationSuite

sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j asrobots --offline-bundle ./as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp --install-offline-prereqs --accept-license-agreementsudo su 
mv /var/tmp/UiPathAutomationSuite /opt
cd /opt/UiPathAutomationSuite
sudo chmod -R 755 /opt/UiPathAutomationSuite

sudo ./install-uipath.sh -i ./cluster_config.json -o ./output.json -k -j asrobots --offline-bundle ./as-infra.tar.gz --offline-tmp-folder /opt/UiPathAutomationSuite/tmp --install-offline-prereqs --accept-license-agreement

Step 4: Enabling Kubectl

To set the kubectl context on the Automation Suite Robots machine, run the following command:

sudo su -
export KUBECONFIG=/var/lib/rancher/rke2/agent/kubelet.kubeconfig
export PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get nodessudo su -
export KUBECONFIG=/var/lib/rancher/rke2/agent/kubelet.kubeconfig
export PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get nodes

You should see the nodes and their corresponding names. You need the name of the Automation Suite Robots node for the next step.

Step 5: Verifying the Automation Suite Robots Configuration

Check if the Automation Suite Robots node is configured. Make sure to replace <node name> with the Automation Suite Robots node name.

kubectl describe node <node name> | grep -i "taints"kubectl describe node <node name> | grep -i "taints"

The command should return the following output:

$ kubectl describe node asrobots0 | grep -i "taints"
Taints:             serverless.robot=present:NoSchedule$ kubectl describe node asrobots0 | grep -i "taints"
Taints:             serverless.robot=present:NoSchedule

At this point, you have successfully completed the installation for Automation Suite Robots.

On this page