public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: "Dominic Jäger" <d.jaeger@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH v4 serries 0/4] disk reassign: add new feature
Date: Thu, 19 Nov 2020 11:54:20 +0100	[thread overview]
Message-ID: <20201119105420.GA66443@mala.proxmox.com> (raw)
In-Reply-To: <8ca313df-8bec-72da-3b2a-55a289b2a02d@proxmox.com>

Gave it a quick test: Moving some disks from one VM to another on a CIFS
storage worked for me.  Had to do some conflict resolution upon application
though.
=> If (there is more feedback and) you rebase it, then I can test it (+ GUI) more thoroughly :)

I would probably rename the parameter name drive_key for qm to something that
already exists in our code, because to me it looks like we have different names
for it already
 - Bus/Device in the GUI
 - the word (ide, scsi)  is called Bus/Controller in man qm
 - the word is called interface (of a drive) in QemuServer.pm
 - we have $deviceid =~ m/^(virtio)(\d+)$/ in qemu-server, so the whole word+integer
 - and also "my $drive_id = "$drive->{interface}$drive->{index}";
 - we have "{drive_name} may be used to specify ide0, scsi1, etc ..." in the (old) Importdisk.pm
 - and in ControllerSelector.js the first half is controller and the integer is deviceid

And for me it would make sense to minimize those differences.

Tested-by: Dominic Jäger <d.jaeger@proxmox.com>

On Fri, Oct 30, 2020 at 11:42:23AM +0100, Aaron Lauterer wrote:
> Does anyone have time to take a look at the latest iteration of these patches?
> 
> Thx :)
> 
> On 10/2/20 10:23 AM, Aaron Lauterer wrote:
> > deleted as well because it still had the VMID of VM A in it's name.
> > 
> > To issue a reassign from the CLI run:
> > 
> > qm reassign_disk <source VMID> <target VMID> <drive key>
> > 
> > where <drive key> is the config key of the disk, e.g. ide0, scsi1 and so
> > on.
> > 
> > The following storage types are implemented at the moment:
> > * dir based ones
> >      * CIFS




      reply	other threads:[~2020-11-19 10:54 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-02  8:23 Aaron Lauterer
2020-10-02  8:23 ` [pve-devel] [PATCH v4 qemu-server 1/4] disk reassign: add API endpoint Aaron Lauterer
2020-11-20 16:17   ` Fabian Grünbichler
2020-10-02  8:23 ` [pve-devel] [PATCH v4 qemu-server 2/4] cli: disk reassign: add reassign_disk to qm command Aaron Lauterer
2020-10-02  8:23 ` [pve-devel] [PATCH v4 storage 3/4] add disk reassign feature Aaron Lauterer
2020-11-20 16:17   ` Fabian Grünbichler
2020-10-02  8:23 ` [pve-devel] [PATCH v4 manager 4/4] ui: tasks: add qmreassign task description Aaron Lauterer
2020-10-30 10:42 ` [pve-devel] [PATCH v4 serries 0/4] disk reassign: add new feature Aaron Lauterer
2020-11-19 10:54   ` Dominic Jäger [this message]

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=20201119105420.GA66443@mala.proxmox.com \
    --to=d.jaeger@proxmox.com \
    --cc=pve-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