Downloads

The Linux SCSI Target Wiki

You do not have permission to edit this page, for the following reasons:

• The action you have requested is limited to users in the group: Administrators.
• This page has been locked to prevent editing.

You can view and copy the source of this page:

The '''Downloads''' page contains the instructions for all free download repositories. == Linux inclusion == Versions of {{T}} and ''targetcli'' are included in most Linux distributions per default. Here is an overview over the most popular distributions: {{Linux Inclusion}} == {{anchor|targetcli|cli}} [[targetcli]] == === Overview === ''[[targetcli]]'' is the general management platform for {{T}}. It comprises a shell that uses the {{Target}} library through a well-defined API, and is available under the {{Apache 2}}. Everyone is welcome to [[Contributing|contribute]]. ''targetcli'' was released on {{RTS releases|RTSadmin|initial_date}}, and supports all fabric modules, including [[FCoE]], [[Fibre Channel]], [[IBM vSCSI]], [[iSCSI]], [[iSER]], [[SRP]], [[tcm_loop]], and [[vHost]]. It is is based on a modular, extensible architecture, with plug-in modules for additional functionality. ''targetcli'' consists of three Python modules ([[targetcli#Download|download and build]] instructions): * the ''targetcli'' user shell itself ({{RTS releases|RTSadmin|module_cli}}) * the underlying ''rtslib'' ({{RTS releases|RTSadmin|module_lib}}) and API {{Lib Ref Guide HTML}}{{Lib Ref Guide PDF}} * the ''configshell'' that provides extensibility ({{RTS releases|RTSadmin|module_cfg}}) === Installation === If your Linux distribution doesn't already contain an adequate ''targetcli'' version, or ''targetcli'' can't be installed as described above, you can manually install it from the {{RTS short}} repositories as follows. ==== Clone GIT repositories ==== The source code of the three ''targetcli'' components ({{RTS releases|RTSadmin|module_cfg}}, {{RTS releases|RTSadmin|module_lib}}, {{RTS releases|RTSadmin|module_cli}}) is available for downloaded from their GIT repositories, respectively: <pre> $ git clone https://github.com/Datera/configshell.git $ git clone https://github.com/Datera/rtslib.git $ git clone https://github.com/Datera/targetcli.git </pre> ==== Install and Build ==== Please follow the distribution-specific instructions: * [[CentOS]] * [[Debian]] * [[Fedora]] * [[openSUSE]] * [[RHEL]] * [[Scientific Linux]] * [[SLES]] * [[Ubuntu]] ==== Run ==== Run ''targetcli'' as 'root' as follows: <pre> # PYTHONPATH=. ./scripts/targetcli </pre> == {{anchor|Target|LIO|4|4.0}} {{Target}} == === Overview === [http://git.kernel.org/?p=linux/kernel/git/nab/target-pending.git target-pending.git (v4.1.0-rcX)] is for kernel developers and users who want to use the latest {{T}} code before it becomes available in the mainline [http://www.linux.com/ Linux] [http://www.kernel.org/ Kernel]. This tree tracks Linus' [http://git.kernel.org/?p=linux/kernel/git/torvalds/linux.git mainline] and follows the quarterly kernel release schedule. It is intended for kernel developers who are interested in contributing to the upstream {{T}} code, and are comfortable running and debugging bleeding edge kernel code. It involves building a complete running Linux kernel and associated modules, and expects the user to have experience with configuring, building and installing kernels. {{Ambox| type=warning| head=''lio-core.git'' is deprecated.| text=The ''lio-core.git'' development tree has been deprecated as of June 2012.}} Starting with 3.5-rc code in June 2012, the target-pending.git tree is now setup using a [http://permalink.gmane.org/gmane.linux.scsi.target.devel/1974 work-flow] similar to [http://www.linux-kvm.org/page/Kvm-Git-Workflow Kvm-Git-Workflow] using the following branch structure: * '''master''': contains latest target rc-fixes for the current release * '''for-next''': contains developmental patches for next merge window * '''for-next-merge''': contains new fabric drivers for next merge window * '''queue''': contains untested patches (usually) headed into for-next* * '''auto-next''': combination of current master + for-next* (rebased often) If you're a developer, usually developing against 'for-next' is okay. If 'for-next' is unstable for you or you need a new upstream API, work against 'auto-next', but let the maintainers know that when posting your patch. If you're working on a fix for the current cycle, work against upstream or 'master' (they should be equivalent most of the time). If you're a sub-maintainer, post ''git'' pull requests against 'for-next' or 'master', according to your merge target. {{Ambox| type=note| head=Backports| text=[[Datera]] offers stable qual'd backport trees for sale for most older Linux kernels and for most Linux distributions.}} {{Ambox| type=info| head=SCSI test suite| text={{RTS releases|RTSadmin|module_test}} provides a complementary open-source SCSI test suite.}} === Installation === ==== Clone GIT repositories ==== The source code of the {{Target}} ({{RTS releases|LIO|module_repo}}) engine is available for download from its kernel.org GIT repository. First, close the full git tree: <pre> $ git clone git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git target-pending.git </pre> Show the available remote branches: <pre> $ cd target-pending.git/ $ git branch -vr </pre> ==== Resolve dependencies ==== Install the necessary kernel development packages, including ''gcc'', ''make'', ''libncurses-dev''. ===== Debian ===== On a Debian based system these packages ([http://packages.debian.org/sid/gcc gcc], [http://packages.debian.org/sid/make make], [http://packages.debian.org/sid/libncurses5-dev libncurses5-dev]) can be installed as follows: <pre> $ su -c 'apt-get install gcc make libncurses5-dev kernel-devel' </pre> ===== RHEL/CentOS/Fedora ===== <pre> $ su -c 'yum install gcc make ncurses-devel kernel-devel' </pre> ===== SLES/openSUSE ===== <pre> $ su -c 'zypper install gcc make ncurses-devel kernel-devel' </pre> ===== Ubuntu ===== <pre> $ su -c 'apt-get install gcc make ncurses-devel kernel-devel' </pre> ==== Select modules ==== To configure the kernel build (hardware dependent), run: <pre> $ make menuconfig </pre> ===== {{Target}} ===== Enable the {{T}} ({{RTS releases|LIO|module_repo}}) module and the desired backend driver modules. Also, enable the desired fabric drivers for [[iSCSI]] ({{RTS releases|iSCSI|module_repo}}), [[FCoE]] ({{RTS releases|FCoE|module_repo}}), [[tcm_loop]] ({{RTS releases|tcm_loop|module_repo}}), and Firewire SBP-2: <pre> Device Drivers ---> <M> Generic Target Core Mod (TCM) and ConfigFS Infrastructure ---> --- Generic Target Core Mod (TCM) and ConfigFS Infrastructure <M> TCM/IBLOCK Subsystem Plugin for Linux/BLOCK <M> TCM/FILEIO Subsystem Plugin for Linux/VFS <M> TCM/pSCSI Subsystem Plugin for Linux/SCSI <M> TCM Virtual SAS target and Linux/SCSI LDD fabric loopback module <M> TCM_FC fabric Plugin <M> Linux-iSCSI.org iSCSI Target Mode Stack <M> FireWire SBP-2 fabric module </pre> ===== Mellanox InfiniBand ===== Optionally, enable the [[InfiniBand]] target module ({{RTS releases|SRP-Mellanox|module_repo}}), plus the ''umad'' and ''verbs'' modules: <pre> Device Drivers ---> <M> InfiniBand support ---> --- InfiniBand support <M> InfiniBand userspace MAD support <M> InfiniBand userspace access (verbs and CM) <M> InfiniBand SCSI RDMA Protocol target support </pre> ===== QLogic Fibre Channel ===== Optionally, enable the QLogic [[Fibre Channel]] target module ({{RTS releases|FC-QLogic|module_repo}}), including its SCSI LLD: <pre> Device Drivers ---> SCSI device support ---> [*] SCSI low-level drivers ---> --- SCSI low-level drivers <M> QLogic QLA2XXX Fibre Channel Support <M> TCM_QLA2XXX fabric module for Qlogic 2xxx series target mode HBAs </pre> ===== USB Gadget ===== Optionally, enable the USB Gadget module: <pre> Device Drivers ---> [*] USB support ---> <M> USB Gadget Support ---> --- USB Gadget Support <M> USB Gadget Target Fabric Module </pre> ==== Build ==== Build the Linux kernel with the selected modules: <pre> $ make bzImage ; make modules </pre> ==== Install ==== Install the Linux kernel with the selected modules: <pre> $ su -c 'make modules_install ; make install' </pre> ==== Rebuild initrd ==== If necessary, back up and rebuild the initial RAM disk ''initrd'' depending on the distribution. ===== Debian ===== Rebuild ''initrd'' by running the following command: <pre> $ su -c 'update-initrd -c -k $(uname -r)' </pre> ===== RHEL/CentOS/Fedora ===== Rebuild ''initrd'' by running the following command: <pre> $ su -c 'mkinitrd -f /boot/initramfs-$(uname -r).img $(uname -r)' </pre> ===== SLES/OpenSUSE ===== Rebuild ''initrd'' by running the following command: <pre> $ su -c 'mkinitrd' </pre> ===== Ubuntu ===== Rebuild ''initrd'' by running the following command: <pre> $ su -c 'update-initramfs -c -k $(uname -r)' </pre> == Contact == Please post your comments, questions or bug reports here: * For {{T}} or ''[[targetcli]]'': the [http://www.spinics.net/lists/target-devel/ target-devel] mailing list ([mailto:target-devel@vger.kernel.org post], [mailto:majordomo@vger.kernel.org&body=subscribe%20target-devel subscribe], [http://vger.kernel.org/vger-lists.html#target-devel list info], [http://dir.gmane.org/gmane.linux.scsi.target.devel gmane archive]) * For the [[Initiator]]: the [http://groups.google.com/group/Core-iSCSI Core-iSCSI] mailing list * For general SCSI: the [http://marc.info/?l=linux-scsi&r=1&w=2 linux-scsi] mailing list * For the Linux kernel: the [http://lkml.org/ Linux Kernel mailing list] ([http://marc.info/?l=linux-kernel&r=1&w=2 archive]) Please see [[Support]] for more information. == See also == * {{Target}}, [[targetcli]] * [[{{OS}}]] * [[Support]] == External links == * {{Official|http://www.daterainc.com/}} [[Category:Support]]

Return to Downloads.