activate#

dpsctl resource-group activate Usage Guide#

Activate a resource group. You must first create a resource group before it can be activated.

Usage#

dpsctl resource-group activate

Flags#

Includes global dpsctl options.

  --resource-group string       resource group name
  --strict-policy               if the requested allocation is not possible, fail instead of accepting a reduced allocation (default: false)
  --sync                        synchronous activation. Wait until resource group activation is complete (default: false)
  --async                       asynchronous activation (default). Return immediately after validating the resource group, but activation continues asynchronously
  --async-n-hosts int           asynchronous activation, but wait until at least this many hosts are configured before returning (default: 0)
  --async-percent-hosts int     asynchronous activation, but wait until at least this percent of hosts are configured before returning (default: 0)
  --async-wait duration         asynchronous activation, but wait this much before returning (default: 0s)
  --at-least-n-hosts int        at least this number of hosts must be activated for the resource group activation to succeed. Remaining hosts may fail to be configured, but they remain part of the resource group (default: 0)
  --at-least-percent-hosts int  at least this percent of hosts must be activated for the resource group activation to succeed. Remaining hosts may fail to be configured, but they remain part of the resource group (default: 0)
  --partial-timeout duration    wait at most this much for the resource group activation to come to an acceptable level. If the resource group cannot be activated for the given failure tolerance levels within this duration, activation fails. (default: 0s)
  --allow-reprovision           allow power policy reprovisioning of other resource groups in order to activate the resource group if there is not enough power to activate the resource group (default: true)
  --help, -h                    show help

Async and Partial Completion Rules#

  • If neither --sync nor --async is specified, activation runs asynchronously by default.

  • --sync cannot be combined with async return controls.

  • At most one of --async-n-hosts, --async-percent-hosts, or --async-wait can be used.

  • At most one of --at-least-n-hosts or --at-least-percent-hosts can be used.

  • Percent values must be between 0 and 100.

Examples#

Activation with Normal Allocation#

Activate the resource group after creating it, adding its entities, and confirming the selected policy_bundle with dpsctl resource-group list.

Without --strict-policy, DPS can admit a reduced allocation within the effective policy constraints. When --allow-reprovision is enabled, it can also adjust eligible active resource groups to make room. This is allocation from the effective typed policies, not fallback through legacy names such as Node-High, Node-Med, or Node-Low.

dpsctl resource-group activate --resource-group test-2

Activation with Strict Policy Application#

Use --strict-policy when the requested allocation must be admitted without reduction. The request fails if that allocation cannot be satisfied.

dpsctl resource-group activate \
  --resource-group test-2 \
  --strict-policy \
  --sync

Apply Per-GPU Limits After Activation#

Explicit per-GPU limits use the standalone dpsctl gpu-policy command on nodes in an active resource group. They are not configured through a resource-group update flag or as per-GPU entries in the selected bundle.

dpsctl gpu-policy --node node001=500,550

Refer to dpsctl gpu-policy for validation and response details.