Configure turbonomic to support 200 plus targets

Document created by ansaba Expert on Feb 7, 2019Last modified by iddo.avneri on Oct 18, 2019
Version 3Show 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. Make a copy of the file in case you need to roll back:

     

    cp /srv/tomcat/data/config/disc.config.topology /srv/tomcat/data/config/disc.config.topology.bck

     

  2. Increase DiscoveryManagerImpl thread pool size to 50: change numThreads="10" to 50

    note - 50 is a good number for 600 targets. For 200 targets, you can use 20. 
  3. 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 by editing 

    startup.BlazeDS.bootstrap:

    cp /srv/tomcat/data/config/startup.BlazeDS.bootstrap /srv/tomcat/data/config/startup.BlazeDS.bootstrap.bck

    inside the file point to the market.60min.config.topology file instead of the default 10 minutes:
    i.e. change

    to:

    Note - there is also a 30 minutes file. So if discovery takes less than 30 minutes, you can use that file. 
  2. To disable discovery dumping set the following properties in data/config/discovery-dumping.properties 

global=0

If the file doesn't exist please create it and make sure it is owned by tomcat:tomcat (have the file include this single line)

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. You might need to add these lines to the file. 
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 (noticed that the version number will change according to the version you are on)

Make a backup of the file

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

and edit it:

<?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>

 

 

restart tomcat

service tomcat restart
1 person found this helpful

Attachments

    Outcomes