Step A: Prepare the Hardware and Download Files - AWS Elemental Conductor File

This is version 2.16 of the AWS Elemental Conductor File documentation. This is the latest version. For prior versions, see the Archive section of AWS Elemental Conductor File and AWS Elemental Server Documentation.

Step A: Prepare the Hardware and Download Files

Determine the Primary Conductor Node

The Conductor File nodes are license servers because they manage the pooled licenses that the AWS Elemental Server worker nodes use. Typically, you have two AWS Elemental Conductor File nodes to support failover to a backup if the primary fails. Decide which of the Conductor File nodes is the primary and which is the secondary. Note that the primary node takes on the role of primary license server and the secondary that of secondary license server.

Prepare the Hardware and Network

To prepare your hardware and network, make sure you have done the following:

  • Physically installed the hardware unit.

  • Set up the unit as a node on your network.

  • Configured network cards and ensured that they're able to reach other machines on the network.

  • Set up a method, such as SCP, for transferring files from your workstation to the VM guest.

Note Your Activation Code

You should have received an email with your activation code. You need this number for the installation.

If you're installing AWS Elemental software on more than one system, you received an activation code for each system. Decide and note which activation code you will use for each unit. The codes are not tied ahead of time to any specific system, but you cannot use the same code on more than one.

Download Files

Download the installation files for each unique AWS Elemental product that you're using.

To download installation files

  1. Log in to the AWS Elemental User Community and follow the prompts to navigate to your files. For detailed steps to download installation files, see Downloading AWS Elemental Conductor File Software.

  2. Download your files.

    You need the following files for each unique piece of AWS Elemental software that you're installing.

    • A kickstart (.ova) file for creating a VM instance. For example, centos-20161028T12270-production-usb.ova.

      You will use this file to put a preconfigured installation of your operating system on your VM.

    • An installation (.run) file for the AWS Elemental software itself. For example,

      Make sure that you download the right version of software for the processing architecture that you need, either CPU-only or GPU-enabled.

    For example, if you're installing AWS Elemental Conductor File on two systems and AWS Elemental Server on five systems, you need to download two .ova files and two .run files.

Make Downloads Accessible

Move the .ova and .run files to a location where they can be accessed during installation. Note that:

  • The AWS Elemental software installers (.run) must be stored on a network share that the VM has access to. This location can't require login credentials.

  • The OVA image can be left in your workstation download directory or you can put it on the same network share as the software installers.