public inbox for pdm-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Lukas Wagner <l.wagner@proxmox.com>, pdm-devel@lists.proxmox.com
Subject: Re: [PATCH datacenter-manager v2 16/20] api-cache: add wrapper type
Date: Mon, 24 Aug 2026 14:33:39 +0200	[thread overview]
Message-ID: <20fd1678-99b3-44d4-917d-f27d519bef0d@proxmox.com> (raw)
In-Reply-To: <20260820145220.418032-17-l.wagner@proxmox.com>

i'm missing a bit here why we need a wrapper around a type we fully
control here? couldn't we use NamespacedCache directly?

what advantage has wrapping it in this way?

To me it's not immediately obvious, so a short sentence
in the commit message or as comment on the struct, would be good.

On 8/20/26 4:52 PM, Lukas Wagner wrote:
> Wrap the underlying NamespacedCache in a new ApiCache type that
> exposes the same read/write helpers as methods. The global CACHE
> static and its free functions remain, just implemented as thin
> wrappers around the new type, so this only prepares ApiCache to be
> owned by PdmApplication in the next commit.
> 
> Signed-off-by: Lukas Wagner <l.wagner@proxmox.com>
> ---
>   server/src/api_cache.rs | 98 +++++++++++++++++++++++++++++++++++------
>   1 file changed, 84 insertions(+), 14 deletions(-)
> 
> diff --git a/server/src/api_cache.rs b/server/src/api_cache.rs
> index b20f0535..6dc8a043 100644
> --- a/server/src/api_cache.rs
> +++ b/server/src/api_cache.rs
> @@ -59,6 +59,8 @@ use std::time::Duration;
>   
>   use nix::sys::stat::Mode;
>   
> +use proxmox_sys::fs::CreateOptions;
> +
>   use crate::namespaced_cache::{
>       BlockingReadableCacheNamespace, BlockingWritableCacheNamespace, CacheError, NamespacedCache,
>       ReadableCacheNamespace, WritableCacheNamespace,
> @@ -70,57 +72,125 @@ pub const PDM_API_CACHE_PATH: &str = concat!(pdm_buildcfg::PDM_RUN_DIR_M!(), "/a
>   const GLOBAL_NAMESPACE: &str = "global";
>   const LOCK_TIMEOUT: Duration = Duration::from_secs(10);
>   
> -static CACHE: LazyLock<NamespacedCache> = LazyLock::new(|| {
> +static CACHE: LazyLock<ApiCache> = LazyLock::new(|| {
>       let file_options = proxmox_product_config::default_create_options();
>       let dir_options = file_options.perm(Mode::from_bits_truncate(0o750));
>   
> -    NamespacedCache::new(PathBuf::from(PDM_API_CACHE_PATH), dir_options, file_options)
> +    ApiCache::new(PathBuf::from(PDM_API_CACHE_PATH), dir_options, file_options)
>   });
>   
>   fn format_remote_namespace(remote: &str) -> String {
>       format!("remote-{remote}")
>   }
>   
> +/// Cache for API responses from remotes.
> +///
> +/// Thin wrapper around a [`NamespacedCache`], providing remote-specific and
> +/// global namespaces as described in the module documentation.
> +pub struct ApiCache {
> +    cache: NamespacedCache,
> +}
> +
> +impl ApiCache {
> +    pub fn new<P: Into<PathBuf>>(
> +        base_directory: P,
> +        dir_options: CreateOptions,
> +        file_options: CreateOptions,
> +    ) -> Self {
> +        Self {
> +            cache: NamespacedCache::new(base_directory, dir_options, file_options),
> +        }
> +    }
> +
> +    /// Lock the cache for reading remote-specific data (blocking interface).
> +    pub fn read_remote_blocking(
> +        &self,
> +        remote: &str,
> +    ) -> Result<BlockingReadableCacheNamespace, CacheError> {
> +        self.cache
> +            .read_blocking(&format_remote_namespace(remote), LOCK_TIMEOUT)
> +    }
> +
> +    /// Lock the cache for writing remote-specific data (blocking interface).
> +    pub fn write_remote_blocking(
> +        &self,
> +        remote: &str,
> +    ) -> Result<BlockingWritableCacheNamespace, CacheError> {
> +        self.cache
> +            .write_blocking(&format_remote_namespace(remote), LOCK_TIMEOUT)
> +    }
> +
> +    /// Lock the cache for reading global data (blocking interface).
> +    pub fn read_global_blocking(&self) -> Result<BlockingReadableCacheNamespace, CacheError> {
> +        self.cache.read_blocking(GLOBAL_NAMESPACE, LOCK_TIMEOUT)
> +    }
> +
> +    /// Lock the cache for writing global data (blocking interface).
> +    pub fn write_global_blocking(&self) -> Result<BlockingWritableCacheNamespace, CacheError> {
> +        self.cache.write_blocking(GLOBAL_NAMESPACE, LOCK_TIMEOUT)
> +    }
> +
> +    /// Lock the cache for reading remote-specific data (async interface).
> +    pub async fn read_remote(&self, remote: &str) -> Result<ReadableCacheNamespace, CacheError> {
> +        self.cache
> +            .read(&format_remote_namespace(remote), LOCK_TIMEOUT)
> +            .await
> +    }
> +
> +    /// Lock the cache for writing remote-specific data (async interface).
> +    pub async fn write_remote(&self, remote: &str) -> Result<WritableCacheNamespace, CacheError> {
> +        self.cache
> +            .write(&format_remote_namespace(remote), LOCK_TIMEOUT)
> +            .await
> +    }
> +
> +    /// Lock the cache for reading global data (async interface).
> +    pub async fn read_global(&self) -> Result<ReadableCacheNamespace, CacheError> {
> +        self.cache.read(GLOBAL_NAMESPACE, LOCK_TIMEOUT).await
> +    }
> +
> +    /// Lock the cache for writing global data (async interface).
> +    pub async fn write_global(&self) -> Result<WritableCacheNamespace, CacheError> {
> +        self.cache.write(GLOBAL_NAMESPACE, LOCK_TIMEOUT).await
> +    }
> +}
> +
>   /// Lock the cache for reading remote-specific data (blocking interface).
>   pub fn read_remote_blocking(remote: &str) -> Result<BlockingReadableCacheNamespace, CacheError> {
> -    CACHE.read_blocking(&format_remote_namespace(remote), LOCK_TIMEOUT)
> +    CACHE.read_remote_blocking(remote)
>   }
>   
>   /// Lock the cache for writing remote-specific data (blocking interface).
>   pub fn write_remote_blocking(remote: &str) -> Result<BlockingWritableCacheNamespace, CacheError> {
> -    CACHE.write_blocking(&format_remote_namespace(remote), LOCK_TIMEOUT)
> +    CACHE.write_remote_blocking(remote)
>   }
>   
>   /// Lock the cache for reading global data (blocking interface).
>   pub fn read_global_blocking() -> Result<BlockingReadableCacheNamespace, CacheError> {
> -    CACHE.read_blocking(GLOBAL_NAMESPACE, LOCK_TIMEOUT)
> +    CACHE.read_global_blocking()
>   }
>   
>   /// Lock the cache for writing global data (blocking interface).
>   pub fn write_global_blocking() -> Result<BlockingWritableCacheNamespace, CacheError> {
> -    CACHE.write_blocking(GLOBAL_NAMESPACE, LOCK_TIMEOUT)
> +    CACHE.write_global_blocking()
>   }
>   
>   /// Lock the cache for reading remote-specific data (async interface).
>   pub async fn read_remote(remote: &str) -> Result<ReadableCacheNamespace, CacheError> {
> -    CACHE
> -        .read(&format_remote_namespace(remote), LOCK_TIMEOUT)
> -        .await
> +    CACHE.read_remote(remote).await
>   }
>   
>   /// Lock the cache for writing remote-specific data (async interface).
>   pub async fn write_remote(remote: &str) -> Result<WritableCacheNamespace, CacheError> {
> -    CACHE
> -        .write(&format_remote_namespace(remote), LOCK_TIMEOUT)
> -        .await
> +    CACHE.write_remote(remote).await
>   }
>   
>   /// Lock the cache for reading global data (async interface).
>   pub async fn read_global() -> Result<ReadableCacheNamespace, CacheError> {
> -    CACHE.read(GLOBAL_NAMESPACE, LOCK_TIMEOUT).await
> +    CACHE.read_global().await
>   }
>   
>   /// Lock the cache for writing global data (async interface).
>   pub async fn write_global() -> Result<WritableCacheNamespace, CacheError> {
> -    CACHE.write(GLOBAL_NAMESPACE, LOCK_TIMEOUT).await
> +    CACHE.write_global().await
>   }





  reply	other threads:[~2026-08-24 12:33 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-20 14:52 [PATCH datacenter-manager/proxmox v2 00/20] inject application context via API macro for easier integration testing Lukas Wagner
2026-08-20 14:52 ` [PATCH proxmox v2 01/20] router: introduce shared state Lukas Wagner
2026-08-20 14:52 ` [PATCH proxmox v2 02/20] rest-server: allow to inject " Lukas Wagner
2026-08-20 14:52 ` [PATCH proxmox v2 03/20] api-macro: support shared state extraction type Lukas Wagner
2026-08-24 12:33   ` Dominik Csapak
2026-08-24 13:17     ` Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 04/20] context: promote context to a dir-style module Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 05/20] pdm-config: remotes: rename trait methods to read/write/lock Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 06/20] pdm-config: subscriptions: " Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 07/20] remote iterator: pass remote config reader explicitly Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 08/20] context: introduce a ContextFactory to build application context Lukas Wagner
2026-08-24 12:33   ` Dominik Csapak
2026-08-24 13:48     ` Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 09/20] context: establish PdmApplication object Lukas Wagner
2026-08-21  9:52   ` Thomas Ellmenreich
2026-08-21 12:26     ` Lukas Wagner
2026-08-24 12:33   ` Dominik Csapak
2026-08-24 13:23     ` Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 10/20] context: register PdmApplication in router Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 11/20] parallel fetcher: pass arguments to closure in a single type Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 12/20] parallel fetcher: support a custom client factory Lukas Wagner
2026-08-24 12:33   ` Dominik Csapak
2026-08-24 13:42     ` Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 13/20] api: sdn: use PdmApplication handle for accessing remotes Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 14/20] tests: add helpers for building API-handler-level integration tests Lukas Wagner
2026-08-21  9:57   ` Thomas Ellmenreich
2026-08-21 12:25     ` Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 15/20] tests: add example tests for SDN API routes Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 16/20] api-cache: add wrapper type Lukas Wagner
2026-08-24 12:33   ` Dominik Csapak [this message]
2026-08-24 13:47     ` Lukas Wagner
2026-08-24 13:57       ` Dominik Csapak
2026-08-20 14:52 ` [PATCH datacenter-manager v2 17/20] context: provide api-cache on the app object Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 18/20] api: subscriptions: use PdmApplication instead of globals Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 19/20] pdm-config: subscriptions: drop unused accessor functions Lukas Wagner
2026-08-20 14:52 ` [PATCH datacenter-manager v2 20/20] tests: add example tests for remote subscription management Lukas Wagner
2026-08-24 12:33 ` [PATCH datacenter-manager/proxmox v2 00/20] inject application context via API macro for easier integration testing Dominik Csapak

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=20fd1678-99b3-44d4-917d-f27d519bef0d@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=l.wagner@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