[pve-devel] [PATCH] add ide-cd, ide-hd, scsi-cd, scsi-hd, scsi-block to device syntax

[Alexandre DERUMIER]

> > But they are a drawback with current config syntax, if we don't have 
> > initiator on the host side, we can't list iscsi devices so and we can't have disk 
> id. 

>>>Well, I think libiscsi also provides some way to list devices. 
>>>They have even a simple LD_PRELOAD library. 

Oh, I didn't know that ! i'll take a look.
Also some san have api. (nexenta by example). Citrix use StorageLink protocol, but proprietary :( 

> > 
> > So maybe we can change config syntax from by example: 
> > 
> > virtio0: 
> > nexenta:0.0.1.scsi-3600144f0f62f0e0000004cd953550008,cache=none 
> > 
> > to 
> > 
> > virtio0: nexenta:1,cache=none (just put lunid) 
> 
> >>If you define a storage, that storage is always activated on the host. 
> 
> I was thinking of using a syntax that works for both case, if in the future we 
> don't need to have storage activated on host. 

>>>We can't change the syntax of the existing storage type 'iscsi'. That type is assumed 
>>>to be available on the host (open-iscsi), and is used as base storage for LVM. 

>>>But you can simple create a new storage type (call it 'nexenta', or 'libiscsi'). Then 
>>>you can use whatever naming scheme you like. (Although I thing a LUN number 
>>>does not uniquely identify a devive.) 

ok,you are right, it can be better/cleaner and don't break current work.


>>>But how can we implement backup/restore for such storage? 
Good question, I didn't have think about it. (I personnaly don't use backup/restore from proxmox, but use snapshot/restore from my san.)


I'll do some tests this month, I keep you in touch.

Regards,

Alexandre


-------------- next part --------------
A non-text attachment was scrubbed...
Name: aderumier.vcf
Type: text/x-vcard
Size: 183 bytes
Desc: not available
URL: <http://lists.proxmox.com/pipermail/pve-devel/attachments/20111208/6dc78f8c/attachment.vcf>