on 2013/12/10 21:56, Rodrigo Trujillo wrote:
> Hi folks,
>
> I am starting to work in this feature, but I did not understand exactly
> what the project need.
> The wiki says:
>
> """
> Create a new FC libvirt storage pool
>
> * Allow for FC target specification.
> * Associate the target with a storage pool.
>
> """
>
> As far as I know FC luns are mapped in linux as devices ( /dev/sdX ),
> and can be mounted normally.
> So, is the request related to pass the devices or mounting points to
> kimchi ? In this case, this is
> almost the same that create a Filesystem pool.
> So, kinchi would have to check if the filesystem belongs to a FC device.
>
> Thoughts ?
>
> Rodrigo
>
The FC configuration is rather automatic and simple if the HBA card and
switch are installed correctly.
To trigger the FC scan, we usually just run
echo "- - -" > /sys/class/scsi_host/hostX/scan
After the OS scans for FC LUNs, they appear as /dev/sdX. There is no
step like iSCSI login to specific target. In libvirt official
documentation it mentions iSCSI storage pool but not FC pool. Does the
task mean for FCoE?
I think FC mapped /dev/sdX can be used as PVs in a VG, so the tasks "Add
a new local physical disk to a new libvirt storage pool" and "Add a new
local physical disk to an existing libvirt storage pool" should cover it
already. Maybe we can inspect the generated /dev/sdX and collect those
from the specific target and add them to a storage pool, or create a new
logical volume storage pool for them.
--
Thanks and best regards!
Zhou Zheng Sheng / 周征晟
E-mail:
zhsh...@linux.vnet.ibm.com
Telephone: 86-10-82454397