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.