Automation Suite on Linux installation guide

Preparing the cluster_config.json file​

1. Generate the cluster_config.json file on the source cluster by running one of the following commands:

   1. If you upgrade from versions prior to 2023.10.0, use the following options:

      • Option A: If you already have a cluster_config.json file available, get it by navigating to the latest installer folder and running the following command:

        assignment

        cd /opt/UiPathAutomationSuite/latest/installer
        
        ./configureUiPathAS.sh config get -i /path/to/old/cluster_config.json -o /opt/UiPathAutomationSuite/cluster_config.json
        cd /opt/UiPathAutomationSuite/latest/installer
        
        ./configureUiPathAS.sh config get -i /path/to/old/cluster_config.json -o /opt/UiPathAutomationSuite/cluster_config.json
        

      • Option B: If you do not have a cluster_config.json file available, generate it by navigating to the latest installer folder and running the following command:

        assignment

        cd /opt/UiPathAutomationSuite/{version}/installer
        
        ./configureUiPathAS.sh config get -o /opt/UiPathAutomationSuite/cluster_config.json
        cd /opt/UiPathAutomationSuite/{version}/installer
        
        ./configureUiPathAS.sh config get -o /opt/UiPathAutomationSuite/cluster_config.json
        

   2. If you upgrade from 2023.10.0 or later versions, generate the config file by navigating to the latest installer folder and running the following command:

      assignment

      ./bin/uipathctl manifest get-revision >> ./cluster_config.json
      ./bin/uipathctl manifest get-revision >> ./cluster_config.json
      

   3. If you opted for Side-by-side upgrade (single node start) model, set or edit the following fields in the cluster_config.json file.

      assignment

      {
      ....
      "profile": "default",
      "fault_tolerance": 0,
      ...
      }
      {
      ....
      "profile": "default",
      "fault_tolerance": 0,
      ...
      }
      

2. Copy the cluster_config.json file from the source cluster and place it in the target cluster:

   assignment

   scp cluster_config.json user@target_cluster_IP /foo/bar
   scp cluster_config.json user@target_cluster_IP /foo/bar
   

   Make sure to replace /foo/bar with the directory path on the target cluster.

3. Perform the following actions:

   1. Generate a new GUID for rke_token to ensure the new cluster does not join the source cluster. Run the following command:
      assignment

      LC_CTYPE=C tr </dev/urandom -dc '!@#$%q_A-Z-a-z-0-9' | head -c 16
      LC_CTYPE=C tr </dev/urandom -dc '!@#$%q_A-Z-a-z-0-9' | head -c 16
      

   2. Update the temporary FQDN, SQL Server, or other configurations as required for the target cluster.
   3. Update the cluster_config.json file accordingly with the new values.
      • You can use any text editor to modify the cluster_config.json file.
      • Optional external objectstore: Provide the external objectstore if you want to change any of its settings.
      • You need to provide a PostgreSQL database for AutomationSuite_Airflow and configure its connection string in cluster_config.json.

Installing the new cluster​

1. Install the infrastructure on the new target cluster, by following the preparation and installation instructions, with the mention that, in this case, you need to skip the Completing the installation step.

2. If you use an in-cluster objectstore, you must install the required in-cluster objectstore for import, by running the following command:

   assignment

   ./bin/uipathctl manifest apply /opt/UiPathAutomationSuite/cluster_config.json --override argocd --versions versions/helm-charts.json
   ./bin/uipathctl manifest apply /opt/UiPathAutomationSuite/cluster_config.json --override argocd --versions versions/helm-charts.json