From: Shan Shaji <s.shaji@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: [PATCH proxmox v2 6/6] pve-api-types: update API dump for /node/status and regenerate types
Date: Wed, 2 Sep 2026 16:59:44 +0200 [thread overview]
Message-ID: <20260902145944.365185-7-s.shaji@proxmox.com> (raw)
In-Reply-To: <20260902145944.365185-1-s.shaji@proxmox.com>
Adds `uptime` and `idle` properties to the NodeStatus struct.
Signed-off-by: Shan Shaji <s.shaji@proxmox.com>
---
pve-api-types/pve-api.json | 10 ++++++++++
pve-api-types/src/generated/types.rs | 16 ++++++++++++++++
2 files changed, 26 insertions(+)
diff --git a/pve-api-types/pve-api.json b/pve-api-types/pve-api.json
index 1006538e..7e77070e 100644
--- a/pve-api-types/pve-api.json
+++ b/pve-api-types/pve-api.json
@@ -56178,6 +56178,11 @@
},
"type": "object"
},
+ "idle": {
+ "description": "Sum of how much time each core has spent idle, in seconds.",
+ "minimum": 0,
+ "type": "integer"
+ },
"loadavg": {
"description": "An array of load avg for 1, 5 and 15 minutes respectively.",
"items": {
@@ -56231,6 +56236,11 @@
}
},
"type": "object"
+ },
+ "uptime": {
+ "description": "The uptime of the system (including time spent in suspend), in seconds.",
+ "minimum": 0,
+ "type": "integer"
}
},
"type": "object"
diff --git a/pve-api-types/src/generated/types.rs b/pve-api-types/src/generated/types.rs
index 129f82ed..3a1e4951 100644
--- a/pve-api-types/src/generated/types.rs
+++ b/pve-api-types/src/generated/types.rs
@@ -11487,6 +11487,10 @@ pub struct NodeShellTicket {
"current-kernel": {
type: NodeStatusCurrentKernel,
},
+ idle: {
+ minimum: 0,
+ type: Integer,
+ },
loadavg: {
items: {
description: "The value of the load.",
@@ -11503,6 +11507,10 @@ pub struct NodeShellTicket {
rootfs: {
type: NodeStatusRootfs,
},
+ uptime: {
+ minimum: 0,
+ type: Integer,
+ },
},
)]
/// Object.
@@ -11522,6 +11530,10 @@ pub struct NodeStatus {
#[serde(rename = "current-kernel")]
pub current_kernel: NodeStatusCurrentKernel,
+ /// Sum of how much time each core has spent idle, in seconds.
+ #[serde(deserialize_with = "proxmox_serde::perl::deserialize_u64")]
+ pub idle: u64,
+
/// An array of load avg for 1, 5 and 15 minutes respectively.
pub loadavg: Vec<String>,
@@ -11532,6 +11544,10 @@ pub struct NodeStatus {
pub rootfs: NodeStatusRootfs,
+ /// The uptime of the system (including time spent in suspend), in seconds.
+ #[serde(deserialize_with = "proxmox_serde::perl::deserialize_u64")]
+ pub uptime: u64,
+
#[serde(flatten)]
pub additional_properties: HashMap<String, Value>,
}
--
2.47.3
prev parent reply other threads:[~2026-09-02 15:00 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-02 14:59 [PATCH manager/proxmox{-yew-comp,} v2 0/6] add missing uptime to the GUI, update API dump, and regenerate pve-api-types Shan Shaji
2026-09-02 14:59 ` [PATCH pve-manager v2 1/6] fix: nodes: update `idle` key value in hash reference Shan Shaji
2026-09-02 14:59 ` [PATCH pve-manager v2 2/6] fix: node: add missing `uptime` property inside the return schema Shan Shaji
2026-09-02 14:59 ` [PATCH proxmox-yew-comp v2 3/6] fix #7932: add missing uptime to the GUI Shan Shaji
2026-09-02 14:59 ` [PATCH proxmox v2 4/6] chore: pve-api-types: update API dump and regenerate types Shan Shaji
2026-09-02 14:59 ` [PATCH proxmox v2 5/6] pve-api-types: register missing pve-fw-comment-spec verify function Shan Shaji
2026-09-02 14:59 ` Shan Shaji [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20260902145944.365185-7-s.shaji@proxmox.com \
--to=s.shaji@proxmox.com \
--cc=pve-devel@lists.proxmox.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox