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
A computer cluster is a group of two or more computers, or hosts, that are connected in a network and run in parallel to complete individual tasks. Turbonomic discovers clusters in your environment, and represents them in the Supply Chain. You can use clusters to specify scope for your Turbonomic session, for plans, for policies, and for charts.
In Turbonomic, you can configure placement policies that merge clusters. Turbonomic can use a Merge placement policy to move workloads across cluster boundaries. This creates a Supercluster.
A Container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computer environment to another (Docker website). The benefits include quick delivery and feedback and lower release risk.
Turbonomic discovers Containers through Kube-Turbo targets that run in your Kubernetes cluster (see also Container Pod, Container Spec, Workload Controller, and Namespace).
In Kubernetes, controllers are control loops that watch the state of your cluster, then make or request changes where needed. Each controller tries to move the current cluster state closer to the desired state. (Kubernetes Documentation: https://kubernetes.io/docs/concepts/architecture/controller/)
In Turbonomic on-prem environments, CPU (Central Processing Unit) is the measure of processing capacity on a host. CPU is typically expressed on the host as the number of cores, with a given processing speed. Turbonomic measures allocated CPU capacity and utilized CPU in hertz of processing power (GHz or MHz).