public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Christian Ebner <c.ebner@proxmox.com>
To: pdm-devel@lists.proxmox.com
Subject: [pdm-devel] [PATCH datacenter-manager v3 14/19] server: resources: extend the PBS resources by config properties
Date: Tue, 21 Oct 2025 13:11:24 +0200	[thread overview]
Message-ID: <20251021111129.294349-15-c.ebner@proxmox.com> (raw)
In-Reply-To: <20251021111129.294349-1-c.ebner@proxmox.com>

At the cost of one additional api call, fetch the datastore list
which includes datastore config properties. Use this to map the
additional information to the `PbsDatastoreResource`.

With the intend to show further datastore information on the
dashboard.

Signed-off-by: Christian Ebner <c.ebner@proxmox.com>
---
Changes since version 2:
- not present in previous version

 server/src/api/resources.rs | 69 ++++++++++++++++++++++++++++++++-----
 1 file changed, 60 insertions(+), 9 deletions(-)

diff --git a/server/src/api/resources.rs b/server/src/api/resources.rs
index fb281f4..793abfc 100644
--- a/server/src/api/resources.rs
+++ b/server/src/api/resources.rs
@@ -6,7 +6,9 @@ use anyhow::{bail, format_err, Error};
 use futures::future::join_all;
 use futures::FutureExt;
 
-use pbs_api_types::{DataStoreStatusListItem, NodeStatus};
+use pbs_api_types::{
+    DataStoreStatusListItem, DatastoreBackendConfig, DatastoreBackendType, NodeStatus,
+};
 use pdm_api_types::remotes::{Remote, RemoteType};
 use pdm_api_types::resource::{
     FailedRemote, PbsDatastoreResource, PbsNodeResource, PveLxcResource, PveNodeResource,
@@ -841,8 +843,18 @@ async fn fetch_remote_resource(remote: &Remote) -> Result<Vec<Resource>, Error>
             let status = client.node_status().await?;
             resources.push(map_pbs_node_status(&remote_name, status));
 
+            let datastores = client.list_datastores().await?;
+            let datastore_map: HashMap<String, pbs_api_types::DataStoreConfig> = datastores
+                .into_iter()
+                .map(|store| (store.name.clone(), store))
+                .collect();
+
             for datastore_usage in client.datastore_usage().await? {
-                resources.push(map_pbs_datastore_status(&remote_name, datastore_usage));
+                resources.push(map_pbs_datastore_status(
+                    &remote_name,
+                    datastore_usage,
+                    &datastore_map,
+                ));
             }
         }
     }
@@ -997,13 +1009,52 @@ fn map_pbs_node_status(remote: &str, status: NodeStatus) -> Resource {
     })
 }
 
-fn map_pbs_datastore_status(remote: &str, status: DataStoreStatusListItem) -> Resource {
-    Resource::PbsDatastore(PbsDatastoreResource {
-        id: format!("remote/{remote}/datastore/{}", status.store),
-        name: status.store,
-        maxdisk: status.total.unwrap_or_default(),
-        disk: status.used.unwrap_or_default(),
-    })
+fn map_pbs_datastore_status(
+    remote: &str,
+    status: DataStoreStatusListItem,
+    datastore_map: &HashMap<String, pbs_api_types::DataStoreConfig>,
+) -> Resource {
+    let maxdisk = status.total.unwrap_or_default();
+    let disk = status.used.unwrap_or_default();
+
+    let usage = if maxdisk > 0 {
+        disk as f64 / maxdisk as f64
+    } else {
+        0.0
+    };
+
+    if let Some(store_config) = datastore_map.get(&status.store) {
+        let mut backend_type = None;
+        if let Some(store_backend) = &store_config.backend {
+            match store_backend.parse::<DatastoreBackendConfig>() {
+                Ok(backend_config) => {
+                    if let Some(DatastoreBackendType::S3) = backend_config.ty {
+                        backend_type = Some(DatastoreBackendType::S3.to_string())
+                    }
+                }
+                Err(_) => backend_type = Some("unknown".to_string()),
+            }
+        }
+        Resource::PbsDatastore(PbsDatastoreResource {
+            id: format!("remote/{remote}/datastore/{}", status.store),
+            name: status.store,
+            maxdisk,
+            disk,
+            usage,
+            maintenance: store_config.maintenance_mode.clone(),
+            backing_device: store_config.backing_device.clone(),
+            backend_type,
+        })
+    } else {
+        Resource::PbsDatastore(PbsDatastoreResource {
+            id: format!("remote/{remote}/datastore/{}", status.store),
+            name: status.store,
+            maxdisk,
+            disk,
+            usage,
+            ..Default::default()
+        })
+    }
 }
 
 #[cfg(test)]
-- 
2.47.3



_______________________________________________
pdm-devel mailing list
pdm-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pdm-devel


  parent reply	other threads:[~2025-10-21 11:11 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-21 11:11 [pdm-devel] [PATCH datacenter-manager v3 00/19] add remote type based search and PBS node status panel to dashboard Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 01/19] server: fix small formatting issue via `cargo fmt` Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 02/19] server: api: pass remote as reference to fetching helpers Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 03/19] server: api: refactor filter logic for resource post gathering Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 04/19] api: resources: new transient type for remote resource gathering Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 05/19] server: api: add remote-type search category for resources Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 06/19] pdm-api-types: extend resource status by list of failed remotes Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 07/19] server: api: collect failed remotes list while getting status Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 08/19] ui: dashboard: reimplement node status panel as dedicated component Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 09/19] ui: dashboard: use new node status component Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 10/19] ui: dashboard: extend node panel creation by remote type Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 11/19] ui: dashboard: expose PBS nodes status panel Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 12/19] pdm-api-types: introduce PBS datastore specific counters Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 13/19] pdm-api-types/resources: extend datastore resources by config properties Christian Ebner
2025-10-21 11:11 ` Christian Ebner [this message]
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 15/19] server: resources: extend datastore status counters by multiple states Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 16/19] pdm-api-types: extend status matching for PBS datastore resources Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 17/19] pdm-api-types: extend resources by properties string generator method Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 18/19] server: resources: add property matching for resources Christian Ebner
2025-10-21 11:11 ` [pdm-devel] [PATCH datacenter-manager v3 19/19] ui: dashboard: add panel for PBS datastore statistics Christian Ebner
2025-10-23 21:23 ` [pdm-devel] [PATCH datacenter-manager v3 00/19] add remote type based search and PBS node status panel to dashboard Thomas Lamprecht

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=20251021111129.294349-15-c.ebner@proxmox.com \
    --to=c.ebner@proxmox.com \
    --cc=pdm-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
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal