Turbonomic Global Glossary
Special | A | B | C | D | E | F | G | H | I | J | K | L | M | N | O | P | Q | R | S | T | U | V | W | X | Y | Z | ALL
Action Execution Schedule
An Action Execution Schedule is a policy setting which determines when Turbonomic can execute specific generated actions. You can use it to defer the execution of generated actions to a non-critical time window.
For example, if mission-critical VMs experience memory bottlenecks during the week, you can defer the necessary memory resizes to the weekend. Even if the VMs have minimal utilization over the weekend, Turbonomic will recognize the need to resize, and execute the resize actions. Do not confuse Action Execution Schedule with Policy Schedule. (For more about the difference, see Policy Schedule.)
The Action Orchestrator is a component of the Turbonomic platform that tracks, translates, and starts the execution of actions in both the live and Plan markets.
It also provides statistics about actions and action severity.
Active Directory (AD)
Active Directory (AD) is a directory service developed by Microsoft for Windows domain networks. It authenticates and authorizes all users and computers in a Windows domain type network. (https://en.wikipedia.org/wiki/Active_Directory)
Turbonomic integrates AD servers and domains to authenticate AD users and groups, and assign them user roles.
An affinity rule is a rule affecting placement of virtual machines on a host. You can implement affinity rules in Turbonomic via placement policies. Also, Turbonomic discovers vSphere Host Distributed Resource Scheduler (DRS) rules when DRS is enabled, and implements them as placement policies. Imported rules are enabled by default, but you can disable specific rules as necessary.
Turbonomic supports Place, Don’t Place, Merge, and License policies. The Place and Don’t Place policies implement Affinity and Anti-affinity rules, respectively. Affinity rules place groups of workloads together on specific hosts so you can easily audit the usage of those workloads. Anti-affinity rules keep specific workloads from running together on the same host to support HA and prevent a single point of failure at that host.
An agent is a computer program installed on a node or server to monitor the processes in the background. In most cases, Turbonomic monitors your environment without agents. It uses target APIs to discover applications, platforms, and infrastructure in your environment.
To monitor Kubernetes clusters, Turbonomic uses the Kubeturbo agent. When you install Kubeturbo on a node, it automatically registers itself as a target for the complete cluster.
[Also called Percentile] In Turbonomic, Aggressiveness is the percentile to use when calculating the utilization of a resource. The utilization drives actions to scale the available capacity either up or down.
To measure utilization, analysis considers a given utilization percentile. For example, assume a 95th percentile. The percentile utilization is the highest value that 95% of the observed samples fall below.
A percentile evaluates the sustained resource utilization, and ignores bursts that occurred for a small portion of the samples. You can think of this as aggressiveness of resizing, as follows:
Amazon Web Services (AWS)
Amazon Web Services is a public Cloud platform that provides compute, storage, and application services.
Turbonomic can manage AWS targets in your environment. Turbonomic is an AWS Partner Network Partner with Cloud Management Tools Competency status.
Ansible is an IT automation engine for cloud provisioning, configuration management, application deployment, intra-service orchestration and more. Based on YAML, it uses no agents or additional custom security infrastructure. Turbonomic uses Ansible Inventory and Play Books to discover VM configuration data and to build application topologies.
See Affinity Rule