neutron/neutron/callbacks
Kevin Benton c17c78df7c Port device events for common agent
Some of the agent code may want to receive events whenever
a device is added/updated/deleted. Currently the only way
to do that is to modify the loop directly or create an
extension. Neither of these options are good if it's code
we don't want users to disable (the extensions) and it's
specific to one agent (so we don't want to modify the loop).

Partially-Implements: blueprint vlan-aware-vms
Change-Id: I3468c7f46cc1b4000cdd537e8f216d207a14727a
2016-08-02 20:53:59 +00:00
..
__init__.py Add callbacks-based system to Neutron 2015-02-25 06:11:59 -08:00
events.py Add two more callbacks registry events 2016-06-28 11:41:52 -07:00
exceptions.py Convert multiple exception types in the API 2016-06-08 16:54:24 -07:00
manager.py Separate exception class for retriables in callbacks 2016-06-22 23:03:09 +00:00
registry.py Add callbacks-based system to Neutron 2015-02-25 06:11:59 -08:00
resources.py Port device events for common agent 2016-08-02 20:53:59 +00:00