From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <proxmox@giftfish.de> 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)) (No client certificate requested) by lists.proxmox.com (Postfix) with ESMTPS id 3F0DB60531 for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 11:06:53 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id 24E8C10063 for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 11:06:23 +0200 (CEST) Received: from mx.giftfish.de (mx.giftfish.de [176.9.239.230]) (using TLSv1.2 with cipher ECDHE-RSA-CHACHA20-POLY1305 (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id F207C1004E for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 11:06:21 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=giftfish.de; s=dkim; t=1599642373; h=from:from:sender:sender:reply-to:subject:subject:date:date: message-id:message-id:to:to:cc:mime-version:mime-version: content-type:content-type:in-reply-to:in-reply-to: references:references; bh=qIehS12UN2/RgT4CQeH41gs4qC+NVC0Ck72K0/Q+21I=; b=VxW3WLNUh5qgm+VTPe7zQ1a5QNV+hr0VI1YwJs+h6HCjnDJIZdyN8pDW82E+U8H5GiL1AO 26iJE2z20KiYuM4Ld9I4q50JT/9g/zB6qMmDYCRt0oXrPrLqz0qgAjAGXHVw94/1lMeipQ k7Dss8FSBS2sTUdtwYWp7oxou2QcXyX6dYEqW2J3gRO98UN37UjN1gN/5lyRZXwDFqCUmp qTGEMwVAZXRpRkcPkZ9UldZJk6GBziSI+dXX2Ius6UlxxzYEZqv/XDRC5MKZViWDPg6f6x XhsRm2MK+V/z7P/XslgTvBgkrzUV6IoghGod6q3CpJRs0M4ESCdWK09/ntRvrw== Received: by mx.giftfish.de (OpenSMTPD) with ESMTP id a2ad7773 for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 11:06:13 +0200 (CEST) Received: by mx.giftfish.de (kopano-spooler) with MAPI; Wed, 9 Sep 2020 11:06:13 +0200 From: "proxmox" <proxmox@giftfish.de> To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com> Date: Wed, 9 Sep 2020 09:06:13 +0000 Mime-Version: 1.0 In-Reply-To: <164332898.407195.1599464008788.JavaMail.zimbra@odiso.com> References: <kcRK.AAAAAAJZh+74Ak+ZgfTuugd5TBgBAAAABQAAAC9qJF5oxmZOmbnepn3tg6UAAAAA.ADLiDM+C1gE=@mx.giftfish.de> <164332898.407195.1599464008788.JavaMail.zimbra@odiso.com> X-Priority: 3 (Normal) Sender: "Marius Schellenberger" <marius@giftfish.de> Message-Id: <kcRK.AAAAAAJZh+74Ak+ZgfTuugd5TBgBAAAABQAAAAHwUP11VVtHn0Mg+dCM8PoAAAAA.gPBYd4iG1gE=@mx.giftfish.de> X-SPAM-LEVEL: Spam detection results: 0 AWL 0.104 Adjusted score from AWL reputation of From: address 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 DKIM_VALID_AU -0.1 Message has a valid DKIM or DK signature from author's domain DKIM_VALID_EF -0.1 Message has a valid DKIM or DK signature from envelope-from domain HTML_MESSAGE 0.001 HTML included in message SPF_HELO_NONE 0.001 SPF: HELO does not publish an SPF Record SPF_PASS -0.001 SPF: sender matches SPF record URIBL_BLOCKED 0.001 ADMINISTRATOR NOTICE: The query to URIBL was blocked. See http://wiki.apache.org/spamassassin/DnsBlocklists#dnsbl-block for more information. [giftfish.de, hetzner.cloud, proxmox.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] [PATCH qemu-server] api: cloud-init support for mtu and userdata X-BeenThere: pve-devel@lists.proxmox.com X-Mailman-Version: 2.1.29 Precedence: list List-Id: Proxmox VE development discussion <pve-devel.lists.proxmox.com> List-Unsubscribe: <https://lists.proxmox.com/cgi-bin/mailman/options/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=unsubscribe> List-Archive: <http://lists.proxmox.com/pipermail/pve-devel/> List-Post: <mailto:pve-devel@lists.proxmox.com> List-Help: <mailto:pve-devel-request@lists.proxmox.com?subject=help> List-Subscribe: <https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel>, <mailto:pve-devel-request@lists.proxmox.com?subject=subscribe> X-List-Received-Date: Wed, 09 Sep 2020 09:06:53 -0000 But this does not change the MTU inside the VM right=3F -----Urspr=C3=BCngliche Nachricht----- Von: Alexandre DERUMIER=C2=A0<aderumier@odiso.com> Gesendet: Montag 7 September 2020 09:34 An: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Betreff: Re: [pve-devel] [PATCH qemu-server] api: cloud-init support for = mtu and userdata Hi, not related to cloudinit, but for virtio-net nic, it's already possible t= o add "mtu=3Dxxx" option to netX:..... It's not yet available in gui, but you should be able to do it with "qm s= et <vmid> --net0 ...,mtu=3Dxxxx" ----- Mail original ----- De: "proxmox" <proxmox@giftfish.de> =C3=80: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>= Envoy=C3=A9: Vendredi 4 Septembre 2020 17:21:24 Objet: Re: [pve-devel] [PATCH qemu-server] api: cloud-init support for mt= u and userdata Hello=20 I didn't know this patch mail got approved, so sorry for the (very) late = response.=20 My intention for not going with snippets was the fact that they could not= be created via the API and one would have to manually create a file on t= he target machine for cloud-init userdata.=20 One possible use case was to spin up a kubernetes cluster on proxmox only= via API.=20 I wanted to have something similar to the hetzner cloud API where the ful= l userdata can be submitted for VM provisioning:=20 https://docs.hetzner.cloud/#servers-create-a-server=20 So going further here you want me to submit the MTU patches separately=3F= =20 Should I integrate userdata into the cicustom field=3F I thought this wou= ld make things more complex in favor of parsing out the base64 stuff. So = I would still go with an extra field.=20 Thoughts=3F=20 _______________________________________________=20 pve-devel mailing list=20 pve-devel@lists.proxmox.com=20 https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel=20 _______________________________________________ pve-devel mailing list pve-devel@lists.proxmox.com https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel