| 2013-08-07 12:02:34 |
Edward Hope-Morley |
bug |
|
|
added bug |
| 2013-08-07 12:02:49 |
Edward Hope-Morley |
description |
RBD volume cloning currently does a full copy. We could speed this up by creating a copy-on-write clone instead. This would require taking a snapshot of the volume first and then creating a copy-on-write clone. There are different ways we could implement this, especially in view of upcoming auto-flattening support, but for now I suggest we do it as follows:
* create discrete snapshot of volume if one does not already exist
* if snapshot has > some-configurable-number snapshots (detect with list_children()) we disallow the clone for performance degradation reasons and enforce a full copy as before - this can be disabled when auto-flattening comes in.
* create copy-on-write clone if snapshot
* et voila! |
RBD volume cloning currently does a full copy. We could speed this up by creating a copy-on-write clone instead. This would require taking a snapshot of the volume first and then creating a copy-on-write clone. There are different ways we could implement this, especially in view of upcoming auto-flattening support, but for now I suggest we do it as follows:
* create discrete snapshot of volume if one does not already exist
* if snapshot has > some-configurable-number snapshots (detect with list_children()) we disallow the clone for performance degradation reasons and enforce a full copy as before - this can be disabled when auto-flattening comes in.
* create copy-on-write clone of snapshot
* et voila! |
|
| 2013-08-07 12:03:03 |
Edward Hope-Morley |
bug |
|
|
added subscriber Josh Durgin |
| 2013-08-07 12:03:20 |
Edward Hope-Morley |
cinder: assignee |
|
Edward Hope-Morley (hopem) |
|
| 2013-08-07 12:03:58 |
Edward Hope-Morley |
summary |
use copy-on-write for rbd volume cloning |
use copy-on-write for all rbd volume cloning |
|
| 2013-08-07 12:04:21 |
Edward Hope-Morley |
description |
RBD volume cloning currently does a full copy. We could speed this up by creating a copy-on-write clone instead. This would require taking a snapshot of the volume first and then creating a copy-on-write clone. There are different ways we could implement this, especially in view of upcoming auto-flattening support, but for now I suggest we do it as follows:
* create discrete snapshot of volume if one does not already exist
* if snapshot has > some-configurable-number snapshots (detect with list_children()) we disallow the clone for performance degradation reasons and enforce a full copy as before - this can be disabled when auto-flattening comes in.
* create copy-on-write clone of snapshot
* et voila! |
RBD volume cloning (from vol not snap) currently does a full copy. We could speed this up by creating a copy-on-write clone instead. This would require taking a snapshot of the volume first and then creating a copy-on-write clone. There are different ways we could implement this, especially in view of upcoming auto-flattening support, but for now I suggest we do it as follows:
* create discrete snapshot of volume if one does not already exist
* if snapshot has > some-configurable-number snapshots (detect with list_children()) we disallow the clone for performance degradation reasons and enforce a full copy as before - this can be disabled when auto-flattening comes in.
* create copy-on-write clone of snapshot
* et voila! |
|
| 2013-08-07 14:05:01 |
Edward Hope-Morley |
bug |
|
|
added subscriber xiaoxi_chen |
| 2013-08-07 14:42:15 |
Xiaoxi Chen |
cinder: status |
New |
Opinion |
|
| 2013-08-07 15:01:34 |
Edward Hope-Morley |
cinder: status |
Opinion |
In Progress |
|
| 2013-09-06 00:34:03 |
OpenStack Infra |
cinder: status |
In Progress |
Fix Committed |
|
| 2013-10-04 07:34:45 |
Thierry Carrez |
cinder: status |
Fix Committed |
Fix Released |
|
| 2013-10-04 07:34:45 |
Thierry Carrez |
cinder: milestone |
|
havana-rc1 |
|
| 2013-10-17 10:30:28 |
Thierry Carrez |
cinder: milestone |
havana-rc1 |
2013.2 |
|
| 2021-06-30 13:17:01 |
Christian Rohmann |
bug |
|
|
added subscriber Christian Rohmann |
