all lists on lists.proxmox.com
 help / color / mirror / Atom feed
From: Arthur Bied-Charreton <a.bied-charreton@proxmox.com>
To: Hannes Laimer <h.laimer@proxmox.com>
Cc: pbs-devel@lists.proxmox.com
Subject: Re: [PATCH proxmox-backup v6 8/8] cli: add move-namespace and move-group commands
Date: Thu, 2 Apr 2026 11:22:44 +0200	[thread overview]
Message-ID: <v7zsyjiwdfthr22kaczayuj4stywd6hucpqvekkx2c3742cpfv@oszch73othmj> (raw)
In-Reply-To: <20260331123409.198353-9-h.laimer@proxmox.com>

On Tue, Mar 31, 2026 at 02:34:09PM +0200, Hannes Laimer wrote:
> Add 'move-namespace' and 'move-group' subcommands to
> proxmox-backup-manager datastore. Both call the corresponding API
> handler and wait for the worker task to complete.
> 
> Signed-off-by: Hannes Laimer <h.laimer@proxmox.com>
Hey, one comment & one nit inline
> ---
>  src/bin/proxmox_backup_manager/datastore.rs | 84 ++++++++++++++++++++-
>  1 file changed, 83 insertions(+), 1 deletion(-)
> 
> diff --git a/src/bin/proxmox_backup_manager/datastore.rs b/src/bin/proxmox_backup_manager/datastore.rs
> index 5c65c5ec..2ee56fba 100644
> --- a/src/bin/proxmox_backup_manager/datastore.rs
> +++ b/src/bin/proxmox_backup_manager/datastore.rs
> @@ -1,5 +1,6 @@
>  use pbs_api_types::{
> -    DataStoreConfig, DataStoreConfigUpdater, DATASTORE_SCHEMA, PROXMOX_CONFIG_DIGEST_SCHEMA,
> +    BackupNamespace, DataStoreConfig, DataStoreConfigUpdater, DATASTORE_SCHEMA,
> +    PROXMOX_CONFIG_DIGEST_SCHEMA,
>  };
>  use pbs_client::view_task_result;
>  use proxmox_router::{cli::*, ApiHandler, RpcEnvironment};
> @@ -323,6 +324,75 @@ async fn uuid_mount(mut param: Value, _rpcenv: &mut dyn RpcEnvironment) -> Resul
>      Ok(Value::Null)
>  }
>  
> +#[api(
> +    protected: true,
> +    input: {
> +        properties: {
> +            store: {
> +                schema: DATASTORE_SCHEMA,
> +            },
> +            ns: {
> +                type: BackupNamespace,
> +            },
> +            "new-ns": {
> +                type: BackupNamespace,
> +            },
> +        },
> +    },
> +)]
> +/// Move a backup namespace to a new location within the same datastore.
> +async fn cli_move_namespace(
> +    mut param: Value,
> +    rpcenv: &mut dyn RpcEnvironment,
> +) -> Result<(), Error> {
> +    param["node"] = "localhost".into();
> +
> +    let info = &api2::admin::namespace::API_METHOD_MOVE_NAMESPACE;
> +    let result = match info.handler {
> +        ApiHandler::Sync(handler) => (handler)(param, info, rpcenv)?,
> +        _ => unreachable!(),
> +    };
> +
> +    crate::wait_for_local_worker(result.as_str().unwrap()).await?;
> +    Ok(())
> +}
nit: The `move-namespace` command outputs a log message from
`DataStore::with_store_and_config` ("using datastore cache ...").
That's unrelated to these changes, but it's a little confusing since
that ends up being the only output you get when moving a namespace.
IMO this would benefit from some kind of success message to make it 
clear that the move happened.
> +
> +#[api(
> +    protected: true,
> +    input: {
> +        properties: {
> +            store: {
> +                schema: DATASTORE_SCHEMA,
> +            },
> +            ns: {
> +                type: BackupNamespace,
> +                optional: true,
> +            },
> +            group: {
> +                type: pbs_api_types::BackupGroup,
> +                flatten: true,
> +            },
> +            "new-ns": {
> +                type: BackupNamespace,
> +                optional: true,
> +            },
> +        },
> +    },
> +)]
> +/// Move a backup group to a different namespace within the same datastore.
> +async fn cli_move_group(mut param: Value, rpcenv: &mut dyn RpcEnvironment) -> Result<(), Error> {
> +    param["node"] = "localhost".into();
> +
> +    let info = &api2::admin::datastore::API_METHOD_MOVE_GROUP;
> +    let result = match info.handler {
> +        ApiHandler::Sync(handler) => (handler)(param, info, rpcenv)?,
> +        _ => unreachable!(),
> +    };
> +
> +    crate::wait_for_local_worker(result.as_str().unwrap()).await?;
> +    Ok(())
> +}
It is not clear to me why not setting a source/target operand should
automatically imply the root namespace. I assume this is to reflect the
actual namespace structure, where root is actually stored as '', but I
think it would be cleaner if there was a way to make it explicit, or if
that's not possible (not sure if there is even a keyword we can reserve
for this), at least document it.
>  #[api(
>      protected: true,
>      input: {
> @@ -407,6 +477,18 @@ pub fn datastore_commands() -> CommandLineInterface {
>              CliCommand::new(&API_METHOD_DELETE_DATASTORE)
>                  .arg_param(&["name"])
>                  .completion_cb("name", pbs_config::datastore::complete_datastore_name),
> +        )
> +        .insert(
> +            "move-namespace",
> +            CliCommand::new(&API_METHOD_CLI_MOVE_NAMESPACE)
> +                .arg_param(&["store"])
> +                .completion_cb("store", pbs_config::datastore::complete_datastore_name),
> +        )
> +        .insert(
> +            "move-group",
> +            CliCommand::new(&API_METHOD_CLI_MOVE_GROUP)
> +                .arg_param(&["store"])
> +                .completion_cb("store", pbs_config::datastore::complete_datastore_name),
>          );
>  
>      cmd_def.into()
> -- 
> 2.47.3
> 
> 
> 
> 
> 




  reply	other threads:[~2026-04-02  9:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 12:34 [PATCH proxmox-backup v6 0/8] fixes #6195: add support for moving groups and namespaces Hannes Laimer
2026-03-31 12:34 ` [PATCH proxmox-backup v6 1/8] ui: show empty groups Hannes Laimer
2026-03-31 12:34 ` [PATCH proxmox-backup v6 2/8] datastore: add move_group Hannes Laimer
2026-03-31 12:34 ` [PATCH proxmox-backup v6 3/8] datastore: add move_namespace Hannes Laimer
2026-03-31 12:34 ` [PATCH proxmox-backup v6 4/8] api: add PUT endpoint for move_group Hannes Laimer
2026-03-31 12:34 ` [PATCH proxmox-backup v6 5/8] api: add PUT endpoint for move_namespace Hannes Laimer
2026-03-31 12:34 ` [PATCH proxmox-backup v6 6/8] ui: add move group action Hannes Laimer
2026-03-31 12:34 ` [PATCH proxmox-backup v6 7/8] ui: add move namespace action Hannes Laimer
2026-04-02  9:28   ` Arthur Bied-Charreton
2026-03-31 12:34 ` [PATCH proxmox-backup v6 8/8] cli: add move-namespace and move-group commands Hannes Laimer
2026-04-02  9:22   ` Arthur Bied-Charreton [this message]
2026-04-02  9:34 ` [PATCH proxmox-backup v6 0/8] fixes #6195: add support for moving groups and namespaces Arthur Bied-Charreton

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=v7zsyjiwdfthr22kaczayuj4stywd6hucpqvekkx2c3742cpfv@oszch73othmj \
    --to=a.bied-charreton@proxmox.com \
    --cc=h.laimer@proxmox.com \
    --cc=pbs-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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.
Service provided by Proxmox Server Solutions GmbH | Privacy | Legal