Ability to specify availabilty zone when restoring a backup

Bug #1749888 reported by Sam Morrison
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
In Progress
Wishlist
Rajat Dhasmana

Bug Description

Would be good if you could specify an availability zone when restoring a backup. This would then restore the backup onto a cinder-volume in the desired availability-zone.

Revision history for this message
Gorka Eguileor (gorka) wrote :

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...

Revision history for this message
Sam Morrison (sorrison) wrote :

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?

Revision history for this message
Deepak Mourya (mourya007) wrote :

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

Revision history for this message
Sam Morrison (sorrison) wrote :

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

Changed in cinder:
assignee: nobody → Rajat Dhasmana (whoami-rajat)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to cinder (master)

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

Changed in cinder:
status: New → In Progress
Eric Harney (eharney)
Changed in cinder:
importance: Undecided → Wishlist
Revision history for this message
TommyLike (hu-husheng) wrote :

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

Revision history for this message
Sam Morrison (sorrison) wrote :

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.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Related fix proposed to cinder-specs (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder-specs (master)

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

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on cinder (master)

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

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.