Hi Cliff,
Cliff White wrote:
Nick Jennings | CMD Technical Director wrote:
I forgot to add to that by asking about updating Lustre itself. My
tendency would be to leave well enough alone and attempt an upgrade of
Lustre on a production system unless absolutely necessary. However, I
then worry about falling behind and being left without a supported
upgrade path. Any advice on this as well?
First, Lustre is mostly kernel-stuff - most other upgrades shouldn't
impact it. Of course we prefer that Lustre servers are dedicated to
Lustre, which makes things simplier.
We also prefer you keep Lustre up to date, since we do fix bugs and
stuff. Upgrades of minor version release should be fairly painless, and
good for bug fixes.
We do attempt to release updates when the distros release a new kernel,
especially when there are security-related kernel updates.
Thanks, that's pretty much what I assumed but I just wanted to ask to be
sure. Basically if I just lock down the kernel packages from being
automatically updated I think I'll be fine.
Thanks,
Nick
Nick Jennings | CMD Technical Director wrote:
Hi all,
I was wondering what kind of precautions should be taken during a
system update on a RHEL5 Lustre machine (regardless of it being a
client node, oss, or mds) ?
I'd like to maintain an up-to-date system, with all the latest
security patches, etc. but I worry about automating this task and
breaking lustre somehow. Are there any tips to avoid possible issues
down the line?
begin:vcard
fn:Nick Jennings
n:Jennings;Nick
org:Creative Motion Design
email;internet:[email protected]
title:Technical Director
x-mozilla-html:FALSE
url:www.creativemotiondesign.com
version:2.1
end:vcard
_______________________________________________
Lustre-discuss mailing list
[email protected]
http://lists.lustre.org/mailman/listinfo/lustre-discuss
