update#

dpsctl resource-group update Usage Guide#

Update supported non-policy settings on a resource group.

Important

In DPS 0.9, the CLI exposes --policy-bundle and --remove-policy-bundle, but the server rejects either option with NOT_IMPLEMENTED and the message resource group policy updates are not supported. The server rejects the request before it distinguishes between active and inactive groups. Select the bundle when you create the resource group. To use a different bundle, delete and recreate the group.

Use dpsctl gpu-policy for per-GPU watt limits. The resource-group update command has no --entity-policy or --entity-gpu-policy flag.

Usage#

dpsctl resource-group update --resource-group <name> [flags]

Flags#

Includes global dpsctl options.

   --resource-group string              resource group name
   --policy-bundle string               currently rejected by the server
   --remove-policy-bundle               currently rejected by the server
   --strict-policy                      require the configured policy to apply without automatic fallback
   --workload-profile-ids string        workload power profile Redfish IDs (comma-separated)
   --remove-all-workload-profiles       remove workload power profiles
   --sync                               wait for the update to complete
   --async                              return after validation while the update continues (default)
   --async-n-hosts int                  wait until at least this many hosts are configured
   --async-percent-hosts int            wait until at least this percentage of hosts are configured
   --async-wait duration                wait this long before returning
   --at-least-n-hosts int               minimum number of hosts that must update successfully
   --at-least-percent-hosts int         minimum percentage of hosts that must update successfully
   --partial-timeout duration           maximum wait for the acceptable completion threshold
   --wpps-disable-async-verification    disable asynchronous WPPS verification
   --priority int                       priority for power stealing and giveback ordering
   --help, -h                           show help

Async and Partial Completion Rules#

  • If neither --sync nor --async is specified, update runs asynchronously.

  • --sync cannot be combined with asynchronous 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.

  • Percentage values must be between 0 and 100.

Update Priority#

--priority is sent only when you pass the flag. The change is stored immediately and is used the next time giveback or stealing runs. It does not rebalance power by itself. Refer to Resource Group Priority.

$ dpsctl resource-group update --resource-group example1 --priority 10
{
  "status": {
    "ok": true,
    "diag_msg": "Success"
  }
}

Update Workload Profiles#

Replace the workload-profile IDs:

dpsctl resource-group update \
  --resource-group example1 \
  --workload-profile-ids 3,4

Remove all workload profiles:

dpsctl resource-group update \
  --resource-group example1 \
  --remove-all-workload-profiles