Skip navigation
All Places > Product Forum > Blog > 2017 > November

In certain situations you may want to excluded EC2 instance or Azure Virtual Machine types from being recommended by Turbonomic for either real-time scaling actions or migration plans.  This may be due to an application team that prefers to only run on a certain size, an operational policy to only use a certain family, or a way to attempt and reduce cost by not allowing expensive ones. 


Keep in mind that Turbonomic makes the best decisions to match your workload demand with the available templates across families and clouds so whenever you define these types of constraints you may be limiting the value Turbo can add in your environment.


That being said here is the approach. 


To exclude for a group of VMs, click on Settings> Policies> Automation Policy>Virtual Machine 

To exclude for a group, click on Settings>Automation Policies> + Automation Policy (top right)>Virtual Machine. 


From here you can add Templates to exclude by defining the:


  • Scope (enter group (s) name)
  • Excluding templates under Scaling Constraints>Add Scaling Constraint>Excluded Templates> Choose the templates you’d like to exclude 


Below is an example excluding the C3 family for all AWS VMs. 




That's it, the policy now applies to both real-time scaling actions, migration and cloud optimization plans . The policy will take affect within the next discovery cycle, typically 10 min.  


Turbo will also let you know if certain workloads are out of compliance and run on templates you've excluded. In that case you will see an action to move to the best template that provides the workloads with the resources it needs while minimizing your costs.  


Note in Turbonomic 6.1 you can also exclude templates for Databases on AWS or Azure and can no longer set this policy as a default policy, i.e. you have to select a group or multiple groups. 

Turbonomic can automatically suspend unused virtual machines in an AWS or Azure environment. This can significantly reduce monthly bills and eliminate the need to chase down development teams to clean up their environments. 


Here is an example of how to enable this capability in your environment with Turbonomic version 6.1. 


Navigate to Settings > Groups. 


Create a new application group and select the apps to include. See example below. 

Now you need to set an Automation Policy for the application group you just created. This can be found under Settings > Policies and selecting Automation Policy. 


Select Application under policy type and define the following:

  • Scope to the app group you defined 'auto suspend group' in my example above  
  • Set the schedule, e.g. daily 5 pm to 11 pm 
  • Set Application Priority to Normal 


See example below. 


Finally you need to set the Minimum Sustained Utilization and ensure the underlying VMs for these application workloads have the right automation policy in place to stop and start (for proof of concept you may want to first set this to Recommend or Manual before moving to full automation). 


To the set the VM automation policy navigate to Settings > Policies and selecting Automation Policy. 


Select Virtual Machines under policy type and define the following:

  • Scope to the underlying VM group for the apps 
  • Set the Minimum Sustained Utilization to a current and historical VCPU utilization value below which you'd like the VM to suspend 
  • Set Suspend under Action Automation to Automated, Manual or Recommended 
  • Set Start under Action Automation to Automated, Manual or Recommended 


See examples below. 



That's it. Turbonomic will identify apps that are not consuming resources during the time window you define and drive suspend actions on the underlying VMs. And when the policy time expires Turbonomic will turn those VMs back on.