Bug 1321043

Summary:	Backport "libvirt: make snapshot use RBD snapshot/clone when available"
Product:	Red Hat OpenStack	Reporter:	Chris St. Pierre <cstpierr>
Component:	openstack-nova	Assignee:	Eoghan Glynn <eglynn>
Status:	CLOSED DUPLICATE	QA Contact:	nlevinki <nlevinki>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.0 (Liberty)	CC:	berrange, dasmith, dcadzow, eglynn, jdonohue, kchamart, lyarwood, ndipanov, sbauza, sferdjao, sgordon, vromanso, yeylon
Target Milestone:	---	Keywords:	FeatureBackport
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-04-07 14:48:32 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Bug Depends On:
Bug Blocks:	1194008, 1295530

Description Chris St. Pierre 2016-03-24 14:23:14 UTC

Description of problem:

When backed by Ceph, Nova snapshots are unreasonably slow: https://bugs.launchpad.net/nova/+bug/1346525

There is an upstream fix in Mitaka (https://review.openstack.org/#/c/205282/), but upstream has refused to backport it to Liberty (https://review.openstack.org/#/c/287954/). We'd like it backported to OSP8, since the performance gains are quite significant.

Version-Release number of selected component (if applicable):

Nova 12.0.0

How reproducible:

Always.

Steps to Reproduce:

See https://bugs.launchpad.net/nova/+bug/1346525

Actual results:

See https://bugs.launchpad.net/nova/+bug/1346525

Expected results:

See https://bugs.launchpad.net/nova/+bug/1346525

Additional info:

Comment 2 Lee Yarwood 2016-04-07 14:48:32 UTC

Marking as a duplicate of BZ#1311314 where it was decided not to backport the new functionality from Mitaka into Liberty but instead carry forward our own implementation for one final cycle. We will then move to the new implementation in Mitaka.

*** This bug has been marked as a duplicate of bug 1311314 ***