No, for server, it's CentOS 6 for everything earlier than current development branches (which will become 2.8.0).
For client, it can be built for nearly any linux kernel from 2.6.32 vintage up to somewhere around 3.16. (Someone else will know the exact latest.)
If you'd like stability, 2.5 is your best bet as it was the last maintenance release (pull the 2.5 branch, I believe it saw patches committed after the last tagged release, 2.5.3). If you're going features, there's no reason to pick 2.6 instead of 2.7,
so just go with 2.7. As for a compromise... That's a hard thing to judge. My ideal combination, personally, would be 2.7 clients and 2.5 servers, as the largest recent improvements have been to clients.
We should really get some wiki pages written for these questions...
- Patrick
From: Sean Caron [scaron@umich.edu]
Sent: Friday, June 05, 2015 3:46 PM
To: Chris Horn; Sean Caron
Cc: Patrick Farrell; hpdd-discuss@lists.01.org
Subject: Re: [HPDD-discuss] Performing "make rpms" on current Git pull fails with "error: line 144: Version required: Requires: kernel ="
Thanks, guys, just talked to Brock on the phone and he clued me in a little bit. I will retry with a slightly backed up version, 2.7.0 straight and see how that goes.
Just wanted to confirm -- Brock wasn't sure -- both client and server are intended to run on RHEL/CentOS 7? Looking at the release, it gives me the feeling; and it patches and compiles clean which is a strong indicator; just trying to not do anything totally
nuts here.
I hate to take this particular thread too far off topic but can you guys provide any guidance on what would make a good compromise between features and stability in terms of the Lustre release? This is mostly experimental for now but will eventually lead
to kind of a "pilot" deployment ... I don't want to roll out something that's essentially obsolete as soon as it hits pilot and would require an immediate update, but I don't want something too unstable for real work, either.
Thanks!
Sean