public inbox for pve-devel@lists.proxmox.com
 help / color / mirror / Atom feed
From: Wolf Noble <wolf@wolfspyre.com>
To: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] Feature idea: import cloud images as disks, or at VM creation
Date: Sun, 23 Apr 2023 17:39:20 -0500	[thread overview]
Message-ID: <2ADAC3DD-43D1-49AE-8EE6-5D3D22C5BD5B@wolfspyre.com> (raw)
In-Reply-To: <mailman.16.1682241508.359.pve-devel@lists.proxmox.com>


I concur that this (or something like it) would definitely make it easier to create new VMs….

what would the CLI / API implementation look like for this? 
would new canned privilege levels need to exist?




> On Apr 23, 2023, at 04:18, Gilou via pve-devel <pve-devel@lists.proxmox.com> wrote:

> Le 09/11/2021 à 03:03, Gilles Pietri a écrit :
> Hi,
> 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..

Hi,

This is an "old" email from 2021, but the need has risen again, so, well, let's talk about it, if anybody cares!

What to do?
- implement a QEMU disk template (next to ISO Images and Container templates?)
- make it so you can importdisk easily that to a VM? Attach it, set it as a bootdisk, resize it?
- add the option to do all that in the creation flow for a VM?
- offer to add a cloud-init disk directly?
- then maybe offer to set username/password/ssh key, or IP settings directly in the creation flow, as cloud-init data

We could even go as far as add in the template content handler a few "well-known" base images such as
https://cloud-images.ubuntu.com/
https://cloud.debian.org/images/cloud/

All that would make self service crazily improved when using Proxmox, allowing to provide a great experience, starting from "empty" to a running VM, allowing us to "duplicate" the cool CT experience in VMs!

Plus, the base is already there ;)
Or am I the only one seeing any interest int that?

Regards,

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


[= The contents of this message have been written, read, processed, erased, sorted, sniffed, compressed, rewritten, misspelled, overcompensated, lost, found, and most importantly delivered entirely with recycled electrons =]

       reply	other threads:[~2023-04-23 22:40 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <mailman.16.1682241508.359.pve-devel@lists.proxmox.com>
2023-04-23 22:39 ` Wolf Noble [this message]
2023-04-24  8:01   ` DERUMIER, Alexandre
2023-04-24  9:00     ` Fabian Grünbichler
2023-04-24 18:05       ` Wolf Noble
2021-11-09  2:03 Gilles Pietri
2021-11-09  7:29 ` Thomas Lamprecht

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=2ADAC3DD-43D1-49AE-8EE6-5D3D22C5BD5B@wolfspyre.com \
    --to=wolf@wolfspyre.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