[pve-devel] Disk cloning feature for shared lvm storage
Dietmar Maurer
dietmar at proxmox.com
Fri Oct 14 11:32:41 CEST 2011
> OK so copying and moving should be handled by storage_migrate? Do we need
> to rename it in that case?
I guess the name is not really important.
> Should i add a flag like $delete_src? So
> storage_migrate can do copy and move actions.
sounds reasonable.
>Oder should i add an action
> parameter which can be copy or move?
>
> Should we block / stop the action if the src volume is in use? How can we check
> that?
The caller need to check that.
> Then our decisions how to handle the action are based on:
> action (copy/move)
> storage_id (src != dst or src = dst)
> type (dir/nfs/lvm)
> shared (1/0)
>
> I think we should then write down what should happen on each cobination.
> I'm not so familar with lvm so i def. need help with that. As we have a lot of
> different combinations any idea on how to write them down so that they're still
> readable?
Sorry, I currently simple have no time to work on that. I need to finish the 2.0 things first.
- Dietmar
More information about the pve-devel
mailing list