Automation Suite on Linux installation guide

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 10GB are required for package caching.

Adding an Automation Suite Agent Node to the Cluster​

Step 1: Configuring the Machine​

Step 1.1: Partitioning the disk​

Step 1.2: Configuring the disk for package caching​

Option A​

Option B​

./bin/uipathctl rke2 disk --robot-package-disk-name [DISKNAME] --robot-package-path /uipath_asrobots_package_cache
./bin/uipathctl rke2 disk --robot-package-disk-name [DISKNAME] --robot-package-path /uipath_asrobots_package_cache

Step 1.3: Configuring the node for serverless robots​

./bin/uipathctl rke2 install -i ./cluster_config.json -o ./output.json -k -j asrobots --accept-license-agreement
./bin/uipathctl rke2 install -i ./cluster_config.json -o ./output.json -k -j asrobots --accept-license-agreement

• taint: serverless.robot=present:NoSchedule
• labels: serverless.robot=true and serverless.daemon=true

1. Add a taint for serverless robots:

   assignment

   kubectl taint nodes [NODE_NAME] serverless.robot=present:NoSchedule
   kubectl taint nodes [NODE_NAME] serverless.robot=present:NoSchedule
   

2. Add the labels for serverless robots:

   assignment

   kubectl label nodes [NODE_NAME] serverless.robot=true serverless.daemon=true
   kubectl label nodes [NODE_NAME] serverless.robot=true serverless.daemon=true
   

Step 2: Copying the Interactive Installer to the Target Machine​

1. 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.

2. 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.

   assignment

   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/
   

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

1. SSH to the Automation Suite Robots node.

2. Run the Automation Suite interactive installer.

   assignment

   sudo su -
   cd /opt/UiPathAutomationSuite
   yum install unzip jq -y
   CONFIG_PATH=/opt/UiPathAutomationSuite/cluster_config.json 
   
   ./bin/uipathctl rke2 install -i ./cluster_config.json -o ./output.json -k -j asrobots --accept-license-agreement
   sudo su -
   cd /opt/UiPathAutomationSuite
   yum install unzip jq -y
   CONFIG_PATH=/opt/UiPathAutomationSuite/cluster_config.json 
   
   ./bin/uipathctl rke2 install -i ./cluster_config.json -o ./output.json -k -j asrobots --accept-license-agreement
   

Step 4: Enabling Kubectl​

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

Step 5: Verifying the Automation Suite Robots Configuration​

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

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