Don't change volume's status when create backups from snapshots
when users try to create a backup from a snapshot, the volume
related to the snapshot is set to backing-up during the action
and can't be used for other actions.
When create a backup from a large snapshot, such as larger
than 1 TB, it will cost few hours generally. It's really a
problem that the volume is not available for such a long time.
If the snapshot is provided, we change the status of the snapshot;
otherwise, we change the status of the volume as usual.
This patch added "backing-up" status for snapshot as well
Reviewed: https:/ /review. openstack. org/442241 /git.openstack. org/cgit/ openstack/ cinder/ commit/ ?id=d304f621c23 c81580fbddaf61e 61ef135558acd4
Committed: https:/
Submitter: Jenkins
Branch: master
commit d304f621c23c815 80fbddaf61e61ef 135558acd4
Author: wangxiyuan <email address hidden>
Date: Tue Mar 7 10:42:02 2017 +0800
Don't change volume's status when create backups from snapshots
when users try to create a backup from a snapshot, the volume
related to the snapshot is set to backing-up during the action
and can't be used for other actions.
When create a backup from a large snapshot, such as larger
than 1 TB, it will cost few hours generally. It's really a
problem that the volume is not available for such a long time.
If the snapshot is provided, we change the status of the snapshot;
otherwise, we change the status of the volume as usual.
This patch added "backing-up" status for snapshot as well
DocImpact
Change-Id: I86d34c470fabbf 4132b5e004d9f36 8e751c893a5
Closes-bug: #1670541