Link
These are three screencasts I made recently to better explain how to use targetcli to configure the Linux kernel target subsystem. Doing them uncovered a number of usability issues in targetcli, so they’ve already been of use to me, and hopefully will be of use for potential users of targetcli and LIO as well.
- Overview and backstores
- Fabrics and ISCSI
- The configuration file and Python API
I’ve also been dogfooding screencast software on RHEL 6, which works only with effort. I ended up using gtk-recordmydesktop (in EPEL) and then converting the .ogv to VP8 with oggconvert (will be getting into EPEL), before I could successfully upload to YouTube with good results.
Thanks so much for doing these!
tgtd doesn’t support write exclusive registrants only reservations. LIO made it possible for me to play with scsi fencing in Red Hat Cluster Suite, and your videos made it easy to deploy LIO.
-Trap
What can I do when I don’t have any fabric modules listed? I’m trying to use qla2xxx. I installed Kernel 3.7 with the QLogic TCM drivers.
I have created /etc/modprobe.d/qla2xxx.conf:
options qla2xxx qlini_mode=”disabled”
mkinitrd -f /boot/initramfs-$(uname -r).img $(uname -r)
reboot
cat /sys/module/qla2xxx/parameters/qlini_mode:
disabled
When I run targetcli, I don’t see any modules at startup and no modules with ls.
My saveconfig.json looks like:
{
“fabric_modules”: [],
“storage_objects”: [],
“targets”: []
}
Any ideas?
Hi Robert,
What distro and version of targetcli are you using? You should at least be seeing iscsi and loopback as possible fabrics.
Also, what do you see for /sys/class/fc_host/host*/port_name ?