Automate - Install on Amazon Linux 2

Install OpenJDK 11.

Download the Nuix Engine.

Unzip the Nuix Engine.

Move the contents of the Nuix Engine files to /opt/nuix-engine.

Clean-up the installation files.

Install the Nuix Engine dependencies listed at https://download.nuix.com/releases/engine/.

Update the nofile limits.

Download the latest Rampiva Automate.

Install unzip.

Unzip Rampiva Automate.

Update the end-of-line character of the installer script to Unix.

Run the installer.

Clean-up the installation files.

Open the Scheduler config.yml file for editing.

Update the apiSecret value with and random value that will be the same on the Scheduler and all Engine Servers.

Sample beginning of configuration file:

apiSecret: a228a905-d0cf-4955-8420-4923f1d78bdc

runScheduler: true

# Uncomment to enable Login with hardcoded credentials - for testing only
internalCredentials:
  displayName: Internal
  credentials:
    - username: temp-admin
      password: h@d751255n1

userSessionTimeout: 900

By default, no authentication mechanism are enabled. For testing, enable the internalCredentials mechanism.

Manually start the Scheduler service.

Confirm that the service started successfully by browsing to the Scheduler webpage.

If the webpage is not accessible, inspect the Scheduler logs.

Stop the manually started Scheduler service.

Create a service file for Scheduler.

sudo nano /etc/systemd/system/rampiva-scheduler.service

File contents:

[Unit]
After=network.service

[Service]
ExecStart=/opt/rampiva/automate/runScheduler.sh

[Install]
WantedBy=default.target

Reload the SystemD configuration and configure the service to start automatically at boot.

Reboot the system and confirm that the service starts.

Log on to Scheduler and deploy a valid Rampiva license.

Open the Settings → Execution Profiles panel, and edit the Default Profile with the following settings:

• Log Folder: /var/logs/rampiva

• Command-Line Parameters: -Xmx16g -Dnuix.logdir=/var/logs/rampiva -Duser.language=en -Duser.country=US -Dstorage.wal.allowDirectIO=false

• {base_data_folder}: /fsx/data

• {base_case_folder}: /fsx/cases

Open the Engine Server config.yml file for editing.

Update the apiSecret value with the value used in the Scheduler configuration file.

Sample beginning of configuration file:

apiSecret: a228a905-d0cf-4955-8420-4923f1d78bdc

runServer: true

nuixFlags: -Dnuix.logdir=/var/log/rampiva

Optionally, if the Engine Server is running on the same system as Scheduler, change the default HTTPS port from 443 to another port.

Manually start the Engine Server service.

Confirm that the service started successfully by browsing to the Engine Server webpage.

If the webpage is not accessible, inspect the Engine Server logs.

Stop the manually started Engine Server service.

Create a service file for the Engine Server.

sudo nano /etc/systemd/system/rampiva-engine-server.service

File contents:

[Unit]
After=network.service

[Service]
ExecStart=/opt/rampiva/automate/runEngineServer.sh

[Install]
WantedBy=default.target

Reload the SystemD configuration and configure the service to start automatically at boot.

Reboot the system and confirm that the service starts.

Install the Lustre client according to the AWS instructions from https://docs.aws.amazon.com/fsx/latest/LustreGuide/install-lustre-client.html .

Create a Lustre file system if one is not already available.

https://console.aws.amazon.com/fsx/home?#file-system-create

From the AWS file system console, retrieve the attach instructions.

Sample instructions:

sudo mkdir /fsx
sudo mount -t lustre -o noatime,flock fs-0a95b9ccff30dee78.fsx.us-east-1.amazonaws.com@tcp:/banzrbmv /fsx

Run the attach commands.

Confirm that the Lustre file system was mounted correctly.

mount  | grep fsx

Sample output:

172.31.71.8@tcp:/banzrbmv on /fsx type lustre (rw,noatime,flock,lazystatfs)

Create a script file for mounting the Lustre file system at boot.

sudo nano /opt/aws/mount-lustre.sh

Sample file contents (adjust based on attach instructions):

#!/bin/bash
mount -t lustre -o noatime,flock fs-0a95b9ccff30dee78.fsx.us-east-1.amazonaws.com@tcp:/banzrbmv /fsx

sudo chmod 755 /opt/aws/mount-lustre.sh

Create a service file for mounting the Lustre file system at boot.

sudo nano /etc/systemd/system/fsx-lustre.service

File contents:

[Unit]
After=network.service

[Service]
ExecStart=/opt/aws/mount-lustre.sh

[Install]
WantedBy=default.target

Reload the SystemD configuration and configure the service to start automatically at boot.

Reboot the system and confirm that the file system was mounted correctly.