Configure turbonomic to support 600 plus targets

Document created by ansaba Expert on Feb 7, 2019Last modified by ansaba Expert on Jul 31, 2019
Version 2Show Document
  • View in full screen mode

Objective

Turbonomic has been supporting over 20K entities in environment but with few number of targets. This article talks about when number of target is at large scale eg 600 and total number of entities is like 3000.

 

Testing Environment

Below configuration is based on simulation 600 AWS targets in turbonomic lab. We have used modified utilProbe simulating exactly like AWS probe in term of latency and threads.

 

Recommended setting for turbonomic to support 600 pls targets

 

disc.config.topology changes

  1. Increase DiscoveryManagerImpl thread pool size to 50: change numThreads="10" to 50
  2. Tune post-processing to run once per 1 hour: add maxTimeWithoutPostprocSeconds="2400" and minTimeBetweenPostprocSeconds="1800" right after numThreads
numThreads="50" maxTimeWithoutPostprocSeconds="2400"  minTimeBetweenPostprocSeconds="1800"

 

Market changes

  1. Configure market to run every hour: market.60min.config.topology will be provided
  2. To disable discovery dumping set the following properties in data/config/discovery-dumping.properties 

    global=0

  3. Increase the Discovery thread pool in disc.config.topology 

          numThreads="25"

VM changes

  1. Increase CPU and Memory: m5.2xlarge is recommended 
  2. Increased disk space, 600 discoveries generate 1200 discovery dumps in /srv/tomcat/data/discoveries. Also 600 targets increase log size dramatically. + 30 additional Gb


AWS Probe changes

  1. in sdk.probe.properties adjust thread pool sizes 
probe.AWS.thread.pool.dc.size=5
probe.AWS.thread.pool.queries.size=5
probe.AWS.thread.pool.monitoring.size=5

   2.  Change AWS discovery interval to 60 min

/srv/tomcat/webapps/vmturbo/probe-jars/com.vmturbo.mediation.aws-6.3.3/probe-conf.xml

<?xml version="1.0" encoding="UTF-8"?>
<probe>
    <full-class-name>com.vmturbo.mediation.aws.AwsProbe</full-class-name>
    <executor-class-name>com.vmturbo.mediation.aws.control.AwsActionExecutor</executor-class-name>
    <type>AWS</type>
    <category>Cloud Management</category>
    <version>1.0.0</version>
    <rediscovery-interval-seconds>3600</rediscovery-interval-seconds>
</probe>

Attachments

    Outcomes