[pve-devel] [PATCH qemu-server] api: cloud-init support for mtu and userdata

[Alexandre DERUMIER]

it has been added to kernel in 2016

https://git.kernel.org/pub/scm/linux/kernel/git/stable/linux.git/commit/?h=v5.8.7&id=14de9d114a82a564b94388c95af79a701dc93134

----- Mail original -----
De: "aderumier" <aderumier at odiso.com>
À: "Proxmox VE development discussion" <pve-devel at lists.proxmox.com>
Envoyé: 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? 

yes, it change the mtu inside the vm! 

(at least on recent kernel, don't remember when this had been added) 

----- Mail original ----- 
De: "proxmox" <proxmox at giftfish.de> 
À: "Proxmox VE development discussion" <pve-devel at lists.proxmox.com> 
Envoyé: Mercredi 9 Septembre 2020 11:06:13 
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? 



-----Ursprüngliche Nachricht----- 
Von: Alexandre DERUMIER <aderumier at odiso.com> 
Gesendet: Montag 7 September 2020 09:34 
An: Proxmox VE development discussion <pve-devel at 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 at giftfish.de> 
À: "Proxmox VE development discussion" <pve-devel at 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 at lists.proxmox.com 
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 


_______________________________________________ 
pve-devel mailing list 
pve-devel at lists.proxmox.com 
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 
_______________________________________________ 
pve-devel mailing list 
pve-devel at lists.proxmox.com 
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel 


_______________________________________________ 
pve-devel mailing list 
pve-devel at lists.proxmox.com 
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel