Logging the ID of the callback should be enough
since the ID contains the path to the callback.
Before:
Notify callbacks
[('neutron.services.segments.db._update_segment_host_mapping_for_agent-8784700722903',
<function _update_segment_host_mapping_for_agent at 0x7fd58f74ed70>)]
for agent, after_create _notify_loop"
After:
Notify callbacks
['neutron.services.segments.db._update_segment_host_mapping_for_agent-8784700722903']
for agent, after_create _notify_loop"
TrivialFix
Change-Id: Ice15c89c7a6288af5a0385df9e3e74e9d9d6f977
This patch builds a small hierarchy of event objects that
represent the payload for callback notification events. The
overall goal of this work is to begin moving away from the
existing unstructured **kwargs passed today and standardize
on a common set of event payload objects; the beginning of such
contained herein.
A PoC/dummy patch for neutron is provided in [1] that exemplifies
consumption of the new API by:
- Removes neutron.callbacks and moves all uses to
neutron_lib.callbacks.
- Neutron uses of callbacks for BEFORE_RESPONSE events
now use neutron-lib.
- Neutron uses of callbacks for ROUTER and PROCESS
resource events now use neutron-lib.
- Neutron UTs updated to pass with this patch.
For existing discussion on this approach please see [2][3].
Co-Authored-By: Armando Migliaccio <armamig@gmail.com>
[1] https://review.openstack.org/400404/
[2] https://review.openstack.org/#/c/345718
[3] https://review.openstack.org/#/c/342304
Change-Id: If76457b1f0d5d3479e394d0dba3b22a90928f0f2
