Bug 1041011

Summary: [RFE][nova]: Support to backup for instance that boot from volume
Product: Red Hat OpenStack Reporter: RHOS Integration <rhos-integ>
Component: RFEsAssignee: RHOS Maint <rhos-maint>
Status: CLOSED UPSTREAM QA Contact:
Severity: low Docs Contact:
Priority: unspecified    
Version: unspecifiedCC: markmc, yeylon
Target Milestone: ---Keywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
URL: https://blueprints.launchpad.net/nova/+spec/folsom-backup-for-ebs
Whiteboard: upstream_milestone_none upstream_status_unknown upstream_definition_obsolete
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-03-19 17:33:05 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

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