[ANNOUNCE]: SCST 3.1 pre-release freeze
From: Vladislav Bolkhovitin
Date: Fri Nov 06 2015 - 01:49:25 EST
Hi All,
I'm glad to announce SCST 3.1 pre-release code freeze in the SCST SVN branch 3.0.x.
You can get it by command:
$ svn co https://scst.svn.sourceforge.net/svnroot/scst/branches/3.1.x
It is going to be released after few weeks of testing, if no significant issues found.
Highlights for this release:
- Cluster support for SCSI reservations. This feature is essential for initiator-side
clustering approaches based on persistent reservations, e.g. the quorum disk
implementation in Windows Clustering.
- Full support for VAAI or vStorage API for Array Integration: Extended Copy command
support has been added as well as performance of WRITE SAME and of Atomic Test & Set,
also known as COMPARE AND WRITE, has been improved.
- T10-PI support has been added.
- ALUA support has been improved: explicit ALUA (SET TARGET PORT GROUPS command) has
been added and DRBD compatibility has been improved.
- SCST events user space infrastructure has been added, so now SCST can notify a user
space agent about important internal and fabric events.
- QLogic target driver has been significantly improved.
SCST is alternative SCSI target stack for Linux. SCST allows creation of sophisticated
storage devices, which can provide advanced functionality, like replication, thin
provisioning, deduplication, high availability, automatic backup, etc. Majority of
recently developed SAN appliances, especially higher end ones, are SCST based. It might
well be that your favorite storage appliance running SCST in the firmware.
More info about SCST and its modules you can find on: http://scst.sourceforge.net
Thanks to all who made it happen, especially to SanDisk for the great support! All
above highlights development was supported by SanDisk.
Vlad
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/