add

dpsctl resource-group add Usage Guide

Add resources to a resource group.

Resources can be added to both inactive and active resource groups:

• Inactive resource groups: Adding resources is a database-only operation. The resource group’s configured policy bundle is applied when the resource group is activated.

• Active resource groups: The resource group’s configured policy bundle is applied to the added resources immediately, and power is reallocated as needed.

Note: Adding resources to a resource group that is currently activating or deactivating will be rejected. Wait for the operation to complete before adding resources.

Usage

dpsctl resource-group add

Flags

Includes global dpsctl options.

  --resource-group string  resource group name
  --entities string        resource entity names (comma-separated list)
  --strict-policy          if the configured policy bundle is not feasible, fail instead of retrying it at the effective policy floor (only applies when resource group is active)
  --allow-reprovision      allow power policy reprovisioning of other resource groups if there is not enough power (only applies when resource group is active; default: true)
  --help, -h               show help

Examples

Add entities to a resource group

$ dpsctl resource-group add --resource-group example1 --entities node001,node002
{
  "status": {
    "ok": true,
    "diag_msg": "Success"
  }
}

Add entities to an active resource group with strict policy enforcement

When adding resources to an active resource group, use --strict-policy to require its configured policy bundle. If the bundle is not feasible, the operation fails instead of retrying at the effective policy floor.

$ dpsctl resource-group add --resource-group example1 --entities node004 --strict-policy
{
  "status": {
    "ok": true,
    "diag_msg": "Success"
  }
}

Add entities without allowing power reprovisioning

By default, when adding resources to an active resource group, power may be redistributed from other resource groups if needed (power stealing). Use --allow-reprovision=false to prevent this behavior.

$ dpsctl resource-group add --resource-group example1 --entities node005 --allow-reprovision=false
{
  "status": {
    "ok": true,
    "diag_msg": "Success"
  }
}