a130387b45
When running Cinder with notifications disabled we are still doing all the work and calls to Oslo message notifier and it's there, at the very last moment when it's going to send the message that it checks that there's no actual extension loaded in the driver manager and skips the actual send of the data. This is considerably wasteful considering that for some of the notifications we are actually querying the DB to get data, for example volume attachments and glance metadata information when notifying about volume usage. This patch proposes short-circuiting notification methods as much as possible to optimize code execution when Cinder has no notification transport mechanism configured, as is the case when deployed as a standalone SDS service. Closes-Bug: #1660303 Change-Id: I77f655d3ef90088ce71304da5d4ea7b543991e90 |
||
|---|---|---|
| .. | ||
| evaluator | ||
| filters | ||
| flows | ||
| weights | ||
| __init__.py | ||
| base_filter.py | ||
| base_handler.py | ||
| base_weight.py | ||
| driver.py | ||
| filter_scheduler.py | ||
| host_manager.py | ||
| manager.py | ||
| rpcapi.py | ||
| scheduler_options.py | ||