import
dpsctl bcm import Usage Guide
Generate DPS entities from Base Cluster Manager (BCM) inventory.
Usage
dpsctl bcm importFlags
Includes global dpsctl options.
--url value BCM URL (required)
--username value BCM username (required)
--password value BCM password (required)
--tls-insecure-skip-verify BCM TLS insecure skip verify
--help, -h show helpExamples
Basic Import
$ dpsctl bcm import \
--url https://bcm.example.com:8443 \
--username admin \
--password secretpassword
[
{
"name": "node001",
"type": "ComputerSystem",
"model": "DGX_H100",
"redfish": {
"@odata.type": "#ComputerSystem.v1_23_0.ComputerSystem",
"@odata.id": "/node001",
"id": "node001",
"url": "https://node001-bmc.example.com",
"secret_name": "node001"
}
},
{
"name": "node002",
"type": "ComputerSystem",
"model": "DGX_H100",
"redfish": {
"@odata.type": "#ComputerSystem.v1_23_0.ComputerSystem",
"@odata.id": "/node002",
"id": "node002",
"url": "https://node002-bmc.example.com",
"secret_name": "node002"
}
}
]Import with TLS Skip Verify
$ dpsctl bcm import \
--url https://bcm.example.com:8443 \
--username admin \
--password secretpassword \
--tls-insecure-skip-verifySave Output to File
$ dpsctl bcm import \
--url https://bcm.example.com:8443 \
--username admin \
--password secretpassword > entities.jsonNotes
- Requires BCM version 11 or later
- Generated entities can be saved to a file and imported into DPS topology
- BCM credentials must have sufficient privileges to read cluster inventory
- The output format is compatible with DPS topology import format
- Generated entities will include BMC URLs and credential references