[prev in list] [next in list] [prev in thread] [next in thread] 

List:       lustre-discuss
Subject:    Re: [lustre-discuss] Building RPMs for 2.5.3 on CentOS-7.2
From:       Patrick Farrell <paf () cray ! com>
Date:       2016-06-05 15:57:08
Message-ID: BY2PR1101MB1144AB5CC8BF61501757544BCB5B0 () BY2PR1101MB1144 ! namprd11 ! prod ! outlook ! com
[Download RAW message or body]


Server-wise, if you do not want any of the new features in 2.6-2.8, then you are \
probably best served with sticking with 2.5 for the time being.  (There's some good \
stuff in there...  But there's also the chance of your workload hitting new bugs as \
well.)  There are no compatibility problems between 2.5 servers and 2.8 clients - \
Just features you don't get.

So, for clients, probably 2.8, since you can't use 2.5 with CentOS 7.2.  2.8 should \
be a bit better than 2.7 (and neither is seeing public post-release patching).

- Patrick
________________________________________
From: Jon Tegner <tegner@foi.se>
Sent: Sunday, June 5, 2016 10:01:25 AM
To: Patrick Farrell; lustre-discuss@lists.lustre.org
Subject: Re: [lustre-discuss] Building RPMs for 2.5.3 on CentOS-7.2

Thanks a lot!

Did found the "--disable-server" and that seemed to work (sort of),
however, had other issues when building the (client) rpms.

Do you have any general advice considering that we want CentOS-7.2 on
the clients? We have happily been using 2.5.3 for quite some time now
(6.5 on both servers and clients), and we would like to see similar
stability on our updated system (that is, with 7.2 on the clients). What
would be my best/safest bet under these circumstances?

I actually tried a client on 2.8.0 using our old servers (6.5/2.5.3) -
and initial (very limited) tests seemed to indicate that this was OK. Is
this something one should generally stay away from? Or would it be
better to use 2.8.0 on the servers also, if that is what is used on the
clients?

Thanks again,
/jon


On 06/05/2016 03:26 PM, Patrick Farrell wrote:
> Do you need the server code?  If not, you can do --disable-server (I think) and \
> skip the kernel patching steps.  If no, you're out of luck - the public 2.5 code is \
> not going to build against 7.2. 
> In fact, you may have some issues even just building the client.  But those may be \
> surmountable, I'd say the server issues are not.

_______________________________________________
lustre-discuss mailing list
lustre-discuss@lists.lustre.org
http://lists.lustre.org/listinfo.cgi/lustre-discuss-lustre.org


[prev in list] [next in list] [prev in thread] [next in thread]