From: Wolfgang Bumiller <w.bumiller@proxmox.com>
To: Gabriel Goller <g.goller@proxmox.com>
Cc: pbs-devel@lists.proxmox.com
Subject: [pbs-devel] applied: [PATCH proxmox-backup] fix: proxmox-backup-manager network reload wait on worker
Date: Thu, 29 Aug 2024 14:17:46 +0200 [thread overview]
Message-ID: <ozfohkma3enwnuk2cj6gnzqzcteexwysxsn7ul75xsv7hfsnrt@2kic5ojtb2h7> (raw)
In-Reply-To: <20240821102236.220755-1-g.goller@proxmox.com>
applied, thanks
On Wed, Aug 21, 2024 at 12:22:36PM GMT, Gabriel Goller wrote:
> Make the `network reload` command in proxmox-backup-manager wait on the
> api handler's workertask. Otherwise the task would be killed when the
> client exits.
>
> Signed-off-by: Gabriel Goller <g.goller@proxmox.com>
> ---
> src/bin/proxmox_backup_manager/network.rs | 21 +++++++++++++++++++--
> 1 file changed, 19 insertions(+), 2 deletions(-)
>
> diff --git a/src/bin/proxmox_backup_manager/network.rs b/src/bin/proxmox_backup_manager/network.rs
> index deac5b1b2960..0f0a50a8932a 100644
> --- a/src/bin/proxmox_backup_manager/network.rs
> +++ b/src/bin/proxmox_backup_manager/network.rs
> @@ -129,6 +129,24 @@ fn pending_network_changes(
> Ok(Value::Null)
> }
>
> +#[api()]
> +/// Reload network changes
> +async fn reload_network_changes(
> + mut param: Value,
> + rpcenv: &mut dyn RpcEnvironment,
> +) -> Result<Value, Error> {
> + param["node"] = "localhost".into();
> +
> + let info = &api2::node::network::API_METHOD_RELOAD_NETWORK_CONFIG;
> + let result = match info.handler {
> + ApiHandler::Async(handler) => (handler)(param, info, rpcenv).await?,
> + _ => unreachable!(),
> + };
Note: we have the above pattern a lot. For `Schema` we already have a
bunch of `const fn unwrap_<type>_schema()`.
We can now also use `const {}` expressions, so maybe we should have
something like this for `ApiHandler` as well, with all these handler
functions then using something like:
let handler = const { info.handler.unwrap_async_handler() };
let result = (handler)(param, info, rpcenv).await?
> + crate::wait_for_local_worker(result.as_str().unwrap()).await?;
> +
> + Ok(Value::Null)
> +}
> +
> pub fn network_commands() -> CommandLineInterface {
> let cmd_def = CliCommandMap::new()
> .insert("list", CliCommand::new(&API_METHOD_LIST_NETWORK_DEVICES))
> @@ -168,8 +186,7 @@ pub fn network_commands() -> CommandLineInterface {
> )
> .insert(
> "reload",
> - CliCommand::new(&api2::node::network::API_METHOD_RELOAD_NETWORK_CONFIG)
> - .fixed_param("node", String::from("localhost")),
> + CliCommand::new(&API_METHOD_RELOAD_NETWORK_CHANGES),
> );
>
> cmd_def.into()
> --
> 2.39.2
_______________________________________________
pbs-devel mailing list
pbs-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pbs-devel
next prev parent reply other threads:[~2024-08-29 12:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-21 10:22 [pbs-devel] " Gabriel Goller
2024-08-29 12:17 ` Wolfgang Bumiller [this message]
2024-08-30 8:18 ` [pbs-devel] applied: " Gabriel Goller
2024-08-30 9:00 ` Wolfgang Bumiller
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=ozfohkma3enwnuk2cj6gnzqzcteexwysxsn7ul75xsv7hfsnrt@2kic5ojtb2h7 \
--to=w.bumiller@proxmox.com \
--cc=g.goller@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox