W dniu 13.05.2015 o 21:13, Andy Grover pisze: > On 05/13/2015 12:48 AM, Tomasz Charoński wrote: >> Dear Andy Grover, targetcli-fb Developers, >> >> firstly, I'd like to thank you for your contribution in targetcli and >> related libraries developing. I am writing to you to ask, if there it is >> possible to add to targetcli qla2xxx_npiv support. I have been studying >> this for 2 days now and it's hard to create NPIV targets manually. > > Hi Tomasz! > > I would hope we could add this and make it easier. I think some > challenges will be I don't have hardware to develop on, at least not > full-time, and also NPIV is a feature not represented in targetcli > before now. Some thought on how best to present it will be needed, see > below. Hi Andy, thank you for your engagement in this case. > >> To create NPIV WWN using qla2xxx you need: >> 1. Create FC host using vport_create: >> >> echo '1111222233334444:5555666677778888' > >> /sys/class/fc_host/host5/vport_create >> >> After this new /sys/class/fc_host/hostX will appear, but NPIV WWN is not >> discovered at FC switch yet. >> >> 2. Create the path: >> /sys/kernel/config/target/qla2xxx_npiv/21:00:00:xx:xx:xx:xx:11@5555666677778888:1111222233334444 >> >> >> where "21:00:00:xx:xx:xx:xx:11" is physical WWN taken from port_name >> (sed needed). > > Even though qla2xxx and qla2xxx_npiv are not represented > hierarchically in configfs (they're peers) I'm wondering if that's not > actually a mistake, and preferable to present differently in > targetcli. It might be clearer to show it hierarchically -- create an > "npivs" node: > > qla2xxx > o- 20:00:00:00:00:00:00:55 > o- acls > o- luns > o- npivs > > in which "npivs/ create 5555666677778888 npiv_wwnn=1111222233334444" > > would actually jump over to the qla2xxx_npiv configfs dir and set > stuff up. > > and then that would have its own "acls" and "luns" nodes too: > > qla2xxx > o- 20:00:00:00:00:00:00:55 > o- acls > o- luns > o- npivs > o- 5555666677778888 > o- acls > o- luns > > **OR** > > the phys wwpn node (e.g. "20:00..") could have a create_npiv command, > e.g.: > > 00:55>/ create_npiv 5555666677778888 npiv_wwnn=1111222233334444" > > leading to: > > qla2xxx > o- 20:00:00:00:00:00:00:55 > o- acls > o- luns > qla2xxx_npiv > o- 5555666677778888 [parent: 20:00:00:00:00:00:00:55] > o- acls > o- luns > > > my thoughts are to prefer the first way. It would be more work for the > way tcm_qla2xxx implements NPIV but assuming LIO gets more FC fabrics > in the future, I'm not sure we'd want them to do npiv like qla2xxx did. First of your representation concept seems to be great. Each NPIV has an option to set individual acls and luns, so it will be clear. In my opinion, also there is no sense in treating qla2xxx_npiv as a separate fabric, because it's served from the same driver (qla2xxx). NPIVs have to have their physical parent; the first representation give us an information about parent in more transparent way. > >> 3. qla2xxx_npiv directory seems to be the same as >> /sys/kernel/config/target/qla2xxx. After enabling tgpt_1 I can see >> "5555666677778888" at FC switch, however I can't successfuly share the >> LUN with an initiator. > > Have you created an ACL and lun mapping for that initiator? If that > doesn't fix it then I don't know. Yes, but I believe I made some mistake, so maybe let's focus on implementation in targetcli. > >> NPIV WWNs are needed to make user-friendly failover between hosts. >> >> I am eager to help you in this development, especially including testing >> this functionality in our infrastructure. > > Great! :-) > > Thanks -- Regards -- Andy > W dniu 13.05.2015 o 22:06, Jerome Martin pisze: > Tomasz, > > Just FYI, NPIV support is something on my roadmap for the coming > weeks, to be pushed into targetcli and rtslib mainline. > > Andy, if you want to give me a hand and contribute to testing, I can > give you access to my lab with the required hardware. > > As for the representation in the hierarchy tree, I'll jump into the > discussion next week when I'm back from traveling. Hi Martin, it's great to hear that there is more people eager to develop this functionality. If there is a need, I can also ask in our company to share with you a bare-metal with QLogic FC HBA 2600 series card. Regards, Tomasz Charoński
Attachment:
smime.p7s
Description: Kryptograficzna sygnatura S/MIME
