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 Globally, click on Settings> Policies> Default>Virtual Machine Default>Scroll down to Scaling Constraint and click ADD > select Excluded Templates (figure 1).
Note in Turbonomic 6.1 you can also exclude templates for Databases on AWS or Azure.
Figure 1: Select Exclude Templates from Scaling Constraints
From here you can add Templates to exclude by clicking on Add Template and then selecting the templates your want to exclude (figure 2).
Figure 2: Click Add Template and select the templates you want to exclude
To exclude for a group, for example if you want to exclude templates for a certain Region or a set of applications defined by tags, click on Settings>Automation Policies> + Automation Policy (top right)>Virtual Machine>Scope (enter group name)> +Scaling Constraints>Add Scaling Constraint>Excluded Templates> Choose the templates you’d like to exclude (figure 3).
Figure 3: Excluding Templates for a Group
That's it, the policy now applies to both real-time scaling actions and migration plans. It 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.