Subject: New Kernel on new YDL 2.0 CD
From: Brian Waite (bwaite@cspi.com)
Date: Thu Jun 28 2001 - 07:49:24 MDT
Does anyone else find this very discomforting? As a company reselling YDL to our customers as part of a cluster this poses a huge problem. The way it should work is that we validate a release that is "supported" ie YDL 2.0. Once our release is complete another group takes over and installs clusters based on our "blessed" software. If YDL 2.0 has 10 kernel upgrades then I have to re-validate each and every distro I get in house. Not to mention I now have to recomplie 3rd party drivers and revalidate+rerelease my software. On top of this there was no mention anywhere of this occurring. I really don't want to be involved in each cluster shipment to make sure all builds and is happy. I would really like this type of upgrade to be handled in either an upgrade, CS 2.1, or a big note about what you are missing. The things about releases is not to have a perfect release, but to have a release that stays stable so every cluster shipped behaves the same out of the factory. Our customer support staff can then test incremental updates on a per customer/installation basis and reccommend updates to other customers, if warranted.
This lastest upgrade is a perfect example, this kernel fixes an issue with iBooks. I am not affected by this, but because it is a new kernel rev I need to re-start all of the release testing from scratch. This is a real pain.
Just my .00000002 cents
Brian Waite
Looking for a TeraFLOP in a closet?
www.fastcluster.com
This archive was generated by hypermail 2a24 : Thu Jun 28 2001 - 07:00:31 MDT