Yeah, thanks, I guess you're right. Thanks for everyone's help -- it's becoming clear that tgtd is just not going to work for this project. I'm used to working with Solaris's STMF iSCSI target framework, and there just aren't the same features available in tgtd. I'm looking at the targetcli stuff from LIO now, and it's able to do what I need. Thanks again. Jon Heese Systems Engineer INetU Managed Hosting P: 610.266.7441 x 261 F: 610.266.7434 www.inetu.net ** This message contains confidential information, which also may be privileged, and is intended only for the person(s) addressed above. Any unauthorized use, distribution, copying or disclosure of confidential and/or privileged information is strictly prohibited. If you have received this communication in error, please erase all copies of the message and its attachments and notify the sender immediately via reply e-mail. ** -----Original Message----- From: ronnie sahlberg [mailto:ronniesahlberg@xxxxxxxxx] Sent: Thursday, September 24, 2015 12:26 PM To: Jon Heese <jheese@xxxxxxxxx> Cc: stgt@xxxxxxxxxxxxxxx Subject: Re: Problems with targets.conf syntax On Wed, Sep 23, 2015 at 11:22 AM, Jon Heese <jheese@xxxxxxxxx> wrote: > Hello, > > I'm using tgtd 1.0.60 on CentOS 7 to provide iSCSI targets on top of Ceph RBD storage, and I'm having some trouble working out the proper targets.conf syntax to make it work how I want... > > So here's a snippet of my current targets.conf: > > <target iqn.1996-12.net.inetu.ceph-storage01> > bs-type rbd > <backing-store cmikolay-sqlcluster_mssql> > initiator-name iqn.1996-12.net.inetu:cmikolay-winlab.cslabs.inetu.net-r4zsbpwh2nfy > </backing-store> > ... > </target> > > This works on a basic level - that is, it provides an iSCSI LUN for the "cmikolay-sqlcluster_mssql" RBD device, but the "initiator-name" directive appears to be being ignored. If I switch from the container format to the inline format, i.e.: > > <target iqn.1996-12.net.inetu.ceph-storage01> > bs-type rbd > backing-store cmikolay-sqlcluster_mssql > initiator-name iqn.1996-12.net.inetu:cmikolay-winlab.cslabs.inetu.net-r4zsbpwh2nfy > ... > </target> > > Then the ACL by IQN works, but I can't add any more LUs to that target without breaking the ACL. > > What I'm looking for is a way to have a single target with multiple LUNs under it, each ACL'd to a set of IQNs. Does anyone know of a way to do this? Thanks in advance! I am not sure you can do that. Afaik the ACLs are per target level and not per LUN. So if you want different LUNs for different initiators and have ACLs to protect access you will need to use multiple targets. > > Jon Heese > Systems Engineer > INetU Managed Hosting > P: 610.266.7441 x 261 > F: 610.266.7434 > www.inetu.net > > ** This message contains confidential information, which also may be > privileged, and is intended only for the person(s) addressed above. > Any unauthorized use, distribution, copying or disclosure of > confidential and/or privileged information is strictly prohibited. If > you have received this communication in error, please erase all copies > of the message and its attachments and notify the sender immediately > via reply e-mail. ** > -- > To unsubscribe from this list: send the line "unsubscribe stgt" in the > body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at > http://vger.kernel.org/majordomo-info.html ��.n��������+%������w��{.n����� ��{ay� ʇڙ���f���h������_�(�階�ݢj"��������G����?���&��
