notifier_strategy should not be restricted to a specific set of drivers
Bug #1018638 reported by
Brian Waldon
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Glance |
Fix Released
|
Low
|
Brian Waldon |
Bug Description
glance/
Changed in glance: | |
status: | Fix Committed → Fix Released |
Changed in glance: | |
milestone: | folsom-2 → 2012.2 |
To post a comment you must log in.
Reviewed: https:/ /review. openstack. org/9079 github. com/openstack/ glance/ commit/ 2a61bf38ff6dae1 6083145e6f27d66 731d5c3271
Committed: http://
Submitter: Jenkins
Branch: master
commit 2a61bf38ff6dae1 6083145e6f27d66 731d5c3271
Author: Brian Waldon <email address hidden>
Date: Wed Jun 27 13:49:15 2012 -0700
Allow CONF.notifier_ strategy to be a full path
Rather than limit the notifier_strategy to a list of internal
drivers, we should also allow a user to supply a full path
to a custom driver. This is going to help us functionally test
our notification system without having to ship a fake driver.
Fixes bug 1018638
Change-Id: Ib1cae7b979dabf aa6b8b5aa59719a ad2ac12d169