Hi all, continuing the discussion: So, what to do ? Create/Enable SCSI StoragePool ?, then list FC devices on it ? ############## from previous emails ################ - Fibre Channel is used as a subtype of SCSI - FC LUNs will be mapped as /dev/sdX devices - Those devices can be used as PV in a VG , or as a Logical StoragePool - LUNs can also be mapped as /dev/disk/by-id/wwn-0x600507680280865df800000000000060 Links: http://wiki.libvirt.org/page/NPIV_in_libvirt#NPIV_in_libvirt http://libvirt.org/formatstorage.html (search for 'fc_host') ##############################################
Hi Rodrigo, In my understanding, this task could include the following sub-tasks: 1. Allow user to define a storage pool by specifying a fc host. (by the second link you added) 2. Allow user to configure vm to use LUN contained in the storage pool defined in 1. It can be done by "type='volume'", which only available from libvirt 1.0.5. You also can get an example from the link 1 you added. That also needs to change the vm template and kimchi's vm creation flow, because kimchi can't use existing volume or image. And we can't create new volume in a 'scsi' pool or 'iscsi' pool. For these two kinds of storage pool, we only can use the volumes(LUNs) predefined on the storage backend. 3. Add a 'refresh' operation for the storage pool. It will invoke a scsi rescan automatically by libvirt. So after the storage admin add new luns on the storage, it can just click the 'refresh' button instead of manually invoking rescan manually. What benefits can provide this feature? Actually, except it can help the host storage management a little bit easier, I don't see others. Because we can just use logical pool on top of the LUNs provided by fc host. It also provide more flexibility. It doesn't like iscsi, libvirt provide connection management. For fc host, kernel can probe and attach the LUNs on boot up. On Fri 20 Dec 2013 05:27:52 AM CST, Rodrigo Trujillo wrote:
Hi all,
continuing the discussion:
So, what to do ? Create/Enable SCSI StoragePool ?, then list FC devices on it ?
############## from previous emails ################
- Fibre Channel is used as a subtype of SCSI - FC LUNs will be mapped as /dev/sdX devices - Those devices can be used as PV in a VG , or as a Logical StoragePool - LUNs can also be mapped as /dev/disk/by-id/wwn-0x600507680280865df800000000000060
Links: http://wiki.libvirt.org/page/NPIV_in_libvirt#NPIV_in_libvirt http://libvirt.org/formatstorage.html (search for 'fc_host')
##############################################
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
On 12/20/2013 04:02 AM, Mark Wu wrote:
Hi Rodrigo,
In my understanding, this task could include the following sub-tasks:
1. Allow user to define a storage pool by specifying a fc host. (by the second link you added) 2. Allow user to configure vm to use LUN contained in the storage pool defined in 1. It can be done by "type='volume'", which only available from libvirt 1.0.5. You also can get an example from the link 1 you added. That also needs to change the vm template and kimchi's vm creation flow, because kimchi can't use existing volume or image. And we can't create new volume in a 'scsi' pool or 'iscsi' pool. For these two kinds of storage pool, we only can use the volumes(LUNs) predefined on the storage backend. 3. Add a 'refresh' operation for the storage pool. It will invoke a scsi rescan automatically by libvirt. So after the storage admin add new luns on the storage, it can just click the 'refresh' button instead of manually invoking rescan manually.
I have the same idea as Mark. Just one more point about 1: while creating a new pool the user must specify the fc_host and wwnn:wwpn pairs Based on that we should be able to expose the wwnn:wwpn pairs to user - which would be a separated task. From that, I would like to see: - one patch set that implements items 1 and 2 - one patch set that implements item 3 - one patch set that exposes wwnn:wwpn pairs to user
What benefits can provide this feature? Actually, except it can help the host storage management a little bit easier, I don't see others. Because we can just use logical pool on top of the LUNs provided by fc host. It also provide more flexibility. It doesn't like iscsi, libvirt provide connection management. For fc host, kernel can probe and attach the LUNs on boot up.
On Fri 20 Dec 2013 05:27:52 AM CST, Rodrigo Trujillo wrote:
Hi all,
continuing the discussion:
So, what to do ? Create/Enable SCSI StoragePool ?, then list FC devices on it ?
############## from previous emails ################
- Fibre Channel is used as a subtype of SCSI - FC LUNs will be mapped as /dev/sdX devices - Those devices can be used as PV in a VG , or as a Logical StoragePool - LUNs can also be mapped as /dev/disk/by-id/wwn-0x600507680280865df800000000000060
Links: http://wiki.libvirt.org/page/NPIV_in_libvirt#NPIV_in_libvirt http://libvirt.org/formatstorage.html (search for 'fc_host')
##############################################
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
_______________________________________________ Kimchi-devel mailing list Kimchi-devel@ovirt.org http://lists.ovirt.org/mailman/listinfo/kimchi-devel
participants (3)
-
Aline Manera -
Mark Wu -
Rodrigo Trujillo