Unified Collection Deployment Guide

Document created by dor.juravski on Feb 23, 2018Last modified by dor.juravski on Apr 5, 2018
Version 5Show Document
  • View in full screen mode

Unified Collection installation method using ELK stack (ELK - Elasticsearch Logstash and Kibana)

 

Collection of Data

Please download the collection scripts at this link.

Python3 is a prerequisite for running Unified Collection scripts. See below a separate set of instructions.

 

  1. Download and copy the file to /root/unified_collection onto your Turbonomic install instance (or any location of your choice)
  2. Unzip the file. This creates “unified_collection_v6_pub”. The number depends on the version of file you have downloaded
  3. Older “turbonomic_install.info” you may have should be merged with the new file, while making sure no new lines are lost.
    For example: from /root/unified_collection/unified_collection_v4/turbonomic_install.info
  4. TURBO_USER/TURBO_PASSWORD:
    Those parameters use a hash (base64) of your Turbonomic user-interface user and password.
    For example “echo -n myname | base64”- this will generate a user hash, that can be copied into turbonomic_install.info
  5. cd to sql_scripts and review the symbolic links in the directory. Each symbolic link represents a script to run. To generate all possible symbolic links run the "create_template_symlinks.sh" script and then cleanup un-wanted links. For example you can clean up *weekly*
  6. Create a “stable” symlink to the current unified_collection_v6 location.
    For example:
    cd /root/unified_collection
    rm -f stable
    ln -s unified_collection_v6_pub stable
  7. Create crontab entries for your needed script times - hourly,daily or weekly:
    For example run:
    “crontab -e”

    Create an entry that looks like this
    30 * * * * /root/unified_collection/stable/unified_execute_run.sh hourly nodebug
  8. Files will be created in the "output" directory. For example /root/unified_collection/stable/output"
  9. Files can be moved manually or using other methods to their destination. See below for other file transfer options

 

Python3 install

Pyhon3 is required to run the unified collection scripts

Online install

yum -y install yum-utils

yum -y install https://centos7.iuscommunity.org/ius-release.rpm

yum -y install python36u python36u-libs python36u-setuptools python36u-pip

 

 Offline install

  1. copy over the file python file from
    /root/unified_collection/stable/python3_install/turbonomic_pro_services-3.6.2-1.tar.gz
    to /tmp
  2. Unzip the file. This will create /tmp/turbonomic_pro_services 
  3. cd /tmp/turbonomic_pro_services
  4. run INSTALL.sh
  5. Verify the version by running "python3" that the output looks like this:

    Python 3.6.2 (default, Jul 18 2017, 22:59:34)

    [GCC 4.8.5 20150623 (Red Hat 4.8.5-11)] on linux

 

File Transfer Options

The collected files can be transferred in the following ways

  1. Via scp to another host - requires a one-time key exchange, which is explained here
    The following parameters need to be set in the file turbonomic_install.info:
    LOGSTASH_HOST
    LOGSTASH_SAVE_LOCATION
    Add the following option to the script "sendhost" for example /root/unified_collection/unified_execute_run.sh daily sendmail
  2. Via email: if SMTP is not setup on the Turbonomic host, please set it up (typically a system admin would perform the task)
    The following parameters need to be set in the file turbonomic_install.info:
    EMAIL_FROM
    EMAIL_TO
    EMAIL_SUBJECT
    EMAIL_MESSAGE
    Add the following option to the script "sendmail" for example /root/unified_collection/unified_execute_run.sh daily sendmail
  3. Upload to an AWS S3 bucket
    The fillowing lines should be modified in the file "unified_execute_run.sh"
    CLOUD_URL
    CLOUD_BUCKET
    CURL_URL
    Add the following option to the script "sendcloud" for example /root/unified_collection/unified_execute_run.sh daily sendmail
2 people found this helpful

Attachments

    Outcomes