From: Bennet Gallein <me@bennetgallein.de>
To: Proxmox VE user list <pve-user@lists.proxmox.com>,
Dominik Csapak <d.csapak@proxmox.com>
Subject: Re: [PVE-User] Moving Disks via API
Date: Tue, 2 Nov 2021 09:02:50 +0100 (CET) [thread overview]
Message-ID: <1608874848.285220.1635840170613@ox.hosteurope.de> (raw)
In-Reply-To: <6f38c9ed-7f39-964e-db6c-c88da7561bb7@proxmox.com>
Hello Dominik,
even though i'm on the devel list I somehow missed that. But yes, that is exactly what I'm looking for! Thanks, I'll keep myself updated!
Best Regards,
Bennet
> Dominik Csapak <d.csapak@proxmox.com> hat am 02.11.2021 08:47 geschrieben:
>
>
> On 11/1/21 17:56, Bennet Gallein wrote:
> > Hello Michael,
> >
> > nothing is wrong with the API-viewer, I like it. There just is no API to move a disk from one VM to another and I was wondering if someone using PVE in production has found a way to automate this without modifying PVE source-code or running extra software on the PVE host.
> > Best Regards,
> > Freundliche Grüße aus Lüneburg,
> > Bennet Gallein
> > Bennet Gallein IT Solutions
>
> hi,
>
> there is currently a patchset on the devel list that does
> what you want (i think)
>
> https://lists.proxmox.com/pipermail/pve-devel/2021-October/050491.html
>
> it's not yet merged (and i think there will be a new version)
>
> kind regards
> Dominik
>
>
>
> _______________________________________________
> pve-user mailing list
> pve-user@lists.proxmox.com
> https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-user
next prev parent reply other threads:[~2021-11-02 8:02 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.139.1635785316.15957.pve-user@lists.proxmox.com>
2021-11-01 16:56 ` Bennet Gallein
2021-11-02 7:47 ` Dominik Csapak
2021-11-02 8:02 ` Bennet Gallein [this message]
2021-11-01 16:33 Bennet Gallein
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=1608874848.285220.1635840170613@ox.hosteurope.de \
--to=me@bennetgallein.de \
--cc=d.csapak@proxmox.com \
--cc=pve-user@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