From: "proxmox" <proxmox@giftfish.de>
To: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu-server] api: cloud-init support for mtu and userdata
Date: Wed, 9 Sep 2020 09:06:13 +0000 [thread overview]
Message-ID: <kcRK.AAAAAAJZh+74Ak+ZgfTuugd5TBgBAAAABQAAAAHwUP11VVtHn0Mg+dCM8PoAAAAA.gPBYd4iG1gE=@mx.giftfish.de> (raw)
In-Reply-To: <164332898.407195.1599464008788.JavaMail.zimbra@odiso.com>
But this does not change the MTU inside the VM right?
-----Ursprüngliche Nachricht-----
Von: Alexandre DERUMIER <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 to add "mtu=xxx" option to netX:.....
It's not yet available in gui, but you should be able to do it with "qm set <vmid> --net0 ...,mtu=xxxx"
----- Mail original -----
De: "proxmox" <proxmox@giftfish.de>
À: "Proxmox VE development discussion" <pve-devel@lists.proxmox.com>
Envoyé: Vendredi 4 Septembre 2020 17:21:24
Objet: Re: [pve-devel] [PATCH qemu-server] api: cloud-init support for mtu and userdata
Hello
I didn't know this patch mail got approved, so sorry for the (very) late response.
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 the target machine for cloud-init userdata.
One possible use case was to spin up a kubernetes cluster on proxmox only via API.
I wanted to have something similar to the hetzner cloud API where the full userdata can be submitted for VM provisioning:
https://docs.hetzner.cloud/#servers-create-a-server
So going further here you want me to submit the MTU patches separately?
Should I integrate userdata into the cicustom field? I thought this would make things more complex in favor of parsing out the base64 stuff. So I would still go with an extra field.
Thoughts?
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
next prev parent reply other threads:[~2020-09-09 9:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-09-04 15:21 proxmox
2020-09-07 7:33 ` Alexandre DERUMIER
2020-09-09 9:06 ` proxmox [this message]
2020-09-09 13:02 ` Alexandre DERUMIER
2020-09-09 13:46 ` Alexandre DERUMIER
2020-09-09 14:05 ` Mira Limbeck
-- strict thread matches above, loose matches on Subject: below --
2020-07-13 15:06 Julien Escario
2020-07-02 16:08 [pve-devel] Extend cloud-init API with MTU " Marius Schellenberger
2020-07-02 16:08 ` [pve-devel] [PATCH qemu-server] api: cloud-init support for mtu " Marius Schellenberger
2020-07-13 12:51 ` Mira Limbeck
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='kcRK.AAAAAAJZh+74Ak+ZgfTuugd5TBgBAAAABQAAAAHwUP11VVtHn0Mg+dCM8PoAAAAA.gPBYd4iG1gE=@mx.giftfish.de' \
--to=proxmox@giftfish.de \
--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