From: Thomas Lamprecht <t.lamprecht@proxmox.com>
To: Fiona Ebner <f.ebner@proxmox.com>,
Maximiliano Sandoval <m.sandoval@proxmox.com>
Cc: Proxmox VE development discussion <pve-devel@lists.proxmox.com>
Subject: Re: [pve-devel] [PATCH qemu] api: qemu: create: default cpu to x86-64-v2-AES
Date: Wed, 23 Oct 2024 13:06:37 +0200 [thread overview]
Message-ID: <a3715ed8-eebd-447e-be02-74826b6bf4d9@proxmox.com> (raw)
In-Reply-To: <ba51d22d-6d7f-46f0-999d-be3d7b2f6566@proxmox.com>
Am 23/10/2024 um 11:56 schrieb Fiona Ebner:
> Maybe we could have (datacenter-wide?) default profiles (one for
> containers, one for VMs) whose values are used for new guest creation?
> Users could modify them if desired and they could also be used to
> pre-fill values in the UI. Could then be shipped for PVE 9 with sensible
> values.
This sounds (at least partially) like the config profile work I wished for
and Dominik worked on a while ago:
https://lore.proxmox.com/pve-devel/20231117114548.3208470-1-d.csapak@proxmox.com/
And yes, with that one could also ship a few built-in profiles that could
be passed on VM/CT creation.
I did not think it through completely, but default profiles could be also
seen as variation of this.
And FWIW, currently the above linked profile approach resolves values and
solves them explicitly, and is not just a reference where changing the
profile will alter the effective config of guests that got created before
that profile change happened. Which might be something that can be desired,
but IMO such a behavior would need to be opt-in.
_______________________________________________
pve-devel mailing list
pve-devel@lists.proxmox.com
https://lists.proxmox.com/cgi-bin/mailman/listinfo/pve-devel
prev parent reply other threads:[~2024-10-23 11:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-01 14:08 Maximiliano Sandoval
2024-10-02 7:50 ` Shannon Sterz
2024-10-22 11:23 ` Fiona Ebner
2024-10-22 11:35 ` Thomas Lamprecht
2024-10-22 12:15 ` Maximiliano Sandoval
2024-10-22 13:35 ` Thomas Lamprecht
2024-10-23 9:56 ` Fiona Ebner
2024-10-23 11:06 ` Thomas Lamprecht [this message]
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=a3715ed8-eebd-447e-be02-74826b6bf4d9@proxmox.com \
--to=t.lamprecht@proxmox.com \
--cc=f.ebner@proxmox.com \
--cc=m.sandoval@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