On Tue, 2023-02-07 at 07:57 +0100, Ulrich Windl wrote: > > > > Ken Gaillot <kgail...@redhat.com> schrieb am 06.02.2023 um > > > > 16:29 in Nachricht > <1fc864736b788762d00fbc0b78da1b34fc1137d3.ca...@redhat.com>: > > Hi all, > > > > Node attributes will receive several enhacements in the Pacemaker > > 2.1.6 > > release, expected in late May. They are available now in the main > > branch. > > > > A longstanding request to support transient utilization attributes > > has > > been implemented. Utilization attributes are used to assign > > resources > > to nodes based on local metrics such as CPU cores, RAM size, etc. > > Previously, these metrics could only be specified as permanent node > > attributes. As of 2.1.6, they can be set as transient node > > attributes > > as well (which last only until the cluster is restarted on the > > node). > > Can you explain the advantages of that change?
The original use case was someone who had tooling/orchestration that would replace the entire configuration section, and utilization attribute values dynamically detected and set by a resource agent. If the agent sets permanent attributes, they get overwritten by the next orchestration push. It also allows utilization attributes that are determined dynamically and shouldn't reuse the previous value from before a reboot. Perhaps the user wants to disallow a newly rebooted node from running resources (zero capacity) until an agent detects the environment. -- Ken Gaillot <kgail...@redhat.com> _______________________________________________ Manage your subscription: https://lists.clusterlabs.org/mailman/listinfo/users ClusterLabs home: https://www.clusterlabs.org/
