Lustre-devel archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jones, Peter A <peter.a.jones@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [lustre-devel] Lustre 2.9.0 released
Date: Thu, 8 Dec 2016 04:25:57 +0000	[thread overview]
Message-ID: <D46E20D2.EB91C%peter.a.jones@intel.com> (raw)

We are pleased to announce that the Lustre 2.9.0 Release has been declared GA and is available for <https://downloads.hpdd.intel.com/public/lustre/latest-feature-release/> download<https://downloads.hpdd.intel.com/public/lustre/lustre-2.9.0/> <https://downloads.hpdd.intel.com/public/lustre/lustre-2.9.0/> . You can also grab the source from <http://git.whamcloud.com/fs/lustre-release.git/commit/ea79df5af4d9b034e39caa396cefc2a075e572ba> git<https://git.hpdd.intel.com/?p=fs/lustre-release.git;a=commit;h=4258370088ae65a7ec7886334191af6d53c73567>

This major release includes new features:

UID/GID Mapping  Provides the capability to remap user and group IDs based on node address so as to simplify administration when sharing access between security domains   (LU-3291<https://jira.hpdd.intel.com/browse/LU-3291>)
Shared Key Crypto Identifies clients/servers and authenticates/encrypts RPCs  (LU-3289<https://jira.hpdd.intel.com/browse/LU-3289>)
Subdirectory Mounts  Offers the option for clients to be able to mount only a defined subset of the filesystem (LU-29<https://jira.hpdd.intel.com/browse/LU-28>)

Server Side Advise and Hinting A Lustre equivalent of fadvise that provides hints to the server about the nature of the data access (willread, dontreed) so that appropriate steps can be taken. (LU-4931<https://jira.hpdd.intel.com/browse/LU-4931>)

Large Bulk IO Allows the configuration of larger options to be able to get more efficient network/disk IO . (LU-7990<https://jira.hpdd.intel.com/browse/LU-7990>)

Weak Updates Lustre support for weak updates (KMP) has been added. Please note the associated name changes for the RPMs . (LU-5614<https://jira.hpdd.intel.com/browse/LU-5614>)
Fuller details can be found in the 2.9 wiki page<http://wiki.lustre.org/Release_2.9.0> (including the ch<http://wiki.lustre.org/Lustre_2.9.0_Changelog>ange log<http://wiki.lustre.org/Lustre_2.9.0_Changelog> and test mat<http://wiki.lustre.org/Release_2.9.0#Test_Matrix>rix<http://wiki.lustre.org/Release_2.9.0#Test_Matrix>)
The following are known issues in the Lustre 2.9 Release:

LU-8313<https://jira.hpdd.intel.com/browse/LU-8813> ? Deployments using kerberos that have upgraded from an earlier release will need to manually add a?k flag to svcgssd in order to maintain compatibility
LU-8880<https://jira.hpdd.intel.com/browse/LU-8880> ? Kerberos does not behave in a consistent manner when deploying in a DNE configuration
These issues are being actively worked and have proposed fixes under testing and review.
Please log any issues found in the issue tracking system<https://jira.hpdd.intel.com/>
Thanks to all those who have contributed to the creation of this release.

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.lustre.org/pipermail/lustre-devel-lustre.org/attachments/20161208/e8bdb7f2/attachment.htm>

                 reply	other threads:[~2016-12-08  4:25 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=D46E20D2.EB91C%peter.a.jones@intel.com \
    --to=peter.a.jones@intel.com \
    --cc=lustre-devel@lists.lustre.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox