WARNING - OLD ARCHIVES

This is an archived copy of the Xen.org mailing list, which we have preserved to ensure that existing links to archives are not broken. The live archive, which contains the latest emails, can be found at http://lists.xen.org/
   
 
 
Xen 
 
Home Products Support Community News
 
   
 

xen-api

[Xen-API] Re: [Xen-devel] [RFC][PATCH] Enhance XenAPI for pvSCSI

To: Yosuke Iwamatsu <y-iwamatsu@xxxxxxxxxxxxx>
Subject: [Xen-API] Re: [Xen-devel] [RFC][PATCH] Enhance XenAPI for pvSCSI
From: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
Date: Mon, 08 Sep 2008 14:03:27 +0900
Cc: kama@xxxxxxxxxxxxxx, t.horikoshi@xxxxxxxxxxxxxx, xen-devel@xxxxxxxxxxxxxxxxxxx, xen-api@xxxxxxxxxxxxxxxxxxx
Delivery-date: Sun, 07 Sep 2008 22:03:49 -0700
Envelope-to: www-data@xxxxxxxxxxxxxxxxxxx
In-reply-to: <48C0F35A.4080107@xxxxxxxxxxxxx>
List-help: <mailto:xen-api-request@lists.xensource.com?subject=help>
List-id: Discussion of API issues surrounding Xen <xen-api.lists.xensource.com>
List-post: <mailto:xen-api@lists.xensource.com>
List-subscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=subscribe>
List-unsubscribe: <http://lists.xensource.com/mailman/listinfo/xen-api>, <mailto:xen-api-request@lists.xensource.com?subject=unsubscribe>
References: <41C90D924C4601kanno.masaki@xxxxxxxxxxxxxx> <48C0F35A.4080107@xxxxxxxxxxxxx>
Sender: xen-api-bounces@xxxxxxxxxxxxxxxxxxx
Hi Yosuke,

Thanks for your comment.

As Kamada said, the pvSCSI driver emulates some SCSI commands, 
the pvSCSI driver does not always pass through SCSI commands. 
So I hesitate to call pvSCSI "direct". 

Best regards,
 Kan

Fri, 05 Sep 2008 17:52:42 +0900, Yosuke Iwamatsu wrote:

>Hi,
>
>Masaki Kanno wrote:
>> Hi,
>> 
>> I would like to enhance XenAPI for pvSCSI. 
>> At the beginning, I updated only the document of XenAPI.  I'm going 
>> to implement XenAPI of pvSCSI along the document.  Could you comment?
>> 
>> The following classes and RPCs are added by the enhancement. 
>>  Classes:
>>   - VSCSI class
>>      This is a class for virtual SCSI devices.
>
>It's nice to keep xen-api updated with new features :-)
>One thing I want to point out is about the class name.
>I think 'DSCSI' (direct scsi) is appropriate rather than 'VSCSI',
>because pvSCSI driver doesn't really provide virtual scsi luns but
>passes through scsi commands to real scsi luns, as far as I understand.
>
>Regards,
>-- Yosuke Iwamatsu
>
>>   - PSCSI class
>>      This is a class for physical SCSI devices.
>> 
>>  RPCs:
>>   - VSCSI class
>>    -- get_all
>>        A list of all VSCSIs known to the system is gotten.
>>    -- get_uuid
>>        An UUID of the VSCSI is gotten.
>>    -- get_VM
>>        A VM ref of the VSCSI is gotten.
>>    -- get_PSCSI
>>        A PSCSI ref of the VSCSI is gotten.
>>    -- get_virtual_host
>>        A virtual host number of the VSCSI is gotten.
>>    -- get_virtual_channel
>>        A virtual channel number of the VSCSI is gotten.
>>    -- get_virtual_target
>>        A virtual target number of the VSCSI is gotten.
>>    -- get_virtual_lun
>>        A virtual logical unit number of the VSCSI is gotten.
>>    -- get_virtual_HCTL
>>        A virtual HCTL (string of "<host>:<channel>:<target>:<lun>") 
>>        of the VSCSI is gotten.
>>    -- create
>>        A new VSCSI instance is created.
>>    -- destroy
>>        The VSCSI instance is destroyed.
>>    -- get_by_uuid
>>        A VSCSI ref of the UUID is gotten.
>>    -- get_record
>>        A VSCSI record of the VSCSI is gotten.
>> 
>>   - PSCSI class
>>    -- get_all
>>        A list of all PSCSIs known to the system is gotten.
>>    -- get_uuid
>>        An UUID of the PSCSI is gotten.
>>    -- get_host
>>        A host ref of the PSCSI is gotten.
>>    -- get_physical_host
>>        A physical host number of the PSCSI is gotten.
>>    -- get_physical_channel
>>        A physical channel number of the PSCSI is gotten.
>>    -- get_physical_target
>>        A physical target number of the PSCSI is gotten.
>>    -- get_physical_lun
>>        A physical logical unit number of the PSCSI is gotten.
>>    -- get_physical_HCTL
>>        A physical HCTL (string of "<host>:<channel>:<target>:<lun>") 
>>        of the PSCSI is gotten.
>>    -- get_vendor_name
>>        A vendor name of the PSCSI is gotten.
>>    -- get_model
>>        A model name of the PSCSI is gotten.
>>    -- get_type_id
>>        An ID of device types of the PSCSI is gotten. (If disk, the ID 
>>        is 0.  If tape, the ID is 1.)
>>    -- get_type
>>        A device type string of the PSCSI is gotten.
>>    -- get_sg_name
>>        A SCSI generic (sg) device name of the PSCSI is gotten.
>>    -- get_revision
>>        A revision string of the PSCSI is gotten.
>>    -- get_scsi_id
>>        A SCSI ID string of the PSCSI is gotten. The string is a result 
>>        of 'scsi_id -gu -s'.
>>    -- get_scsi_level
>>        A SCSI level of the PSCSI is gotten.
>>    -- get_by_uuid
>>        A PSCSI ref of the UUID is gotten.
>>    -- get_record
>>        A PSCSI record of the PSCSI is gotten.
>> 
>>   - VM class
>>    -- get_VSCSIs
>>        VSCSI refs of the VM are gotten.
>> 
>>   - host class
>>    -- get_PSCSIs
>>        PSCSI refs of the host are gotten.
>> 
>> 
>> Signed-off-by: Masaki Kanno <kanno.masaki@xxxxxxxxxxxxxx>
>> 
>> Best regards,
>>  Kan
>> 
>> 
>> ------------------------------------------------------------------------
>> 
>> _______________________________________________
>> Xen-devel mailing list
>> Xen-devel@xxxxxxxxxxxxxxxxxxx
>> http://lists.xensource.com/xen-devel
>
>
>
>_______________________________________________
>Xen-devel mailing list
>Xen-devel@xxxxxxxxxxxxxxxxxxx
>http://lists.xensource.com/xen-devel


_______________________________________________
xen-api mailing list
xen-api@xxxxxxxxxxxxxxxxxxx
http://lists.xensource.com/mailman/listinfo/xen-api