From: Fiona Ebner <f.ebner@proxmox.com>
To: pve-devel@lists.proxmox.com
Subject: Re: [pve-devel] [PATCH-SERIES guest-common/container/qemu-server/ha-manager] make HA manager not depend on internal configuration details
Date: Tue, 6 Jun 2023 08:42:51 +0200 [thread overview]
Message-ID: <1a4178e6-109d-fd5e-776d-8f8f0a98478a@proxmox.com> (raw)
In-Reply-To: <20230228105410.51078-1-f.ebner@proxmox.com>
Am 28.02.23 um 11:54 schrieb Fiona Ebner:
> by introducing a get_derived_property() method for the configuration
> plugins. The derived properties are calculated by the plugins and will
> stay the same regardless of changes to the configuration structure.
> For example, this will allow turning QemuConfig's 'memory' into a
> property string (still requires a versioned Breaks for older HA
> manager).
>
> Dependency bumps ha-manager -> container,qemu-server are needed.
>
Should this be applied together with the versioned Breaks? That Breaks
is needed in preparation for Alexandre's memory hotplug rework
series[0]. Now would be a good opportunity for the versioned Breaks.
[0]: https://lists.proxmox.com/pipermail/pve-devel/2023-February/055920.html
prev parent reply other threads:[~2023-06-06 6:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-28 10:54 Fiona Ebner
2023-02-28 10:54 ` [pve-devel] [PATCH guest-common 1/1] abstract config: add method to calculate derived properties from a config Fiona Ebner
2023-06-07 17:40 ` [pve-devel] applied: " Thomas Lamprecht
2023-02-28 10:54 ` [pve-devel] [PATCH container 1/1] config: implement " Fiona Ebner
2023-06-09 5:50 ` [pve-devel] applied: " Thomas Lamprecht
2023-02-28 10:54 ` [pve-devel] [PATCH qemu-server " Fiona Ebner
2023-06-08 15:59 ` [pve-devel] applied: " Thomas Lamprecht
2023-02-28 10:54 ` [pve-devel] [PATCH ha-manager 1/1] resources: pve: avoid relying on internal configuration details Fiona Ebner
2023-06-06 6:42 ` Fiona Ebner [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=1a4178e6-109d-fd5e-776d-8f8f0a98478a@proxmox.com \
--to=f.ebner@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.