I would like to add yet another perspective to this bug, which is Orchestration and interoperability of orchestration templates.
In Heat we have a delete_policy: snapshot for volume resources, which creates a volume backup on volume delete. However, AFAIK cinder-backup is an optional service, and thus Heat has no way to deduce from user-scoped API requests if this is available or not in order to fail early when such template is used.
I would like to add yet another perspective to this bug, which is Orchestration and interoperability of orchestration templates.
In Heat we have a delete_policy: snapshot for volume resources, which creates a volume backup on volume delete. However, AFAIK cinder-backup is an optional service, and thus Heat has no way to deduce from user-scoped API requests if this is available or not in order to fail early when such template is used.