From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: <aderumier@odiso.com> 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 C5B8860689 for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 15:46:23 +0200 (CEST) Received: from firstgate.proxmox.com (localhost [127.0.0.1]) by firstgate.proxmox.com (Proxmox) with ESMTP id BA3EC126DC for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 15:46:23 +0200 (CEST) Received: from mailpro.odiso.net (mailpro.odiso.net [89.248.211.110]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by firstgate.proxmox.com (Proxmox) with ESMTPS id 2AB28126D2 for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 15:46:21 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id D2BB4197F3CF for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 15:46:20 +0200 (CEST) Received: from mailpro.odiso.net ([127.0.0.1]) by localhost (mailpro.odiso.net [127.0.0.1]) (amavisd-new, port 10032) with ESMTP id 3yHgoaQRxVJO for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 15:46:20 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by mailpro.odiso.net (Postfix) with ESMTP id B94D7197F3D1 for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 15:46:20 +0200 (CEST) X-Virus-Scanned: amavisd-new at mailpro.odiso.com Received: from mailpro.odiso.net ([127.0.0.1]) by localhost (mailpro.odiso.net [127.0.0.1]) (amavisd-new, port 10026) with ESMTP id Zsmcwwd4ECIp for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 15:46:20 +0200 (CEST) Received: from mailpro.odiso.net (mailpro.odiso.net [10.1.31.111]) by mailpro.odiso.net (Postfix) with ESMTP id A3A63197F3CF for <pve-devel@lists.proxmox.com>; Wed, 9 Sep 2020 15:46:20 +0200 (CEST) Date: Wed, 9 Sep 2020 15:46:20 +0200 (CEST) From: Alexandre DERUMIER <aderumier@odiso.com> To: Proxmox VE development discussion <pve-devel@lists.proxmox.com> Message-ID: <2005350344.484226.1599659180629.JavaMail.zimbra@odiso.com> In-Reply-To: <140120601.483203.1599656553686.JavaMail.zimbra@odiso.com> References: <kcRK.AAAAAAJZh+74Ak+ZgfTuugd5TBgBAAAABQAAAC9qJF5oxmZOmbnepn3tg6UAAAAA.ADLiDM+C1gE=@mx.giftfish.de> <164332898.407195.1599464008788.JavaMail.zimbra@odiso.com> <kcRK.AAAAAAJZh+74Ak+ZgfTuugd5TBgBAAAABQAAAAHwUP11VVtHn0Mg+dCM8PoAAAAA.gPBYd4iG1gE=@mx.giftfish.de> <140120601.483203.1599656553686.JavaMail.zimbra@odiso.com> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-Mailer: Zimbra 8.8.12_GA_3866 (ZimbraWebClient - GC83 (Linux)/8.8.12_GA_3844) Thread-Topic: cloud-init support for mtu and userdata Thread-Index: zwvsgHoPyDOrfPQdz3sg9DD4OjVG645A9vf2 X-SPAM-LEVEL: Spam detection results: 0 AWL -0.373 Adjusted score from AWL reputation of From: address KAM_ASCII_DIVIDERS 0.8 Spam that uses ascii formatting tricks KAM_DMARC_STATUS 0.01 Test Rule for DKIM or SPF Failure with Strict Alignment 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 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, hetzner.cloud] 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 13:46:23 -0000 it has been added to kernel in 2016 https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h= =3Dv5.8.7&id=3D14de9d114a82a564b94388c95af79a701dc93134 ----- Mail original ----- De: "aderumier" <aderumier@odiso.com> =C3=80: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com> Envoy=C3=A9: Mercredi 9 Septembre 2020 15:02:33 Objet: Re: [pve-devel] [PATCH qemu-server] api: cloud-init support for mtu = and userdata >>But this does not change the MTU inside the VM right?=20 yes, it change the mtu inside the vm!=20 (at least on recent kernel, don't remember when this had been added)=20 ----- Mail original -----=20 De: "proxmox" <proxmox@giftfish.de>=20 =C3=80: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>= =20 Envoy=C3=A9: Mercredi 9 Septembre 2020 11:06:13=20 Objet: Re: [pve-devel] [PATCH qemu-server] api: cloud-init support for mtu = and userdata=20 But this does not change the MTU inside the VM right?=20 -----Urspr=C3=BCngliche Nachricht-----=20 Von: Alexandre DERUMIER <aderumier@odiso.com>=20 Gesendet: Montag 7 September 2020 09:34=20 An: Proxmox VE development discussion <pve-devel@lists.proxmox.com>=20 Betreff: Re: [pve-devel] [PATCH qemu-server] api: cloud-init support for mt= u and userdata=20 Hi,=20 not related to cloudinit, but for virtio-net nic, it's already possible to = add "mtu=3Dxxx" option to netX:.....=20 It's not yet available in gui, but you should be able to do it with "qm set= <vmid> --net0 ...,mtu=3Dxxxx"=20 ----- Mail original -----=20 De: "proxmox" <proxmox@giftfish.de>=20 =C3=80: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>= =20 Envoy=C3=A9: Vendredi 4 Septembre 2020 17:21:24=20 Objet: Re: [pve-devel] [PATCH qemu-server] api: cloud-init support for mtu = and userdata=20 Hello=20 I didn't know this patch mail got approved, so sorry for the (very) late re= sponse.=20 My intention for not going with snippets was the fact that they could not b= e created via the API and one would have to manually create a file on the t= arget machine for cloud-init userdata.=20 One possible use case was to spin up a kubernetes cluster on proxmox only v= ia API.=20 I wanted to have something similar to the hetzner cloud API where the full = 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?=20 Should I integrate userdata into the cicustom field? I thought this would m= ake things more complex in favor of parsing out the base64 stuff. So I woul= d still go with an extra field.=20 Thoughts?=20 _______________________________________________=20 pve-devel mailing list=20 pve-devel@lists.proxmox.com=20 https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel=20 _______________________________________________=20 pve-devel mailing list=20 pve-devel@lists.proxmox.com=20 https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel=20 _______________________________________________=20 pve-devel mailing list=20 pve-devel@lists.proxmox.com=20 https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel=20 _______________________________________________=20 pve-devel mailing list=20 pve-devel@lists.proxmox.com=20 https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel=20