Bug 729174 - notification system
Summary: notification system
Alias: None
Product: Fedora
Classification: Fedora
Component: freeipa
Version: rawhide
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
Assignee: Rob Crittenden
QA Contact: Fedora Extras Quality Assurance
Depends On:
TreeView+ depends on / blocked
Reported: 2011-08-08 22:37 UTC by Samuel Sieb
Modified: 2011-08-09 00:00 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2011-08-09 00:00:56 UTC

Attachments (Terms of Use)

Description Samuel Sieb 2011-08-08 22:37:12 UTC
A notification system for changes would be very useful.

For example, to be able to automatically create NFS mounted home directories on the server when users are created.

Comment 1 Dmitri Pal 2011-08-08 23:19:11 UTC
What kind of notification system you have in mind? You can monitor the entryUsn and do the updates if you see that a user entry was added. It is unclear what kind of component IPA would have to provide as different people would be interested in monitoring different things. You can also use the replication/changlog/synch capabilities to keep track of changes and filter the ones you care about and perform an action. It is really very custom and it would be hard to come up with a generic solution that would make sense to invest time to. But may be I am missing something.


Comment 2 Samuel Sieb 2011-08-08 23:36:21 UTC
Sorry about the brief description.  There was some discussion on the IRC channel about this.  I'm looking for immediate notification of change events.  The likeliest options discussed were AMQP and/or D-bus.

It was suggested that I could use the retro changelog and persistant searches as a workaround for now, but that long-term the retro changelog is not supported and not recommended.

Re-reading my IRC logs, I just realized I misread and this was supposed to be filed in the trac system...

I will close this bug with the upstream trac link when I open a ticket there.

Comment 3 Samuel Sieb 2011-08-09 00:00:56 UTC
I don't seem to be able to link to the upstream bug so here it is:

Note You need to log in before you can comment on or make changes to this bug.