Ability to specify availabilty zone when restoring a backup

There are currently 2 ways to do this:

- Since API microversion 3.47 you can do "cinder create --backup-id $BACKUP_ID --availability-zone $AZ $SIZE"

- In older versions you could create an empty volume of the right size and desired volume type and AZ and then do a restore to that volume with "cinder backup-restore --volume-id $BACKUP_ID".

I think the best approach to restore your backups at the moment is via the create method, because even if we add the AZ to the backup-restore method we would also have to add the volume-type parameter...

Maybe it should be handled like a snapshot is and instead of having a separate method (backup-restore) you can pass a backup ID into the create volume call?

hi,

I am not able to reproduce this bug because cinder create already has an option for availability zone. https://github.com/openstack/cinder/blob/517dcf451a4c4dff32824dc6af324c38f70dbd9f/cinder/api/v2/volumes.py#L263

It's not the create call I'm talking about, it's the backup-restore call

Fix proposed to branch: master
Review: https://review.openstack.org/574178

What's the difference if I create a volume with specified AZ, and then restore that volume?

I think maybe the best way to handle this is to support a backup-id argument to the volume-create method? Then it acts in the same way as creating a volume from a snapshot. The backup-restore method could be deprecated.

Related fix proposed to branch: master
Review: https://review.openstack.org/576479

Change abandoned by Rajat Dhasmana (<email address hidden>) on branch: master
Review: https://review.openstack.org/576479
Reason: http://eavesdrop.openstack.org/meetings/cinder/2018/cinder.2018-06-27-16.03.log.html#l-56

Change abandoned by Rajat Dhasmana (<email address hidden>) on branch: master
Review: https://review.openstack.org/574178
Reason: https://review.openstack.org/#/c/576479/