From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from firstgate.proxmox.com (firstgate.proxmox.com [212.224.123.68]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id D3C6C985C5 for ; Mon, 24 Apr 2023 11:01:09 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id B4FC72EDCA for ; Mon, 24 Apr 2023 11:00:39 +0200 (CEST) Received: from proxmox-new.maurer-it.com (proxmox-new.maurer-it.com [94.136.29.106]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (2048 bits) server-digest SHA256) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS for ; Mon, 24 Apr 2023 11:00:37 +0200 (CEST) Received: from proxmox-new.maurer-it.com (localhost.localdomain [127.0.0.1]) by proxmox-new.maurer-it.com (Proxmox) with ESMTP id 453B045141 for ; Mon, 24 Apr 2023 11:00:37 +0200 (CEST) Date: Mon, 24 Apr 2023 11:00:30 +0200 From: Fabian =?iso-8859-1?q?Gr=FCnbichler?= To: Proxmox VE development discussion References: <2ADAC3DD-43D1-49AE-8EE6-5D3D22C5BD5B@wolfspyre.com> <92fb220fccfa73e86e68369f63f09b5cd621679e.camel@groupe-cyllene.com> In-Reply-To: <92fb220fccfa73e86e68369f63f09b5cd621679e.camel@groupe-cyllene.com> MIME-Version: 1.0 User-Agent: astroid/0.16.0 (https://github.com/astroidmail/astroid) Message-Id: <1682326436.dqh5ge6k9n.astroid@yuna.none> Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-SPAM-LEVEL: Spam detection results: 0 AWL 0.076 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DMARC_MISSING 0.1 Missing DMARC policy KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record T_SCC_BODY_TEXT_LINE -0.01 - Subject: Re: [pve-devel] Feature idea: import cloud images as disks, or at VM creation X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 24 Apr 2023 09:01:09 -0000 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, >=20 > like "template-....." in the storage >=20 > to match current lxc behaviour. >=20 >=20 > I don't think we need to vm template itself inside this, only the disk. >=20 > then use could create a vm like >=20 > qm create --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=3DSOURCE_STORAGE:V= OLUME,other_option=3Dvalue 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_temp= lates we haven't fully hashed out yet how to integrate it into the GUI, but it's already available on the API and CLI.=20 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.