Skip to navigation
Operations

Inventory and Device Info

View as Markdown

See Operations Overview for the conventions (in-band failures, registered vs. ephemeral targets) referenced below.

Inventory

Node and rack registration. All synchronous.

RPCBehaviorKey inputsKey outputs
CreateNodesRegister a batch of nodes, auto-creating the owning rack. Every node requires a stable BMC endpoint; a host endpoint is optional (switches may be BMC-only).nodes (NodeSet)OperationResponse, stats
ListNodeInventoryEnumerate all nodes across all racks.-nodes[] (id, rack, type, descriptor, addresses)
ListRacksList all rack IDs.-rack_ids[]
DeleteNodeRemove one node from its rack (holds the rack power guard).rack_id, node_idOperationResponse
UpdateNodeNot implemented - always returns Failure.--

NodeDescriptor accepts an optional inventory_profile attribute in addition to the canonical role, vendor, and product_family identity attributes. The value is an opaque deployment-defined key configured in [workflows.expected_inventory_profiles]. Profiles can contain expected NVFWUPD AP names and physical Flint device counts. CreateNodes rejects empty or unknown supplied profiles, while omission preserves legacy behavior. ListNodeInventory returns the selected profile.

CreateNodes succeeds only when no nodes fail. DeleteNode is refused while a registered power operation is running on the rack (the operation resolves its node from current inventory).

Device info

Tray/chassis location and topology info (chassis serial, slot number, tray index). All synchronous.

RPCBehaviorKey inputsKey outputs
GetNodeDeviceInfoDevice info for one registered node.rack_id, node_iddevice_info? (may be absent for node types without it)
ListNodeDeviceInfoByNodeTypeDevice info for all registered nodes of a type in a rack.rack_id, node_typenode_device_details[], stats
BatchGetNodeDeviceInfoDevice info for a caller-supplied ephemeral node set. Delta power-shelf types are rejected.nodesnode_device_details[], stats

Node types that expose no device info return Success with an explanatory message and no device_info payload.