allocation#

dpsctl validate allocation Usage Guide#

Validate policy bundle allocation for devices without applying changes.

Usage#

dpsctl validate allocation [command options]

You can also use the validate alias:

dpsctl val allocation [command options]

Flags#

Includes global dpsctl options.

   --devices string [ --devices string ]  device names (comma-separated)
   --policy-bundle string                 policy bundle name to validate
   --strict-policy                        if the requested policy bundle is not feasible, fail instead of retrying at the effective policy floor (default: false)
   --help, -h                             show help

Behavior#

The dpsctl validate allocation command performs a dry-run power allocation analysis for the requested devices and policy bundle. It reports whether the allocation would succeed and any constraints returned by DPS.

No allocation state is persisted. Use this command to test a policy bundle before selecting it for a resource group or topology.

Required Inputs#

  1. --devices must include at least one device name. Multiple devices can be provided as a comma-separated list.

  2. --policy-bundle must specify the policy bundle name to validate against the devices.

Name Validation#

The policy bundle name and each device name are validated before the request is sent. Invalid names fail fast and return a validation error for the corresponding flag.

Strict Policy#

By default, validation can report the result after retrying an infeasible bundle at its effective policy floor. Use --strict-policy to disable that retry. If the requested bundle is not feasible, the command still prints a validation response, but allocation_would_succeed is false with a diagnostic message.

Examples#

Validate allocation for one device#

$ dpsctl validate allocation --devices node-a --policy-bundle MaxP
{
  "status": {
    "ok": true,
    "diag_msg": "would activate successfully"
  },
  "allocation_would_succeed": true
}

Validate allocation for multiple devices#

$ dpsctl validate allocation --devices node-a,node-b --policy-bundle MaxP
{
  "status": {
    "ok": true,
    "diag_msg": "would activate successfully"
  },
  "allocation_would_succeed": true
}

Validate allocation with strict policy matching#

$ dpsctl validate allocation --devices node-a,node-b --policy-bundle MaxP --strict-policy
{
  "status": {
    "ok": true,
    "diag_msg": "would activate successfully"
  },
  "allocation_would_succeed": true
}

Use the validate alias#

$ dpsctl val allocation --devices node-a,node-b --policy-bundle MaxP --strict-policy
{
  "status": {
    "ok": true,
    "diag_msg": "would activate successfully"
  },
  "allocation_would_succeed": true
}

Notes#

  • This command is a dry run and does not persist allocation, policy, resource group, or topology changes

  • --devices and --policy-bundle are required

  • Device names are sent in the order provided

  • Device and policy bundle names must pass DPS name validation

  • Use --strict-policy when an effective-policy-floor retry is not acceptable

  • Output includes allocation_would_succeed and can include policy-selection, power-reclamation, and per-device status details

  • Output follows the selected global output format, such as json or yaml