[pve-devel] Disk cloning feature for shared lvm storage

Stefan Priebe - Profihost AG s.priebe at profihost.ag
Fri Oct 14 11:50:49 CEST 2011


Am 14.10.2011 11:32, schrieb Dietmar Maurer:
>> 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.
OK.

>> 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.

OK i fully understand that.

pvesh does have a reverse map i would implement copy also as POST - then 
the reverse map gets broken.

sub reverse_map_cmd {
     my $method = shift;

     my $mmap = {
         GET => 'get',
         PUT => 'set',
         POST => 'create',
         POST => 'copy',
         DELETE => 'delete',
     };

Stefan



More information about the pve-devel mailing list