Comment 14 for bug 1479842

Dropping devstack from this. As a tactical fix for liberty we're going to just make sure the os-brick.filters contents are in volume.filters in cinder and compute.filters in nova. This is not ideal long-term because of the tight-coupling it creates and lockstep upgrades required for nova and cinder (and os-brick).

We're going to add oslo.rootwrap here since what we'd like to see discussed at the mitaka summit is the capability in oslo.rootwrap to load the package_data automatically from os-brick.

So the thinking is something like this, nova's rootwrap.conf would have some kind of key=value of library to filter to load, e.g.:

filters_from_libraries: os-brick=os-brick.filters(,os-brick-2.filters,etc),foo-lib=foo.filters

Then oslo.rootwrap could parse that and use:

http://peak.telecommunity.com/DevCenter/PythonEggs#accessing-package-resources

To load the data, e.g. resource_filename('os-brick', 'os-brick.filters').