Bug 1041011 - [RFE][nova]: Support to backup for instance that boot from volume
Summary: [RFE][nova]: Support to backup for instance that boot from volume
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: RFEs
Version: unspecified
Hardware: Unspecified
OS: Unspecified
unspecified
low
Target Milestone: ---
: ---
Assignee: RHOS Maint
QA Contact:
URL: https://blueprints.launchpad.net/nova...
Whiteboard: upstream_milestone_none upstream_stat...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2013-12-12 13:24 UTC by RHOS Integration
Modified: 2015-03-19 17:33 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Enhancement
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-03-19 17:33:05 UTC
Target Upstream Version:


Attachments (Terms of Use)

Description RHOS Integration 2013-12-12 13:24:40 UTC
Cloned from launchpad blueprint https://blueprints.launchpad.net/nova/+spec/folsom-backup-for-ebs.

Description:

It support to backup for instance that was made by 'auto-create-boot-volumes' features.
There is different between normal instance and instance using 'auto-create-boot-volumes'.
normal instance's root volume is just file. For example, /var/lib/nova/instances/instance-XXXXXX/disk
but root volume of instance using 'auto-create-boot-volumes' is a device. For example, /dev/disk/by-path/ip-10.245.34.2:3260-iscsi-iqn.2003-10.com.lefthandnetworks:cxx-zxx-:611:cxx-pxx-lun-0
In backup logic, instance's root volume can be snapshot using qemu-img. But It cannot execute to  instance using 'auto-create-boot-volumes'. because root volume is a device, not a qcow2 file.
So, This blueprint add some command for backup instance using 'auto-create-boot-volumes'. 


Specification URL (additional information):

None


Note You need to log in before you can comment on or make changes to this bug.