When using ceph, creating large encrypted volumes can be very time-consuming
Bug #1883470 reported by
wanwencong
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Cinder |
In Progress
|
Undecided
|
wanwencong | ||
Bug Description
Because rbd import needs to scan the whole space, it is very time-consuming to create a large capacity encrypted volume. For example, a 2TB encrypted volume takes more than half an hour.
| Changed in cinder: | |
| assignee: | nobody → wanwencong (maydaycc) |
Revision history for this message
| wanwencong (maydaycc) wrote | #1 |
| summary: |
- Creating high-capacity encrypted volumes using RBD backend is very slow + When using ceph, creating large encrypted volumes can be very time- + consuming |
| tags: | added: ceph drivers rbd |
| Changed in cinder: | |
| status: | New → In Progress |
To post a comment you must log in.
When creating an encrypted volume with qemu-img command, we can change the target path from a local address to a RBD address. In this way, we do not need to execute the RBD import operation, so the creation time can be reduced from tens of minutes to tens of seconds