Install Worker on a Linux Image

Overview

Use the CloudCenter installer binary (LINUX_WORKER_OS_VERSION) to create CloudCenter-enabled images on different clouds and regions.

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 CloudCenter Tools installed.

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

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

Cloud Nuances

  • When installing the Management Agent on Linux machines, you will need to provide information on the OS and platform being used.

     VMware

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

  • Azure

     Azure Installation Nuances
    1. Install CliQr Tools on the application VM.

    2. Run the following command after the installation is completed

      waagent -deprovision+user

    3. Stop the VM.

    4. Capture the image.

  • vCD

     vCD Installation Nuances
    1. Install CliQr Tools on the application VM.

    2. Stop the VM.

    3. Edit the settings for this VM and be sure to remove the NIC(s).

    4. Save the VM as a template into the vCD catalog of your choice.

Installation Process

To install CloudCenter tools on a Linux image, follow this procedure:

  1. Contact CloudCenter Support to obtain the installer binary and the path. Download the installer package (worker_installer.bin) to the CCM VM’s /tmp folder.

  2. SSH into the application VM instance using the key pair that you used to launch the VM.

  3. Run the following commands to install CloudCenter Tools:

    sudo -i
    cd /tmp
  4. Download the installer package to the application VM’s /tmp folder.

  5. Change permissions and use the application VM (worker) installer file to install CloudCenter Tools:

    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> <worker1 | worker_basic | worker_full>
    
    #See Syntax

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

    cloudtypeamazon, azurepack, azurerm, google, opsource, openstack, softlayer, vmware, and vcd

    worker1 | worker_basic | worker_full = The worker_basic and worker_full options are explained in the following table.

    The following modules are installed as part of the installation process for Base OS images, depending on the specified mode.

    ModuleDescriptionRequired?worker1
    (default installation)
    worker_basicworker_full
    sysupdateBasic RPM filesYesInstalledInstalledInstalled
    worker
    • Custom Linux Image binaries for Application VM images
    • Custom Windows Image binaries for Application VM images
    • JDK 6/7 for Java web application access
    • Jetty
    • JMeter for benchmarks

    The VNC and Interactive modules are not installed by default. If you require VNC access in the Application VM instance, set the following environment variable before running worker_installer.bin:

    export gui_enabled=true
    YesInstalledInstalledInstalled
    docker
    • Dedicated External Script Executor (Conditional)
    • Custom Docker Image
    OptionalInstalledNot installedInstalled
    vncVirtual Network Computing (VNC) binaries for VNC access – Generally used for Linux-based OS with an X Window System and a desktop environment (gnome, kde, xfce, etc).OptionalNot installedNot installedInstalled
    interactiveInteractive VNC access-related binaries for VNC accessOptionalNot installedNot installedInstalled
  6. 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

      or

    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.


Back to: Worker (Conditional)

  • No labels
© 2017-2019 Cisco Systems, Inc. All rights reserved