Action acceptance modes
Action acceptance modes specify the degree of automation for the generated actions. For example, in some environments you might not want to automate resize down of VMs because that is a disruptive action. You would use action acceptance modes in a policy to set that business rule.
Turbonomic supports the following action acceptance modes:
-
Recommend
Recommend the action so that a user can execute it outside Turbonomic.
-
Manual
Recommend the action, and provide the option to execute that action through the Turbonomic user interface.
-
Automated
Execute the action automatically.
For automated resize or move actions on the same entity, Turbonomic waits five minutes between each action to avoid failures associated with trying to execute all actions at once. Any action awaiting execution stays in queue. For example, if a VM has both vCPU and vMem resize actions, Turbonomic could resize vCPU first. After this resize completes, it waits five minutes before resizing vMem.
-
Automated when approved
Execute the action automatically only after they are externally approved. This option is available only after adding a Service Now target.
The Pending Actions charts only count actions in Recommend or Manual mode.
Automated actions appear in the following charts:
-
All Actions chart on the Home Page and the On-prem Executive Dashboard
-
Accepted Actions chart on the Home Page
Setting action acceptance modes
There are two ways to configure action acceptance modes:
-
Change the action acceptance mode in a default policy.
-
Create an automation policy, scope the policy to specific entities or groups, and then select the action acceptance mode for each action.
Turbonomic allows you to create dynamic groups to ensure that entities discovered in the future automatically add to a group and apply the policy of that group. If a conflict arises as a result of an entity belonging to several groups, the entity applies the policy with the most conservative action.
Action acceptance overrides
Under some conditions, Turbonomic changes the action acceptance mode of an action from Manual to Recommend.
Turbonomic makes this change as a safeguard against executing actions that the underlying infrastructure cannot support. For example, assume you have VM move actions set to Manual. Then assume Turbonomic analysis wants to move a VM onto a host that is already utilized fully. In this case, there would be other actions to move workloads off of the given host to make room for this new VM. However, because moves are Manual, the host might not be properly cleared off yet. In that case, Turbonomic changes actions to move workloads to the host from Manual to Recommend.
For cloud environments, some instances require workloads to be configured in specific ways before they can move to those instance types. If Turbonomic recommends moving a workload that is not suitably configured onto one of these instances, then it changes the action acceptance mode from Manual to Recommend, and then describes the reason.