Skip to content
StratumStratum Docs

Raw LVM diagnostic view of a node (operator-only).

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

. Returns the node’s volume groups with their physical and logical volumes (the vgs/pvs/lvs view), parsed to structured JSON. The queries bypass the LVM devices file (use_devicesfile=0), so EVERY VG is returned — host-created and control-plane-created pools alike (the scoping that hid control-plane pools from host vgs).

Read-only diagnostic — pool lifecycle stays on the storage-pools API. Cedar action compute:DescribeNode.

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 LVM view.

Media typeapplication/json

Raw LVM diagnostic view of a node — every volume group with its physical + logical volumes, devices-file bypassed so all VGs show.

Answers for ANY node, not just the one serving the request. The serving node is collected live; every other node is served from its own self-reported inventory, so collectedAt says how fresh that is.

An empty volumeGroups means the node reported and genuinely has none. A node that has never reported returns 503 NODE_LVM_NOT_REPORTED instead, because “no volume groups” and “cannot see this node” are different answers and used to render identically.

object
volumeGroups
required
Array<object>
object
name
required
string
attr
required

Vgs lv_attr-style flags (e.g. wz–n-).

string
sizeBytes
required
integer format: int64
freeBytes
required
integer format: int64
pvCount
required
integer
lvCount
required
integer
physicalVolumes
required
Array<object>
object
path
required
string
sizeBytes
required
integer format: int64
freeBytes
required
integer format: int64
logicalVolumes
required
Array<object>
object
name
required
string
attr
required

Lvs lv_attr flags (e.g. twi-aotz–).

string
sizeBytes
required
integer format: int64
type
required

LVM segment type (e.g. thin-pool, thin, linear).

string
poolLv

For a thin volume, the thin pool LV it belongs to.

string
collectedAt

When this inventory was gathered. Absent for the node serving the request, whose view is collected live at request time; present for any other node, where it is that node’s last self-report. Read it before trusting a peer’s data: a node that stopped reporting an hour ago should not look the same as one reporting now.

string format: date-time

Example generated

{
  "volumeGroups": [
    {
      "name": "example",
      "attr": "example",
      "sizeBytes": 1,
      "freeBytes": 1,
      "pvCount": 1,
      "lvCount": 1,
      "physicalVolumes": [
        {
          "path": "example",
          "sizeBytes": 1,
          "freeBytes": 1
        }
      ],
      "logicalVolumes": [
        {
          "name": "example",
          "attr": "example",
          "sizeBytes": 1,
          "type": "example",
          "poolLv": "example"
        }
      ]
    }
  ],
  "collectedAt": "2026-04-15T12:00:00Z"
}

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"
    }
  ]
}