Making Payload consistent for all the operations of an object

[Manjeet Singh Bhatia]

I observed while implementing L3 flavor driver for OpenDaylight, the payload sent to all the callbacks in a driver is not consistent, which in some cases is an oslo versioned object and sometimes a dictionary, due to this driver always have to do tweaks and hacks for driver and test code. It would make more sense to have one type of payload passed for all the operations of an object, which will help achieving some stability and simplicity.

[Manjeet Singh Bhatia (manjeet-s-bhatia)]

and this not just for L3 resources but all resources inclusive of L2 and L3.

[Boden R (boden)]

This seems like something that will come out of the effort we have underway to standardize callback payloads using payload event objects [1]. Some of this work is already underway [2], and will continue in the Rocky time-frame. IMHO it seems best to just ensure the payloads are proper when changing to the payload objects as part of this work.

[1] https://docs.openstack.org/neutron-lib/latest/contributor/callbacks.html#event-payloads
[2] https://review.openstack.org/#/q/topic:use-callback-payloads

[Rodolfo Alonso (rodolfo-alonso-hernandez)]

Bug closed due to lack of activity, please feel free to reopen if needed.

During the last releases [1] we have been changing all event calls to use "payload". If any call is still unchanged, please open a new bug.

[1]https://review.opendev.org/q/topic:use-callback-payloads