From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>,
Gilles Pietri <contact+dev@gilouweb.com>,
pve-devel@pve.proxmox.com
Subject: Re: [pve-devel] Feature idea: import cloud images as disks, or at VM creation
Date: Tue, 9 Nov 2021 08:29:17 +0100 [thread overview]
Message-ID: <3a0329d8-bea6-ffab-5c03-e4d2e0675b23@proxmox.com> (raw)
In-Reply-To: <87d419d1-f178-8c9b-a5ee-1d03fb0ae7d7@gilouweb.com>
Hi,
On 09.11.21 03:03, Gilles Pietri wrote:
> There's something I'd like to add to the UI, but I'd like some input from others, or at least know how useful it may sound.
>
> I'd like to be able to import cloud image from distributions.
>
> My idea would be to add a qemu template type (could be raw to start, but really anything that can be imported using qemu-img could do), and use those when needed.
>
> It could be through an to import the disk on an existing VM, or at creation: instead of choosing a CD-Rom, we'd chose a template to import as the main disk, and the size chosen later on would be used to resize it.
>
> What do you think? Is this dumb? Has anyone worked on such an idea?
>
> I'm willing to start exploring adding a template type named Qemu template or so, then working on using that to import a disk, then improve the creation ui..
FYI, there was already some effort in adding an OVF importer to the API/GUI:
https://lists.proxmox.com/pipermail/pve-devel/2021-June/048564.html
https://lists.proxmox.com/pipermail/pve-devel/2021-June/048563.html
While it stalled a bit but we still plan to pick that up again in the near
future.
cheers,
Thomas
next prev parent reply other threads:[~2021-11-09 7:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 2:03 Gilles Pietri
2021-11-09 7:29 ` Thomas Lamprecht [this message]
[not found] <mailman.16.1682241508.359.pve-devel@lists.proxmox.com>
2023-04-23 22:39 ` Wolf Noble
2023-04-24 8:01 ` DERUMIER, Alexandre
2023-04-24 9:00 ` Fabian Grünbichler
2023-04-24 18:05 ` Wolf Noble
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=3a0329d8-bea6-ffab-5c03-e4d2e0675b23@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=contact+dev@gilouweb.com \
--cc=pve-devel@lists.proxmox.com \
--cc=pve-devel@pve.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.