Install Worker on a Linux Image


Use the Workload Manager installer binary worker_installer.bin to create Workload Manager-enabled Linux images on different clouds and regions.

The Linux worker installer is compatible with these distributions:

  • CentOS7
  • CentOS6
  • RHEL7
  • RHEL6
  • Ubuntu14.04
  • Ubuntu16.04
  • Ubuntu 18.04

When you modify a pre-built image (for example, when performing an OS update, installing a new tool, upgrading the Management Agent, and so forth), be aware that the pre-built image already has Workload Manager Tools installed.

When updating an image that already has Workload Manager Tools installed, you must delete this file (/usr/local/osmosix/etc/hostid) prior to taking the final snapshot.

Use this procedure to also install Workload Manager Tools on CentOS 7 and RHEL-7.

When you manually install the Management Agent (Worker) on  CentOS 7, RHEL 7, or Ubuntu 14, and select the "worker1" install option, the following Out-Of-Box (OOB) Workload Manager services will automatically run inside a Docker container inside the worker VM:

Cloud Nuances

  •  VMware

    To use VMware VMs, you should have already installed VMware tools on the Linux machine.

  •  AzureRM
    1. Install CliQr Tools on the application VM.

    2. Run the following commands after the installation is completed:

      rm -f /var/lib/waagent/ovf-env.xml
      waagent -deprovision+user
    3. Stop the VM.

    4. Capture the image.

Installation Process

To acquire and run the Linux worker installer, follow this procedure:

  • Download the archive from, unzip the archive, and identify the installer package: worker_installer.bin.

  • SSH into the application VM instance using the key pair that you used to launch the VM and go to the /tmp directory

sudo -i cd /tmp
  • Copy the installer package from you computer to this directory.

  • Change permissions to allow execution of the installer, specify a local package store (if necessary), and run the installer using the syntax shown below:

chmod 755 worker_installer.bin
#Set the following only if a local store is setup
export CUSTOM_REPO=<http://local_package_store IP>

./worker_installer.bin <ostype> <cloudtype> worker_basic

#See Syntax

ostype = rhel6, rhel7, oel6, centos6, centos7, ubuntu10, ubuntu1204, ubuntu1404 (see the section below to identify your OS type)

cloudtype = amazon, azurerm, google, openstack, vmware

worker_basic = The worker_basic option installs all components necessary to download, start, and support the agent

  • Clean up and exit the VM instance:
rm worker_installer.bin rm ~/.ssh/authorized_keys exit

Identifying the OS Type

To verify or identify the OS type, follow this procedure:

  1. In your terminal, issue one of the following commands (based on your Linux implementation):

    1. $ cat /etc/issue

      Ubuntu 14.04.2 LTS \n \l


    2. $ cat /etc/*-release

      CentOS release 6.3 (Final)

  2. Based on the response to one of these commands, you can identify if your OS type.

Successful Installation

After you run the installer commands, the installation results are displayed on the screen as follows:

  • Success scenarios: Identifies a list of successfully installed components in green text.

  • Failure scenarios: Provides a path to the log file that provides details of each failure.

Map a Logical Image to the Pre-bootstrapped Image

In order to use the new pre-bootstrapped image in deployments, you must set up the appropriate Image mapping.

  • No labels
Terms & Conditions Privacy Statement Cookies Trademarks