export

dpsctl topology export Usage Guide

Export the named topology to JSON. By default, export includes the topology and the entities it references. Use --entities to include every entity in the database.

Usage

dpsctl topology export

Flags

Includes global dpsctl options.

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

Examples

Default Export

$ dpsctl topology export --topology datacenter
{
  "Entities": [
    {
      "Type": "PowerDomain",
      "Name": "PD-A",
      "OperatingLimit": {
        "PowerValue": {
          "Value": 1150000,
          "Type": "W"
        },
        "PowerFactor": 0.9
      }
    },
    {
      "Type": "ComputerSystem",
      "Model": "DGX_H100",
      "Name": "node001"
    }
  ],
  "Topology": {
    "Name": "datacenter",
    "Entities": [
      {
        "Name": "PD-A",
        "Children": ["node001"]
      },
      {
        "Name": "node001"
      }
    ]
  }
}

Export with All Entities

$ dpsctl topology export --topology datacenter --entities

The output uses the same Entities and Topology members. --entities includes entities that are not referenced by the topology.

Save to File

$ dpsctl topology export --topology datacenter > exported-topology.json

Notes

• Exported JSON uses Entities and Topology. Remove a nonempty Policies member before re-import.

• Exported JSON is compatible with dpsctl topology import, but it is not a complete portable configuration.

• Export sanitization deliberately removes topologyHash. API clients can get the hash from the GetTopologyModel response header when preparing a non-forced API update.

• The current Go CLI update limitations are documented in update.

• Use --entities to include every entity in the database rather than only topology members.

• Export does not include the topology’s persisted policy-bundle selection. Recreate bundles with dpsctl policy bundle upsert. To recreate the intended power behavior in another DPS instance:

  1. Upsert the source topology’s selected typed bundle on the destination.

  2. Before importing, ensure the destination’s global_policy_bundle resolves to that bundle. If you change the setting for import, restore its saved value afterward.

  3. After import, use dpsctl topology list to verify the imported topology’s policy_bundle.

• An exported entity policy value is legacy. It does not restore the typed bundle selection.

• Refer to policy-bundle selection for resolution and lifecycle behavior.