Downloads

The Linux SCSI Target Wiki

(Difference between revisions)
Jump to: navigation, search
({{anchor|4|4.0}} LIO 4 (released Linux tip-of-tree kernels))
m ({{anchor|4|4.0}} LIO 4 (released Linux tip-of-tree kernels))
Line 39: Line 39:
'master', according to your merge target.
'master', according to your merge target.
-
Here are some brief instructions for checking out the tree:
+
Also from this point onwards, the old development tree (lio-core.git)
 +
should be considered deprecated.
 +
 
 +
Here are some brief [http://www.git-scm.com Git] instructions for checking out the tree:
<pre>
<pre>

Revision as of 19:40, 4 July 2012

The Downloads page contains the references to all free download repositories.

Contents

RTS OS

RTS OS provides a comprehensive, integrated single-node storage operating system based on LIO. RTS OS comes in form of an ISO that can be booted natively and/or in virtual machines (KVM, VMware ESX, etc.).

targetcli

targetcli is the general management platform for LIO. It is available under dual licensing:

targetcli was initially released in May 2011, and it supports all fabric modules, currently including iSCSI, Fibre Channel, FCoE, InfiniBand, IBM vSCSI and tcm_loop, see also Target. It is is based on a modular, extensible architecture, with plug-in modules for additional functionality.

LIO 4 (released Linux tip-of-tree kernels)

target-pending.git (v4.1.0-rcX) is for kernel developers + users who want to use the latest target code. This tree includes the core Target engine v4.x and fabric driver logic.

This tree tracks the Linux kernel tree and follows the upstream linux kernel release schedule. It for kernel developers who are interested in contributing to the upstream LIO 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.

Starting with 3.5-rc code in June 2012, the target-pending.git tree is now setup using a work-flow similar to Kvm-Git-Workflow using the following branch structure:

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 submaintainer, post git pull requests against 'for-next' or 'master', according to your merge target.

Also from this point onwards, the old development tree (lio-core.git) should be considered deprecated.

Here are some brief Git instructions for checking out the tree:

# Clone the full git tree
git clone git://git.kernel.org/pub/scm/linux/kernel/git/nab/target-pending.git target-pending.git
# Change dir
cd target-pending.git/
# Show available remote branches
git branch -vr

LIO 3 backports (Linux kernels ≥2.6.18)

lio-core-backports.git is for users who are interested in running LIO kernel code on a existing unmodified kernel environment, and therefore need "out-of-tree" Linux sources (available from Datera, Inc.).

This tree allows building the LIO kernel modules and packages on many popular distributions, and any kernel back to v2.6.18. It includes Target+iSCSI v3.1, and the Backports HOWTO on installing, configuring and building backport targets for older trees.

There are two key parts to it:

The Backports HOWTO describes how to build, install and run LIO 3 and its tools.

See also

External links

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Google AdSense