Page MenuHomeClusterLabs Projects

Default to sending clone notifications when agent supports it
Open, WishlistPublic

Assigned To
Authored By
Jan 24 2024, 5:27 PM
  • Restricted Project
  • Restricted Project
  • Restricted Project
Referenced Files


Currently users must specify the notify clone meta-attribute to true to get clone notifications. It's unlikely anyone disables notifications intentionally (which would be worth some investigation), so we should probably default to sending notifications whenever a resource is cloned and its resource agent supports notify.

We could change the meta-attribute default to true (and potentially deprecate it), or we could drop the meta-attribute and rely on the notify action's enabled meta-attribute to decide whether to send notifications (potentially with an XSL transform to preserve the existing configuration's behavior).

This would change behavior of existing configurations, so it should be done at a major version bump.


The scheduler doesn't know resource agent capabilities, nor is there a good way to pass them to it, so the likely implementation would be for the scheduler to always schedule notify actions for clones, and have the controller treat them as no-ops if the agent doesn't support them.

This would make transition graphs unnecessarily larger when the agent doesn't support notify, so we would have to check what difference it makes in a large cluster with multiple clones.

Event Timeline

kgaillot triaged this task as Wishlist priority.Jan 24 2024, 5:27 PM
kgaillot created this task.
kgaillot created this object with edit policy "Restricted Project (Project)".
kgaillot renamed this task from Default notify clone meta-attribute to true when agent supports it to Default to sending clone notifications when agent supports it.Jan 24 2024, 5:37 PM
kgaillot updated the task description. (Show Details)
kgaillot moved this task from Restricted Project Column to Restricted Project Column on the Restricted Project board.Jan 24 2024, 5:47 PM