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 1DB1698555 for ; Mon, 24 Apr 2023 00:40:11 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 072B62AAAA for ; Mon, 24 Apr 2023 00:39:41 +0200 (CEST) Received: from mail-oo1-xc31.google.com (mail-oo1-xc31.google.com [IPv6:2607:f8b0:4864:20::c31]) (using TLSv1.3 with cipher TLS_AES_128_GCM_SHA256 (128/128 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 00:39:40 +0200 (CEST) Received: by mail-oo1-xc31.google.com with SMTP id 006d021491bc7-5475e0147c9so810023eaf.1 for ; Sun, 23 Apr 2023 15:39:40 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=wolfspyre-com.20221208.gappssmtp.com; s=20221208; t=1682289572; x=1684881572; h=date:to:in-reply-to:references:message-id:subject:mime-version:from :content-transfer-encoding:from:to:cc:subject:date:message-id :reply-to; bh=ZpIuyCsNtyWEnoIbBIEGWGaxs3KGi059A9zlRz7Ag2Y=; b=YRg4nVEKcoCtgwZG2y1q2QfCfSpmS6xN/r+d2WXzT7+GrrSzmp/H+1XPsoqXwwzy7S s4BXd0NC3ee70EutU93th3zwlU94++vIiwigFE0TyhEGWG7DYLRqZUtayabkcutHnLR7 sijOr4tUqslaKPWI0CCtYw1jUvLRF/sOFvx3CJdJY1Cs+fopczfBQBZUw9YtEUda6Brf dhKbgP4wEiDmYkyMtDtb6xv/C0iDJNYkADThE6Ln/hi9shqdaIek9/jGFpMZjl8LvdXP DwhffY3Hje0EzGJgePQZXuoH458bIVtAszco+zh4cUBnQdA4XCmZh+GJoY0llAsMt37/ 9ozA== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20221208; t=1682289572; x=1684881572; h=date:to:in-reply-to:references:message-id:subject:mime-version:from :content-transfer-encoding:x-gm-message-state:from:to:cc:subject :date:message-id:reply-to; bh=ZpIuyCsNtyWEnoIbBIEGWGaxs3KGi059A9zlRz7Ag2Y=; b=jJe1fE2U4gLXo1mLLUIxGqvTY5SK6gVH3yVK/r3Sd7KJNWPKtTIfxGkHuFC3DrERI3 rtn9u5WF1uTK27ogOGjZmLgbzZ4KWvAQX5G2Lk0iDoOb3PP01YPTRYemdAiWYramLjgD wZui9USPyVAHF1ZNwKMTFEcWXU8/ZHJ0U0NbPsAl1DJRWHkX9Kc964S77WlhsGKJNVPu cxVDpQQwaoKn0650msWiji8RF612GAxATwCtAVHvW/hPEC0c4fV4H4aXavZpH/qGhaLJ heo2Im8PdpOaNucdFs7WOQpAFms7o+NypSD5Lid5/fHilVCAIgDBHz4/pFvPr5VchAzl n1ww== X-Gm-Message-State: AAQBX9f4iVjMs8SOrLMP+z0H4jxhXEK8M+MeaeRR/IlystSX5oZ3fTWO jSihBtxoyAoAw+V3AbQ7HzEuTQ== X-Google-Smtp-Source: AKy350a06OS7ydv1b2WMztq81t5mxz6BFcK7JgLqk6Cb2G3VDpcr1+X9S33fkro4N7ZPu7CB8fTTFw== X-Received: by 2002:a05:6820:410:b0:547:7a04:fca with SMTP id o16-20020a056820041000b005477a040fcamr1968249oou.3.1682289571483; Sun, 23 Apr 2023 15:39:31 -0700 (PDT) Received: from smtpclient.apple (who.wolfspaw.com. [108.221.46.19]) by smtp.gmail.com with ESMTPSA id n14-20020a4a954e000000b0053b547ebee7sm4253116ooi.1.2023.04.23.15.39.30 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 23 Apr 2023 15:39:31 -0700 (PDT) From: Wolf Noble Mime-Version: 1.0 (1.0) Message-Id: <2ADAC3DD-43D1-49AE-8EE6-5D3D22C5BD5B@wolfspyre.com> References: In-Reply-To: To: Proxmox VE development discussion Date: Sun, 23 Apr 2023 17:39:20 -0500 X-Mailer: iPhone Mail (20F5039e) X-SPAM-LEVEL: Spam detection results: 0 AWL -0.045 Adjusted score from AWL reputation of From: address BAYES_00 -1.9 Bayes spam probability is 0 to 1% DKIM_SIGNED 0.1 Message has a DKIM or DK signature, not necessarily valid DKIM_VALID -0.1 Message has at least one valid DKIM or DK signature DMARC_MISSING 0.1 Missing DMARC policy HTML_FONT_LOW_CONTRAST 0.001 HTML font color similar or identical to background HTML_MESSAGE 0.001 HTML included in message MIME_QP_LONG_LINE 0.001 Quoted-printable line longer than 76 chars RCVD_IN_DNSWL_NONE -0.0001 Sender listed at https://www.dnswl.org/, no trust 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 - URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [proxmox.com, ubuntu.com] Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Content-Filtered-By: Mailman/MimeDel 2.1.29 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: Sun, 23 Apr 2023 22:40:11 -0000 I concur that this (or something like it) would definitely make it easier to= create new VMs=E2=80=A6. what would the CLI / API implementation look like for this?=20 would new canned privilege levels need to exist? > On Apr 23, 2023, at 04:18, Gilou via pve-devel wrote: > Le 09/11/2021 =C3=A0 03:03, Gilles Pietri a =C3=A9crit : > Hi, > There's something I'd like to add to the UI, but I'd like some input from o= thers, 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 r= eally anything that can be imported using qemu-img could do), and use those w= hen needed. > It could be through an to import the disk on an existing VM, or at creatio= n: 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 o= r 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, le= t'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 b= ootdisk, 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-k= nown" 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, allowi= ng to provide a great experience, starting from "empty" to a running VM, all= owing 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 [=3D 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 =3D]=