Skip to content
StratumStratum Docs

List a node's memory modules / DIMMs (operator-only).

GET
/v1/compute/nodes/{nodeId}/memory-modules
Code sample: Shell / cURL
curl --request GET \
  --url https://stratum.example.com/v1/compute/nodes/example/memory-modules \
  --header 'Authorization: Bearer <token>'

. Returns the host’s per-slot memory inventory (locator, size, type, speed, manufacturer, part number) for the Metal node Memory tab. Empty slots are included with size 0 so the UI can show how many of the board’s slots are populated.

Read-only inventory parsed from the SMBIOS table (/sys/firmware/dmi/tables/DMI). Cedar action compute:DescribeNode. Platform-tenant.

Authorizations

Section titled “Authorizations”

Parameters

Section titled “Parameters”

Path Parameters

Section titled “Path Parameters”
nodeId
required
string
/^n-[a-z0-9-]+$/

Responses

Section titled “Responses”

200

Section titled “200”

The node’s memory modules.

Media typeapplication/json
object
items
required
Array<object>

One memory slot / DIMM on a node, from SMBIOS.

object
locator
required

SMBIOS device locator (slot), e.g. Controller0-ChannelA-DIMM0.

string
bankLocator
required
string
sizeBytes
required

Module size in bytes; 0 means the slot is empty.

integer format: int64
type
required

DDR4 | DDR5 | LPDDR5 |… (empty when unknown).

string
speedMtps
required

Rated speed in MT/s; 0 when unknown.

integer
manufacturer
required
string
partNumber
required
string

Example generated

{
  "items": [
    {
      "locator": "example",
      "bankLocator": "example",
      "sizeBytes": 1,
      "type": "example",
      "speedMtps": 1,
      "manufacturer": "example",
      "partNumber": "example"
    }
  ]
}

404

Section titled “404”

Resource not found.

Media typeapplication/problem+json
object
type
required
string format: uri
title
required
string
status
required
integer
>= 400 <= 599
detail
string
instance
string format: uri-reference
requestId
required
string
code
required
string
issues

The findings of a rejected IAM policy document (custom and resource policies).

Array<object>

One finding of a rejected IAM policy document. A rejection lists every finding, so the author fixes the document in one round trip.

object
code
required

The finding, e.g. INVALID_DOCUMENT, UNKNOWN_ACTION, ACTION_NOT_APPLICABLE.

string
statement
required

Index of the statement at fault; -1 for the document as a whole.

integer
>= -1
detail
required
string
action

The offending action, where one is at fault (ACTION_NOT_APPLICABLE).

string
errors

Field errors, for codes that carry them: each problem at its field (see FieldError). Documented on the responses that set it, e.g. approveNodeJoin’s INVALID_INPUT and JOIN_APPROVAL_REFUSED. Absent otherwise.

Array<object>

One field’s problem, the stage-2 installer API’s shape. field is the field’s path, message what is wrong with it.

object
field
required

The field’s path, e.g. links[0].interface, disks[1].confirm, mgmt.address or role; empty for the whole request.

string
message
required
string
details

Structured facts about the refusal, for codes that carry them. The shape is fixed per code and documented on the response that answers it, e.g. IMAGE_POOL_MISMATCH (see ImagePoolMismatchDetails) and IMAGE_IN_USE. Absent for codes that carry none.

object
key
additional properties
any

Example 

{
  "issues": [
    {
      "code": "ACTION_NOT_APPLICABLE",
      "action": "compute:CreateVpc"
    }
  ]
}