Workload controller policies

Turbonomic ships with default automation policies that are believed to give you the best results based on our analysis. For certain entities in your environment, you can create automation policies as a way to override the defaults.

Automation workflow

Actions associated with a workload controller resize container specs vertically to assure optimal utilization of resources. This is a natural representation of these actions because the parent controller's container specs for vCPU limits/requests and vMem limits/requests are modified. The workload controller then rolls out the changes in the running environment.

Points to consider:

  • Scale actions

    Workload controller policies do not control scale actions. These actions are generated under the conditions described in this topic.

  • Resize actions

    Container spec policies control the generation of resize actions, while workload controller policies control the execution of these actions.

    Action Default mode
    vCPU Limit Resize Down Manual (automatable)
    vCPU Limit Resize Up Manual (automatable)
    vCPU Request Resize Down Manual (automatable)
    vMem Limit Resize Down Manual (automatable)
    vMem Limit Resize Up Manual (automatable)
    vMem Request Resize Down Manual (automatable)

    You can control action execution based on the specific resources that you want to resize and the resize direction. For example, for vCPU limit resizes, you may want to automate resize down actions, but require reviews of resize up actions and only execute the actions that receive an approval. To enforce these rules, create a workload controller policy and then set the action mode for vCPU Limit Resize Down to automated, and vCPU Limit Resize Up to manual.

  • Action orchestration is currently not supported.