Lustre discuss - Apr 2009 - RHEL5 Lustre system updating precautions

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?

-- 
Nick Jennings
Technical Director
Creative Motion Design
www.creativemotiondesign.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nick.vcf
Type: text/x-vcard
Size: 219 bytes
Desc: not available
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20090402/7b32af04/attachment.vcf

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?

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?
> 
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss
-- 
Nick Jennings
Technical Director
Creative Motion Design
www.creativemotiondesign.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nick.vcf
Type: text/x-vcard
Size: 219 bytes
Desc: not available
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20090402/e0747c40/attachment.vcf

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.
cliffw
> 
> 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?
>>
>> _______________________________________________
>> Lustre-discuss mailing list
>> Lustre-discuss at lists.lustre.org
>> http://lists.lustre.org/mailman/listinfo/lustre-discuss
> 
> _______________________________________________
> Lustre-discuss mailing list
> Lustre-discuss at lists.lustre.org
> http://lists.lustre.org/mailman/listinfo/lustre-discuss

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?
>>>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: nick.vcf
Type: text/x-vcard
Size: 219 bytes
Desc: not available
Url :
http://lists.lustre.org/pipermail/lustre-discuss/attachments/20090403/a45878bb/attachment.vcf