Backlog #2469
evaluate removing the cLVM dependency for lvm and fs_lvm drivers
| Status: | Pending | Start date: | 11/18/2013 | |
|---|---|---|---|---|
| Priority: | Normal | Due date: | ||
| Assignee: |  Jaime Melis | % Done: | 0% | |
| Category: | Drivers - Storage | |||
| Target version: | - |
Description
If all the operations are run in the frontend, we could do without cLVM. We will also need pre/post migration hooks.
History
#1
Updated by Ruben S. Montero over 7 years ago
- Tracker changed from Feature to Backlog
- Target version deleted (
Release 4.6)
#2
Updated by Ruben S. Montero over 7 years ago
- Status changed from New to Pending
#3
Updated by Ruben S. Montero over 7 years ago
- Category set to Drivers - Storage
#4
Updated by Juergen Gotteswinter about 7 years ago
why not using libvirts builtin locking logic? ovirt uses it, and it works fairly well. it just needs a nfs share which can be seen by every node.
pre/postmigration hooks whould be needed here as well.
#5
Updated by Juergen Gotteswinter about 7 years ago
Juergen Gotteswinter wrote:
why not using libvirts builtin locking logic? ovirt uses it, and it works fairly well. it just needs a nfs share which can be seen by every node.
pre/postmigration hooks whould be needed here as well.
sorry, link forgotten...
http://libvirt.org/locking.html
http://blog.abiquolabs.com/locking-disks-on-kvm-through-libvirt-lock-sanlock/
2nd link describes it very well and straight forward