IBM Turbonomic Glossary

Non-disruptive Mode is a policy setting for VMs that prevents actions that require a reboot or introduce disruptions from executing automatically.

Turbonomic posts such actions in Manual (Action Mode), so you can defer their execution to a non-critical time window.

The Notification Center is the location in the user interface where Turbonomic informs you about problems affecting its functionality. This can include issues with VMware Tools, target connectivity, or other similar problems. 

You can find the Notification Center in the lower part of the Navigation Bar. Issues with your environment are not reported here.

For Turbonomic analysis, Observation Period is the time span of sampling for the data that is used to calculate utilization percentiles. You can set a Maximum Observation Period and a Minimum Observation Period.

The observation period impacts the analysis that Turbonomic uses to generate actions. A shorter period means analysis uses fewer data points to calculate utilization percentiles. This results in more dynamic, elastic resizing, while a longer period results in more stable or less elastic resizing.

See also Aggressiveness.

The OpenAPI Specification (OAS) defines a standard, language-agnostic interface to RESTful APIs which allows both humans and computers to discover and understand the capabilities of the service without access to source code, documentation, or through network traffic inspection (https://swagger.io/specification/). 

The Turbonomic API is implemented using OpenAPI, and it uses Swagger as one way to deliver API documentation.

OVA is a file that contains a compressed, installable version of a virtual machine. One of the methods for deploying Turbonomic is via an OVA. When you open an OVA, it extracts the virtual machine (VM) and imports it into your datacenter. The Virtual Machine contains a complete instance of the Turbonomic platform.

(See also MariaDB)

See Aggressiveness

A Plan Market is a snapshot of the real-time market that you can create in Turbonomic  to simulate “what-if” scenarios against your environment. It starts with the same entities, utilization levels, placement constraints and analysis settings as the real-time market has.

To configure the plan, you can modify the plan scope, change policies and constraints, and add or remove workloads. When plans run, they generate and execute actions. The plan stops when there are no further actions to take. 

Turbonomic displays the results at the end of the analysis. Actions in the Plan Market have no effect on the real-time market. 

A Policy Schedule is a setting which makes the policy active only at designated times. This sets a window of time when the policy takes effect.

When the policy is in effect, Turbonomic uses the policy settings in its analysis, and can recommend or automatically execute actions as they are generated. When the policy is not in effect, it is the same as not having the policy at all.

Do not confuse Policy Schedule with Action Execution Schedule. The Policy Schedule sets when the policy takes effect, and an Action Execution Schedule sets when Turbonomic can execute a given action. For example, you can set a policy that automatically resizes or starts VMs for the entire month of December, in anticipation of an increase in demand. Within this same policy, you can set the resize execution schedule to Monday, from midnight to 7:00 AM, when demand is expected to be minimal.

Polling is an action taken to collect data. Turbonomic polls targets periodically to collect data on capacity, average utilization, and peak utilization.