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

      uipathctl manifest get-revision >> ./cluster_config.json
      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
   

3. Use a newly generated GUID for rke_token, as well as a different temporary FQDN, SQL Server, or other configurations, as needed for the target cluster, and update cluster_config.json accordingly.
   • You must generate a new GUID for rke_token to prevent the new cluster from joining the source cluster. To do that, 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
     

   • 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.
   • For Process Mining on Automation Suite 2023.10.9 or higher, using PostgreSQL for the Airflow database is the recommended option. If the target cluster is 23.10.9 or higher and you want latest version of Airflow you need to bring a PostgreSQL database for the Process Mining AutomationSuite_Airflow database and configure the connection string for it in cluster_config.json.

Installing the new cluster​