deactivate#

`dpsctl topology deactivate` Usage Guide#

Deactivate the named active topology. Deactivation stops DPS power management for the topology and attempts to release the DPS-managed policy from each managed node.

You cannot deactivate a topology while it has active resource groups. Delete every active resource group before you run this command.

Behavior#

When you deactivate a topology, DPS performs the following actions:

Marks the topology inactive and removes its active topology policy binding.
Sends an UnsetPolicy request to each node that requires policy cleanup.
Applies the device’s configured idle policy when one exists. Otherwise, the device plugin restores BMC defaults or removes the DPS-managed policy, depending on the platform.
Stops active power management for the topology. The topology remains available for later activation or removal.

Deactivation is different from stopping the DPS service. A planned DPS shutdown, accidental DPS server or agent pod deletion, or temporary DPS outage does not send UnsetPolicy. If the BMC remains operational, it continues enforcing its last successfully applied power limits.

Important

Device cleanup is best effort. A successful response confirms that the topology is inactive, but it does not confirm that every BMC accepted the cleanup request. Verify BMC power limits when your maintenance procedure requires a specific hardware state.

Usage#

dpsctl topology deactivate

Flags#

Includes global dpsctl options.

   --topology value    topology name (required)
   --help, -h          show help

Examples#

Basic Usage#

$ dpsctl topology deactivate --topology topology
{
  "status": {
    "ok": true,
    "diag_msg": "Success"
  }
}

Verify Deactivation#

Confirm that no topology is active and that the deactivated topology appears in the inactive list:

dpsctl topology list --active=true
dpsctl topology list --active=false

For outage behavior and maintenance guidance, refer to Topology Deactivation and Loss of DPS Control and Prepare Nodes for Maintenance.