Rawlin Peters 6877b47105 Add notifications for trunk CRUD and standardize payload ... 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>		2016-07-26 10:24:57 -06:00
..
auto_allocate	Use exceptions from neutron-lib	2016-04-21 21:29:44 -04:00
metering	Do not inherit test case classes from regular Neutron classes	2016-05-26 13:06:49 +03:00
qos	qos: support native sorting/pagination for policies and rules	2016-06-15 14:19:09 +00:00
trunk	Add notifications for trunk CRUD and standardize payload	2016-07-26 10:24:57 -06:00
__init__.py	Empty files should not contain copyright or license	2014-10-20 00:50:32 +00:00
test_provider_configuration.py	Guard against config_dirs not defined on ConfigOpts	2016-05-31 17:01:53 +02:00