Registry notifications should be added for trunk create/update/delete,
and SDN controllers as subscribers will need more callbacks as PRECOMMIT
events.
A standardized notification payload will consist of the following:
- context
- trunk_id
- current_trunk
- original_trunk
- subports
This standardized payload will be used in all trunk-related
notifications (trunk create/update/delete and subport add/remove) and
represents the maximum possible amount of information that can be given
in order to future-proof them.
As a bug fix, AFTER_REMOVE event on subport shouldn't be called
during the db transaction, but after the db commit.
Partially-implements: blueprint vlan-aware-vms
Change-Id: Ic1f44fa53cf9f10bd029ea47824e8ba91a8ab485
Co-Authored-By: Isaku Yamahata <isaku.yamahata@intel.com>
6877b47105