From: Mira Limbeck <m.limbeck@proxmox.com>
To: 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 16:05:33 +0200 [thread overview]
Message-ID: <52868585-8944-188c-3548-97c91d138ab3@proxmox.com> (raw)
In-Reply-To: <kcRK.AAAAAAJZh+74Ak+ZgfTuugd5TBgBAAAABQAAAC9qJF5oxmZOmbnepn3tg6UAAAAA.ADLiDM+C1gE=@mx.giftfish.de>
Hi,
On 9/4/20 5:21 PM, proxmox wrote:
> 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.
There is currently a bug report open for this:
https://bugzilla.proxmox.com/show_bug.cgi?id=2208
This together with backup and migration of snippets could be useful.
>
>
>
> 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?
The MTU patches separately would be great.
>
>
>
> 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.
After some discussions we think that putting the userdata in the config
file is not the right approach. As the cluster filesystem is limited to
32M and a single VM config file is limited to 512K you can easily run
into the limit with a small number of VMs. We would most likely have to
limit the userdata per config to a very small amount (1K?). But with
those limits it is difficult to get everything in.
>
> Thoughts?
> _______________________________________________
> 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 14:05 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
2020-09-09 13:02 ` Alexandre DERUMIER
2020-09-09 13:46 ` Alexandre DERUMIER
2020-09-09 14:05 ` Mira Limbeck [this message]
-- 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=52868585-8944-188c-3548-97c91d138ab3@proxmox.com \
--to=m.limbeck@proxmox.com \
--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