Turbonomic now supports configuring Turbonomic policies to take action if the VMs are out of compliance. This feature enables the user to bring vCPU and vMEM parameters of a VM into compliance by executing compliance actions that are generated based on the VM policies.
What are Compliance Actions?
Compliance actions are Resize actions with action category as Compliance. User can execute these actions to make the VM into compliance. Till now, Resize actions were having a category as either Performance or Efficiency and were generated only when there is a need for demand based resizing based on the observed utilization. Compliance actions are generated only for the On-prem VMs and are generated when the minimum threshold value set for virtual CPU or virtual memory of a virtual machine are not honoured.
If a compliance action is generated, revenue based resize actions will not be generated for the vCPU or vMEM until the VM become compliant, either by executing the compliance actions or by fine tuning the associated policy.
Screenshot below shows Compliance actions generated to resize the vCPU / vMEM to make the VMs compliant with the minimum value set by policy.
Action Details View:
Configurations to make the VM compliant
Configure Automation Workflow for vCPU Resize Below Min and / or vMEM Resize Below Min values in the Virtual Machine Policy to Do not generate actions.
Under the Operational Constraints of Virtual Machine Policy, specify the minimum threshold settings for virtual CPU and virtual Memory.
The new Compliance actions are generated if the virtual CPU or virtual memory of a Virtual Machine are not in compliant with the operational constraints configuration and executing these actions allow the user to bring the VM back into compliance.
For VMs in a consistent scaling group, if at least one VM is non-compliant, compliance actions would be generated for all the VMs making the scaling group consistent.
Turbonomic generate compliance actions as below
| VM Specification |
Automation Policy Configuration |
Action Generation |
|
vCPU = 1 core
vMEM = 2 GB
|
- VMEM Resize Min Threshold = 8 GB
- VCPU Resize Min Threshold = 2 core
- vCPU Resize Below Min = Do not generate actions
- vMEM Resize Below Min = Do not generate actions
|
- Compliance action generated for vCPU to resize up from 1 core to 2 core
- Compliance action generated for vMEM to resize up from 2 GB to 8 GB
|
|
vCPU = 1 core
vMEM = 2 GB
|
- VMEM Resize Min Threshold = 8 GB
- VCPU Resize Min Threshold = 2 core
- vCPU Resize Below Min = Do not generate actions
- vMEM Resize Below Min = AUTOMATIC
|
- Compliance action generated for vCPU to resize up from 1 core to 2 core
- No Compliance action generated for vMEM since the vMEM Resize Below Min is allowed
|
|
vCPU = 4 core
vMEM = 12 GB
|
- VMEM Resize Min Threshold = 8 GB
- VCPU Resize Min Threshold = 2 core
- vCPU Resize Below Min = Do not generate actions
- vMEM Resize Below Min = Do not generate actions
|
- No compliance action for vCPU since the vCPU is within the threshold value
- No Compliance action for vMEM since the vMEM is within the threshold value
|
|
2 VMs in a scaling group
VM1 : vCPU = 1 core and vMEM = 2 GB
VM2 : vCPU = 4 core and vMEM = 12 GB
|
- VMEM Resize Min Threshold = 8 GB
- VCPU Resize Min Threshold = 2 core
- vCPU Resize Below Min = Do not generate actions
- vMEM Resize Below Min = Do not generate actions
|
- Compliance action for VM1 vCPU to resize up from 1 core to 4 core since VM2 in the scaling group is having a vCPU of 4 core
- Compliance action for VM1 vMEM to resize up from 2 GB to 12 GB since VM2 in the scaling group is having a vMEM of 12 GB
|
Scope
This feature is only applicable to On-prem VMs.
Note
This feature is available from Turbonomic version 8.15.3
#Highlights-home