public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Dominik Csapak <d.csapak@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
	Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH storage/manager v3] allow upload & import of qcow2 in the web UI
Date: Wed, 26 Mar 2025 11:47:25 +0100	[thread overview]
Message-ID: <8af44d26-f1ea-4272-b94a-d6540d02249f@proxmox.com> (raw)
In-Reply-To: <8c06736a-abaf-42d5-9c56-cca185d30aee@proxmox.com>

On 3/26/25 11:37, Fiona Ebner wrote:
> Am 25.03.25 um 16:14 schrieb Dominik Csapak:
>> most of the building blocks are already there:
>> * we can have qcow2 files in an import storage
>> * we can import qcow2 files via the api from such a storage
>>
>> this series fills in the missing bits & pieces:
>> * allow uploading qcow2 files into an import storage via the webgui
>> * adding the possibility to select such a file when creating a vm/disk
>>
>> We could maybe also allow this for raw/vmdk if we want to, but IMHO
>> we can start out with qcow2 and add the others as necssary.
>>
>> (if wanted, I can of course also add the others in a next version or as
>> a follow up)
> 
> 
> Yes, please! It would be nice to have all three at the same time. Or is
> there any specific reason why you limit it to qcow2? Otherwise, users
> will just ask why support for these is missing right away.

No specific reason, it was just easier/quicker to implement one first. When we also allow raw files,
should we also allow other extensions than '.raw'? not sure if there is one that
is often used (since I think '.raw' is more a PVE thing)


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


  reply	other threads:[~2025-03-26 10:48 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-25 15:14 Dominik Csapak
2025-03-25 15:14 ` [pve-devel] [PATCH storage v3 1/1] import: allow upload of qcow2 files into import storage Dominik Csapak
2025-03-25 15:14 ` [pve-devel] [PATCH manager v3 1/3] ui: storage content: allow upload of qcow2 for import type Dominik Csapak
2025-03-25 15:14 ` [pve-devel] [PATCH manager v3 2/3] ui: form: file selector: allow optional filter Dominik Csapak
2025-03-25 15:14 ` [pve-devel] [PATCH manager v3 3/3] ui: qemu hd edit: allow importing a disk from the import storage Dominik Csapak
2025-03-26 10:09 ` [pve-devel] [PATCH storage/manager v3] allow upload & import of qcow2 in the web UI Filip Schauer
2025-03-26 10:37 ` Fiona Ebner
2025-03-26 10:47   ` Dominik Csapak [this message]
2025-03-26 11:41     ` Fiona Ebner
2025-03-26 11:47       ` Dominik Csapak
2025-03-26 12:05         ` Fiona Ebner
2025-03-26 12:25           ` Dominik Csapak
2025-03-26 12:28             ` Fiona Ebner
2025-03-26 11:57       ` Dominik Csapak
2025-03-26 12:06         ` Fiona Ebner
2025-03-26 15:30         ` Thomas Lamprecht
2025-03-26 10:47   ` Thomas Lamprecht
2025-03-26 15:27 ` Dominik Csapak

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=8af44d26-f1ea-4272-b94a-d6540d02249f@proxmox.com \
    --to=d.csapak@proxmox.com \
    --cc=f.ebner@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