From: White, Cliff <cliff.white@intel.com>
To: lustre-devel@lists.lustre.org
Subject: [Lustre-devel] Lustre 2.4 Release
Date: Thu, 20 Jun 2013 21:15:25 +0000 [thread overview]
Message-ID: <CDE8BE97.5D32%cliff.white@intel.com> (raw)
In-Reply-To: <CALuPYL1WgGcY=8uikyCsa_Tp5GNqqj0+EysJ3r8baMGLsCL9iA@mail.gmail.com>
From: Indivar Nair <indivar.nair at techterra.in<mailto:indivar.nair@techterra.in>>
Date: Thursday, June 20, 2013 10:38 AM
To: "Dilger, Andreas" <andreas.dilger at intel.com<mailto:andreas.dilger@intel.com>>
Cc: "lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>" <lustre-devel at lists.lustre.org<mailto:lustre-devel@lists.lustre.org>>
Subject: Re: [Lustre-devel] Lustre 2.4 Release
Ok. The diagram seems to suggest that 2.4.0 would be first maintenance release.
Anyways...
So I will be able to make an inplace upgrade from 2.4.0 to 2.4.1 when it is released.
i.e. no re-installation of OS or reformatting OSTs when I move to 2.4.1.
Just upgrading the Lustre Kernel and Lustre Packages to 2.4.1 should do. right?
Yes, that is the meaning of a maintenance release. Any upgrade from Lustre X.Y.N to X.Y.N+1 will not require re-formatting.
However, we track vendor kernel bug fixes in our kernels, so a maintenance release will require a kernel change, but should not impact the OS install otherwise.
Cliffw
Regards,
Indivar Nair
On Thu, Jun 20, 2013 at 9:54 PM, Dilger, Andreas <andreas.dilger at intel.com<mailto:andreas.dilger@intel.com>> wrote:
On 2013/20/06 6:21 AM, "Indivar Nair" <indivar.nair at techterra.in<mailto:indivar.nair@techterra.in>> wrote:
>Hi ...,
>
>
>Lustre 2.4 was supposed to be released as a "Maintenance Release' -
>
> https://wiki.hpdd.intel.com/display/PUB/Community+Lustre+Roadmap
>
>so how come it has been released as a 'Feature Release'?
>
> https://wiki.hpdd.intel.com/display/PUB/Lustre+Releases
>
>
>Will it be moved to 'Maintenance Release' later?
The 2.4.0 release is one of the 6-month feature releases.
2.4.1 will be the first maintenance release on that branch.
Cheers, Andreas
--
Andreas Dilger
Lustre Software Architect
Intel High Performance Data Division
next prev parent reply other threads:[~2013-06-20 21:15 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-20 12:21 [Lustre-devel] Lustre 2.4 Release Indivar Nair
2013-06-20 12:29 ` Jones, Peter A
2013-06-21 17:10 ` Indivar Nair
2013-06-21 20:20 ` Jones, Peter A
2013-06-20 16:24 ` Dilger, Andreas
2013-06-20 17:38 ` Indivar Nair
2013-06-20 21:15 ` White, Cliff [this message]
2013-06-20 21:19 ` Jones, Peter A
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=CDE8BE97.5D32%cliff.white@intel.com \
--to=cliff.white@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.