Main Page

The Linux SCSI Target Wiki

(Difference between revisions)
Jump to: navigation, search
m
m
Line 64: Line 64:
'''[[Target#Fabric modules|Multiprotocol target]]'''
'''[[Target#Fabric modules|Multiprotocol target]]'''
-
* [[Fibre Channel]]. [http://www.qlogic.com QLogic]: released
+
* [[Fibre Channel]] - [http://www.qlogic.com QLogic]: released
* [[Fibre Channel over Ethernet]] (FCoE): released
* [[Fibre Channel over Ethernet]] (FCoE): released
* iEEE 1394: released
* iEEE 1394: released
Line 71: Line 71:
* [[iSCSI]] (SCSI over IP): released
* [[iSCSI]] (SCSI over IP): released
* [[IBM vSCSI]] for [http://www-03.ibm.com/systems/p/ IBM System p]: RC
* [[IBM vSCSI]] for [http://www-03.ibm.com/systems/p/ IBM System p]: RC
-
* [[InfiniBand]]. [http://www.mellanox.com Mellanox]: released
+
* [[InfiniBand]] - [http://www.mellanox.com Mellanox]: released
* [[tcm_loop]] [[SCSI]] virtualization: released
* [[tcm_loop]] [[SCSI]] virtualization: released

Revision as of 07:11, 5 July 2012

Welcome to Linux-IO,
the standard Unified Target in Linux.
100 articles, 90,711,519 pageviews

Summary

LIO (Linux-IO) is the standard open-source Unified Target in Linux. It supports all prevalent storage fabrics, including iSCSI, Fibre Channel (QLogic), FCoE and InfiniBand (Mellanox SRP). LIO has replaced STGT as the standard Target with Linux kernel version 2.6.38.

The LIO Unified Target has become the Linux iSCSI target of choice for many volume storage appliance vendors, including Buffalo, Netgear, QNAP, etc., allowing them to achieve and VMware vSphere 5 certifications, including support for VAAI. LIO also includes targetcli, a management shell and API for the Unified Target, providing a single namespace for all storage objects.

LIO is developed by Datera, Inc., a SAN systems and software company located in the Silicon Valley.

Target

Architecture

Advanced SCSI feature set

  • Persistent Reservations (PRs)
  • Asymmetric Logical Unit Assignment (ALUA)
  • Protocol multiplexing, load-balancing and failover (MC/S)
  • Full Error Recovery (ERL=0,1,2)
  • Active/active task migration and session continuation (ERL=2)
  • Thin LUN provisioning (TRIM)

Multiprotocol target

Storage media independence

Compatibility and certifications

LIO is compatible to Initiators of the following operating systems:
  • Microsoft: Windows Server 2003/2008/R2 and Windows XP/Vista/7
  • Apple Mac OS X (via third-party initiator)
  • Linux: RHEL 4/5/6, SLES 10.3/11, CentOS, Debian, Fedora, openSUSE, Ubuntu
  • Unix: Solaris 10, OpenSolaris, HP-UX
  • VMs: vSphere 5 (incl. VAAI), Red Hat KVM, Microsoft Hyper-V, Oracle xVM/VirtualBox, Xen

LIO passed vSphere 5 (incl. VAAI) certifications with Buffalo and others. It also passes the Microsoft Windows Server 2008 / R2 Failover Cluster compatibility test suites.

RTS OS

The LIO Unified Target has been integrated into RTS OS, a single-node Unified Storage operating system. RTS OS fully supports VMware vSphere 5 including VAAI. Active RTS OS subscriptions provide access to additional RTS OS packages and update services.

RTS OS is currently being extended into RTS Live, a cluster storage operating system that is based on RTS Director.

Management

LIO is complemented with two management frameworks:

High availability and clustering

LIO is designed from gound up to support highly available and cluster storage:
  • Deeply embedded high availability (Network RAID1)
  • Scale-out clusters and disaster recovery solutions

Initiator

The Core-iSCSI Initiator is a high-end iSCSI Initiator that resolves a number of known issues with the Open-iSCSI standard Linux Initiator, especially its slow performance.

Core-iSCSI is available on Linux and Windows, and it has been ported to a wide range of platforms and devices, including:

Datera, Inc. ported OCFS2 onto the Nokia Internet Tablets on top of the Core-iSCSI Initiator.

RTS Director

RTS Director is a distributed, highly-available cluster management framework. It comprises a shell, active library and API. The active library and API provide an extensible platform with a unified namespace to manage complex functionality, such as high-availability and cluster striping. The shell offers location-transparent access to all objects in the SAN. New functionality and devices can be added via plugin-modules.

RTS Director provides zero configuration. It is based on a symmetrically distributed architecture - there is no single point of failure, no cluster controller, no central database, etc. Nodes running the RTS Director automatically discover and join the cluster when coming up (demo video).

See also

Personal tools
Namespaces
Variants
Actions
Navigation
Toolbox
Google AdSense