This is version 2.18 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](https://docs.aws.amazon.com/elemental-server).

# Installing AWS Elemental Conductor File Pooled Licenses on a Virtual Machine (VM)
Installing Pooled Licenses on a Virtual Machine (VM)

This section is for IT administrators who perform the first-time installation of AWS Elemental Conductor File software on a VM (virtual machine) using pooled licenses. The AWS Elemental Server worker nodes have the same licensed options and so can share the same license.

**VM Guest Requirements**  
AWS Elemental software can run only on a VM generated by VMware virtualization software. You must use VMware vCenter Server to create the VM. The vSphere client by itself does not work. 

For version and system requirements and other information about VMware, see [System Requirements for Virtual Machines (VMs)](vm-req.md).

**Phase 1 Setup**  
This section explains how to perform the following on each blade:
+ Create a VM and install the AWS Elemental OVA.
+ Install the licenses.
+ Install the AWS Elemental Conductor File and AWS Elemental Server software.
+ Configure eth0 as the management interface on each VM.

**Prerequisite Knowledge**  
To complete this process, you must have the following knowledge:
+  A basic understanding of server virtualization.
+  Installing and using the VMware Center and the VMware vSphere client interface, including Open Console.
+  Moving files from a VM guest to other systems over the network. We recommend using a utility such as Secure Copy Protocol (SCP).
+  Locating recently downloaded files.

The procedure for installing any version of AWS Elemental Conductor File is the same; only the version number in the file name changes. In this procedure, we show how to install version 2.18.3.12345 of the software.

Installation consists of four parts: 

1.  Downloading files from AWS Elemental

1.  Installing the host operating system (OS)

1.  Installing the AWS Elemental software

1. Setting up licensing

**Topics**
+ [

# Step A: Prepare the Hardware and Download Files
](install-vm-p-cf-ig-prep.md)
+ [

# Step B: Deploy the VM and Install AWS Elemental Conductor File
](install-vm-p-cf-ig-install-vm.md)
+ [

# Step C: Set-up Licensing
](install-vm-p-cf-ig-licensing.md)
+ [

# Step D: Deploy the VM and Install AWS Elemental Server
](install-vm-p-cf-ig-install-vm-w.md)
+ [

# Step E: Verify that Workers Receive Licenses
](install-vm-p-cf-ig-ver.md)
+ [

# Step F: Complete Node Configuration
](install-vm-p-cf-ig-complete.md)

# 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 [AWS Elemental Support Center Activations](https://console.aws.amazon.com/elemental-appliances-software/home?region=us-east-1#/activations). For detailed steps to download installation files, see [Downloading AWS Elemental Conductor File Software](detailed-dl-cf-ig.md).

1. 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, `elemental_production_conductor_file_2.18.3.44452.run`.

     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 your AWS Elemental Servers have GPUs, download the GPU version.

    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.

# Step B: Deploy the VM and Install AWS Elemental Conductor File
Step B: Deploy the VM and Install the Conductor File Software

Set-up the AWS Elemental Conductor File nodes before setting up the worker AWS Elemental Server nodes. 

Perform these steps from your workstation.

**Install the Conductor Software on the Primary Node**

1. Place the OVA image in a convenient location accessible to the VM host.

1. Start the VMware vSphere client and choose the option that lets you run the OVF Deploy wizard to create the VM guest.

1. Complete the fields in the wizard. Pay special attention to the following settings:
   + For the *source*, enter the location where you saved the OVA file.
   + Ensure that the *hostname* that you assign to the VM guest is unique across all of your AWS Elemental products.
   + For *network settings*, such as DNS servers and eth configuration, leave the fields blank. You will configure these settings later in the AWS Elemental Conductor File installation and configuration process.

1. Choose **Finish**. The OVA is installed, the guest is created, and AWS Elemental Conductor File is installed on that guest with the eth0 configured as specified.

1. Before proceeding, take a snapshot of the VM, as described in the VMware vSphere help text.

**Verify Installation**  
The VMware vSphere client provides feedback about creation of the VM guest. However, it does not provide status feedback during installation of the AWS Elemental software. Therefore, to monitor progress of the installation once the VM guest has been created, follow these steps:

1. From the VMware vSphere client, choose **Open Console** and access the AWS Elemental Conductor File VM. The screen shows a progress bar.

1. Press Esc on your keyboard to switch the display to showing text.

1. Watch for the following:
   + Early in the installation process, the display pauses on the line `Starting: ATD`. This indicates that the installation is in progress.
   + The log-in prompt appears when the installation is complete. 

1. At the log in prompt, enter the *elemental* user credentials.

   You are logged in at the home directory (/elemental). If the install succeeds, the AWS Elemental banner is displayed.

**Install on Secondary Node**  
Perform the same installation and verification on the secondary AWS Elemental Conductor File node.

# Step C: Set-up Licensing


Install a valid license file for each AWS Elemental system using the following steps described in the following table. Detailed instructions for each step follow.


****  

| Step | Where to Perform Step | Start Step With | Finish Step With | 
| --- | --- | --- | --- | 
| Step a: Retrieve Activation Code | Your workstation | Activation email | Activation code | 
| Step b: Generate License Activation Key File | The keygen utility available on the VM | Activation code | Key file (.key ) | 
| Step c: Download Licenses from the AWS Elemental User Community | Your workstation | Key file (.key ) | Tarball file (.tgz) | 
| Step d: Install the License Files | Your workstation | Unlicensed software with limited functionality | Fully licensed, full-feature software | 

# Step a: Retrieve Activation Code


You should have received an email containing an activation code. If you're installing software for more than one VM guest, you will have received a separate code for each one.

If you didn't receive this email or have lost it, contact AWS Elemental Support through your company’s Private Space in [AWS Elemental Support Center](https://console.aws.amazon.com/elemental-appliances-software/home?region=us-east-1#/supportcenter).

# Step b: Generate a License Activation Key File


The operating system that you installed on your virtual machine (VM) has a utility you can use to generate an activation key file. 

**To generate an activation key file**

1. From the VMware vSphere client, choose **Open Console** and access the desired VM, using the *elemental* user credentials. 

   You are logged in at the home directory (/elemental).

1. Enter this command.

   ```
   [elemental@hostname ~] ./keygen
   ```

1. At the prompt, enter the activation code for the first VM, including the dashes. The following file is created in the home directory: `activation_<hostname of the system>.key `

1. Copy the activation key file from the VM to your workstation using SCP.

   Use the *elemental* user credentials.

1. Repeat these steps for each VM. 
   + Make sure to repeat step 1 for each AWS Elemental Conductor File activation key file that you want to generate: each key file must contain the hostname of the individual VM.
   + Make sure to use a different activation code on each VM.

# Step c: Download Licenses from the AWS Elemental User Community


**Important**  
You must perform these steps for the system that will act as the primary AWS Elemental Conductor File node first and then for the secondary.

1. Follow the instructions in [Downloading AWS Elemental Conductor File Software](detailed-dl-cf-ig.md) to get to the **Order Detail** page on the [AWS Elemental Support Center Activations](https://console.aws.amazon.com/elemental-appliances-software/home?region=us-east-1#/activations).

1. Hover over the three-bar icon on the right of the screen to bring up a small menu. Choose **License(s)**.  
![\[Three-bar icon with dropdown menu showing "License(s)" and "Download" options.\]](http://docs.aws.amazon.com/elemental-cf2/latest/installguide/images/install-licorderdetail-shared-png.png)

1. On the **License Information** page, choose **Generate**.  
![\[Generate button highlighted on a License Information page interface.\]](http://docs.aws.amazon.com/elemental-cf2/latest/installguide/images/install-licinfo-shared-png.png)

1. On the **Generate Licenses** page, select **Choose File** to browse to and select your `.key` file.

1. This returns you to the **Generate Licenses** page, with your `.key` file selected. Choose **Upload License Key**.  
![\[File upload interface with "Choose File" button and "UPLOAD LICENSE KEY" option highlighted.\]](http://docs.aws.amazon.com/elemental-cf2/latest/installguide/images/install-genlic-shared-png.png)

1. This takes you to the **View Licenses** page, where you can download a `.tgz` file. This is a compressed, aggregated file that contains all the license files that you need for this system.  
![\[View Licenses page showing license details and download options.\]](http://docs.aws.amazon.com/elemental-cf2/latest/installguide/images/install-viewlic-shared-png.png)

1. Save the `.tgz` file to a place accessible to the AWS Elemental system that will be using this license, for example, a directory on your workstation called “licenses”. Make a note of the path. 

   The files are named `lic-download-<hostname>-primary.tgz` and `lic-download-<hostname>-secondary.tgz`.

1. Download the license files for the secondary AWS Elemental Conductor File node using these same steps.

# Step d: Install the License Files


Now that you have a `.tgz` compressed license file for each instance of the software you are running, you must point the software to it.

From your workstation, perform the following steps on each AWS Elemental Conductor File node.

1. Navigate to the directory where you saved the `.tgz` file and unpack it.

1. Bring up the web interface for the primary AWS Elemental Conductor File system. From the main menu, select **Settings** > **Licenses**. The Licenses screen appears.

1. Select **Choose File** and navigate to the directory where you placed the license files. Select the file name with the hostname portion matching the hostname of this node.  
![\[License management interface showing options to upload or update license files.\]](http://docs.aws.amazon.com/elemental-cf2/latest/installguide/images/install-installlic-shared-png.png)

1. Back on the Licenses screen, choose **Update**. The license file will be installed. Be sure to install each license file: `conductor.lic` and `ui.lic`.

1. Look at the information in the left pane and make sure that:
   + **Total** shows the expected number of licenses in the pool.
   + **Expiration** shows the expected expiry date for the licenses.
   + **Product** shows the correct product for the worker nodes.
   + **Processing** shows the expected CPU and GPU counts.
   + **Pacakages** shows the expted options. These are the add-on optionst built in to the AWS Elemental Server pooled license.

1. Repeat on the secondary AWS Elemental Conductor File node.

# Step D: Deploy the VM and Install AWS Elemental Server
Step D: Deploy the VM and Install the Worker Software

After you've installed the AWS Elemental Conductor File nodes, perform these steps on each individual blade that you're adding to the cluster in order to deploy a VM and install the AWS Elemental Server worker software.

1. Start the VMware vSphere client and choose the option that lets you run the OVF Deploy wizard.  
****    
[\[See the AWS documentation website for more details\]](http://docs.aws.amazon.com/elemental-cf2/latest/installguide/install-vm-p-cf-ig-install-vm-w.html)

1. Choose **Finish**. The OVA is installed, the guest is created, and AWS Elemental Conductor File is installed on that guest with the eth0 configured as specified.

1. Before proceeding, take a snapshot of the VM, as described in the VMware vSphere help text.

1. When you've finished installing, enter the hostname of the worker node into a web browser and make sure that the web interface appears.

1. Repeat these steps for each worker node.

# Step E: Verify that Workers Receive Licenses


Before going into production, it is a good idea to verify that the AWS Elemental Server node can obtain a license from AWS Elemental Conductor File. To do so, create a job on the AWS Elemental Server node and start it.

# Step F: Complete Node Configuration


You have now installed and performed basic configuration of AWS Elemental Conductor File and AWS Elemental Server. To complete the setup of your cluster:
+ For AWS Elemental products that aren't using pooled licenses, see [AWS Elemental Server Configuration Guide](https://docs.aws.amazon.com/elemental-server/latest/configguide).
+ For phase 2 (full configuration) of the products using the pooled licenses, see [AWS Elemental Conductor File Configuration Guide](https://docs.aws.amazon.com/elemental-cf2/latest/configguide)>