> On Dec 25, 2017, at 11:35 AM, melek ozel <[email protected]> wrote: > > I preassume there are several tools for both initiator and target.IBLOCK is > just a storage object on target just like "backstores/block".I came across > that on one of wikipage.I am looking for some wikipage or tutorial which > throw this dust away.I came across few tutorials which explain > target/initiator setup with openiscsi.this is how I ended up over here. what > is the difference between using this "iscsi-initiator-utils" and openiscsi if > there is already target configured?
The name “iscsi-initiator-utils” is a name for a package that contains the open-iscsi initiator software. The open-iscsi iSCSI initiator software allows a system to connect to iSCSI targets, making them look like local discs, once connected. It also facilitates discovering such targets. There really aren’t any other Linux OSS initiators I know about. There are several Linux iSCSI target packages, but the “good” one these days is targetcli-fb. The “fb” stands for the “free branch” of targetcli. Read there web page if you want more info about the history. :) The targetcli-fb package supplies the targetcli command. This command allows you to set up targets that open-iscsi can connect to. There is no “iblock” format in targetcli. You can use backstores/block to have targetcli use a block device for your iSCSI target backing store. Or you can use a file with backstores/fileio. The README.md that comes with targetcli-fb has a pretty good bare-bones tutorial on setting up each. > > On Fri, Dec 22, 2017 at 4:13 AM, The Lee-Man <[email protected] > <mailto:[email protected]>> wrote: > On Thursday, December 21, 2017 at 12:10:52 AM UTC-8, malteseLun wrote: > Is there a list that I can see CLIs for scsi targets? actually I cant find > openiscsi on centos 7.4. couldnot even install with yum. I am trying to > implement "IBLOCK(any block device).I cant see IBLOCK on targetcli and saw > some posts openiscsi listing IBLOCK, few howtos actually. > > > Perhaps you're getting iSCSi initiators confused with iSCSI targets? The > open-iscsi project supplies an open-source iSCSI initiator. The targetcli-fb > project (and the older targetcli project which it replaces) are an > open-source iSCSI target. > > I don't know what "CLIs for scsi targets" is. Perhaps you mean the targetcli > command, which lists all iSCSI targets (among other things). > > You shouldn't need open-iscsi if all you want to do is supply iSCSI targets. > But if you want to be able to connect to those (or any) iSCSI targets with an > initiator, then open-iscsi is useful for that. > > I don't know what "IBLOCK" is. I know that it is possible to share a zfs > volume using targetcli, if that is your goal. > -- Lee Duncan "A witty saying proves nothing." -- Voltaire -- You received this message because you are subscribed to the Google Groups "open-iscsi" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/open-iscsi. For more options, visit https://groups.google.com/d/optout.
