Configuring orchestrator.yml

  1. Edit orchestrator.yml on the first node.
    On the first 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
  2. Edit orchestrator.yml on the second node.
    1. On the second node, open the following file:
      /opt/aspera/orchestrator/config/orchestrator.yml
    2. Edit the file to match the configuration for the first node (shown in the previous step), with one exception:
      engine_instance should be set to 2.
  3. Customize HTML branding on each node. (Optional)
    1. Open the following file and edit it to customize branding:
      /opt/aspera/orchestrator/config/branding.yml
    2. Remove the following file, if it exists:
      /opt/aspera/var/config/orchestrator/branding.yml
  4. Store the log file in a local folder. (Optional)
    Log files can be stored in the following local folder:
    /opt/aspera/orchestrator/log/
    They can also point to the log folder on the shared storage:
    /opt/aspera/var/run/orchestrator/log/