From: "Fabian Grünbichler" <f.gruenbichler@proxmox.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: Mon, 24 Apr 2023 11:00:30 +0200 [thread overview]
Message-ID: <1682326436.dqh5ge6k9n.astroid@yuna.none> (raw)
In-Reply-To: <92fb220fccfa73e86e68369f63f09b5cd621679e.camel@groupe-cyllene.com>
On April 24, 2023 10:01 am, DERUMIER, Alexandre wrote:
> I think it could be done with some kind of new naming for this kind of
> disk,
>
> like "template-....." in the storage
>
> to match current lxc behaviour.
>
>
> I don't think we need to vm template itself inside this, only the disk.
>
> then use could create a vm like
>
> qm create <vmid> --iscsi0:template-.....
we basically already have this, it's just not yet on the GUI ;)
$ qm create/set 123 --scsi0 TARGET_STORAGE:0,import-from=SOURCE_STORAGE:VOLUME,other_option=value
will import an existing volume (or, if highly privileged, arbitrary
image/block device) to a newly allocated volume on TARGET_STORAGE.
also mentioned in the docs for cloud-init:
https://pve.proxmox.com/pve-docs/chapter-qm.html#_preparing_cloud_init_templates
we haven't fully hashed out yet how to integrate it into the GUI, but
it's already available on the API and CLI.
one part that might still be worth of discussion is whether to add a new
dir or naming scheme on storages for VM template files like downloaded
cloud(-init) images, and then on the GUI only offer up those and volumes
of VM templates as sources (at least by default), instead of *all*
images accessible to the user.
next prev parent reply other threads:[~2023-04-24 9:01 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
2023-04-24 8:01 ` DERUMIER, Alexandre
2023-04-24 9:00 ` Fabian Grünbichler [this message]
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=1682326436.dqh5ge6k9n.astroid@yuna.none \
--to=f.gruenbichler@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