public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Andrei Perapiolkin via pve-devel <pve-devel@lists.proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Cc: Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
Subject: [pve-devel] Volume live migration concurrency
Date: Mon, 26 May 2025 10:31:20 -0400	[thread overview]
Message-ID: <mailman.34.1748269920.395.pve-devel@lists.proxmox.com> (raw)

[-- Attachment #1: Type: message/rfc822, Size: 7095 bytes --]

From: Andrei Perapiolkin <andrei.perepiolkin@open-e.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Volume live migration concurrency
Date: Mon, 26 May 2025 10:31:20 -0400
Message-ID: <6f0ab1f6-2d3f-41e3-8750-2567eb5b947d@open-e.com>

Hi Proxmox Community,

I'm curious whether there are any standard or guidelines that govern the 
order in which the methods: /activate_volume, deactivate_volume, path/ 
are called during VM live migration.

Assuming the storage plugin supports `live migration`:

1. Can/path/ be called before /activate_volume?/

2. When /vm /migrates from/node1/ to/node2, /might /activate_volume/ 
on/node2/ be invoked before /deactivate_volume/ has completed on /node1?
/

3. In the context of live migration: Will Proxmox skip calling 
/deactivate_volume/ for snapshots that have already been activated? 
Should the storage plugin explicitly deactivate all snapshots of a 
volume during migration?


Best regards,

Andrei Perepiolkin

[-- Attachment #2: Type: text/plain, Size: 160 bytes --]

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

             reply	other threads:[~2025-05-26 14:31 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-05-26 14:31 Andrei Perapiolkin via pve-devel [this message]
2025-05-27  7:02 ` Fabian Grünbichler
2025-05-27 16:08   ` Andrei Perapiolkin via pve-devel
     [not found]   ` <4773cf91-8a0f-453d-b9a1-11dcad1a193f@open-e.com>
2025-05-28  7:06     ` Fabian Grünbichler
2025-05-28 14:49       ` Andrei Perapiolkin via pve-devel
     [not found]       ` <9d2b0cf4-7037-491c-b4a4-81538e63376d@open-e.com>
2025-06-02  7:32         ` Fabian Grünbichler

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=mailman.34.1748269920.395.pve-devel@lists.proxmox.com \
    --to=pve-devel@lists.proxmox.com \
    --cc=andrei.perepiolkin@open-e.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