Hide Forgot
Cloned from launchpad blueprint https://blueprints.launchpad.net/keystone/+spec/event-notif-extensions. Description: Problem Statement Keystone extensions are creating and managing data tables independently from the "core" code. These extensions may create data that have interdependencies with the core data. For instance an extension can create extra data related to a user or a project or establish relationship between two entities. Keystone is not currently providing a method for the extensions to react to changes in the core data enabling them to clean/reflect the state changes in core. Solution The solution is to leverage the existing notification method for Create, Update and Delete and having a mechanism for extensions to register to those events providing a callback. When an event is fired the EvenHandler will go through the list of extensions that have subscribed to that event and invoke their callbacks. The extensions are now responsible of eliminate any data inconsistency that may be present and/or perform any actions that are necessary/required. Specification URL (additional information): None
Need info: 1) The blueprint is a simple copy-paste of this bug, and provides no additional technical data on the feature design 2) Need documentation on writing keystone extensios 3) Need documentation on the new notification framework and how to make use of it
(In reply to Udi from comment #2) > Need info: > 1) The blueprint is a simple copy-paste of this bug, and provides no > additional technical data on the feature design > 2) Need documentation on writing keystone extensios > 3) Need documentation on the new notification framework and how to make use > of it The documentation for developing extensions that use the new internal notification framework is located here: https://github.com/openstack/keystone/blob/master/doc/source/extension_development.rst#event-callbacks
*** Bug 1053724 has been marked as a duplicate of this bug. ***