On Sun, 2008-08-03 at 13:44 +0300, Dimitris Zilaskos wrote: > Hi, > > We are investigating the possibility of deploying lustre in our clusters. > We are using RHEL4. An important issue we are facing is support for the > latest errata kernels. For example at the moment it is possible to download > lustre-patched 2.6.9-67.0.7 kernel, while the latest errata is 2.6.9-78.
We strive to maintain currency with vendor errata kernels but a couple of factors impede us in being as timely as I'm sure you wish we would be. The first is that we don't get an errata kernel any quicker than you do. RH for example don't make any early releases for anyone, so we can only start integration and testing when the kernel is released to the general public. This process can take a couple of weeks for us to do a full QA array of testing, which I'm sure you can appreciate the result of -- knowing that any given release has been through our rigorous testing in order to minimize as much as we can the unfortunate event of upgrade failures. The second impediment is timing. Sometimes an errata kernel is released too late to make it for the feature freeze for an upcoming release even though that release could be a couple of weeks (remember, QA) away. This gives the appearance that we take a long time to get an errata release out since it won't come out now until our next regularly scheduled release. Sometimes we will do a point release for nothing else than to support a very important errata kernel but that doesn't happen entirely often. b.
signature.asc
Description: This is a digitally signed message part
_______________________________________________ Lustre-discuss mailing list [email protected] http://lists.lustre.org/mailman/listinfo/lustre-discuss
