Configuring orchestrator.yml

Update values in orchestrator.yml, as needed.

Search for the following file.

/opt/aspera/var/config/orchestrator/orchestrator.yml

If you discover the file, back it up in another location, then remove it.

This is necessary because the above file is shared between nodes, and in a HA environment it is advisable to edit the file below:

/opt/aspera/orchestrator/config/orchestrator.yml

If you do observe differences, you will need to update the default file on each node with the values from the other orchestrator.yml file, in the this folder:

/opt/aspera/var/config/orchestrator/orchestrator.yml

On one node, open the following file:

/opt/aspera/orchestrator/config/orchestrator.yml

Edit the file to reflect the following configuration, adding any element that is missing.

engine_instance: 1
use_db_time: true 
active_active: true
install_config_file: /opt/aspera/orchestrator/config/orchestrator.yml
aspera_dir: /opt/aspera
orchestrator_dir: /opt/aspera/orchestrator
run_dir: /opt/aspera/var/run/orchestrator
config_dir: /opt/aspera/var/config/orchestrator
archive_dir: /opt/aspera/var/archive/orchestrator
install_images_dir: /opt/aspera/var/config/orchestrator/images
install_pages_dir: /opt/aspera/var/config/orchestrator/pages
install_css_dir: /opt/aspera/var/config/orchestrator/stylesheets
log_file: /opt/aspera/orchestrator/log/orchestrator.log

Edit orchestrator.yml on the peer node.

On the peer node, open the following file:

/opt/aspera/orchestrator/config/orchestrator.yml

Edit the file to match the configuration shown in 2, with one exception: engine_instance should be set to 2.

Customize HTML branding on each node. (Optional)

In some cases, the HTML branding may be inconsistent between the nodes.

Branding can be customized in the following file:

/opt/aspera/orchestrator/config/branding.yml

Remove the following file, if it exists:

/opt/aspera/var/config/orchestrator/branding.yml

Store the log file in a local folder. (Optional)

Log files can be stored in the local folder:

/opt/aspera/orchestrator/log/

They can also point to the log folder on the shared storage:

/opt/aspera/var/run/orchestrator/log/