[pve-devel] [PATCH v2 cluster/guest-common/manager/ha-manager/proxmox{, -perl-rs} 00/42] fix #4156: introduce new notification module

Lukas Wagner l.wagner at proxmox.com
Fri May 26 10:31:07 CEST 2023

On 5/24/23 15:56, Lukas Wagner wrote:
>    - Channels:
>      Logically, channel can be thought of as a 'group of endpoints'. Each
>      endpoint can be included in one or more channels. If one is using the
>      notification API to send a notification, a channel has to be specified.
>      The notification will then be forwarded to all endpoints included in that
>      channel.
>      Logically they decouple endpoints from notification senders - for instance,
>      a backup job configuration would need to contain references to potentially
>      multiple  endpoints, or, a alternatively, always notify via *all* endpoints.
>      The latter would potentially shift more configuration effort to filters, for
>      instance if some backup jobs should only notify via *some* endpoints.
>      I think the group/channel-based approach provides a relatively nice middle
>      ground.
Having worked on UI stuff yesterday, lifting some of my "Betriebsblindheit" after working on this
for a long time, I think I want to s/channel/(notification) group/g - I think
this should make it a bit clearer to the user what this actually means.

Also I want to somehow unify the concepts of groups and endpoints from a users perspective.
Everywhere where a user can choose a group (formerly channel) in the UI (e.g. backup jobs),
the user would also be able to select a single endpoint.
Benefit: If there is only one endpoint (e.g. send email to root), the user does not
have to create a group first.

The changes needed for these two things should be pretty minor, but ultimately
warrant a v3.

I'm out of office for the next two weeks, so I'll probably have to send the v3
along with any other requested changes after that.

- Lukas

More information about the pve-devel mailing list