Ideally:
cinder-volume-support
if it exists at all should only contain accesses that are specific and relevant to all the volume implementation, or at least a large subset of them- it would preferable whenever the storage technology is well understood enough to have specific interfaces to access the storage that could be used in other contexts, if the latter is not true then we need to consider whether we need more specific -support interfaces
- related to the last point, it might not be relevant for storage access, but there is also the option of self-connected
custom-device
slot and plug to access uncommon devices specific to a snap operation