HP Embraces Linux for its Toughest Servers
Colmao writes "Investor's Business Daily wrote up an article interviewing Martin Fink, the head of HP's NonStop Unit. From the article'In a move that suggests Linux is finally ready for prime time, Hewlett-Packard is giving the free software a bigger role on some of its toughest servers.' NonStop servers are HP's most costly machines. They are designed to be always on, mission critical appliances. They are used to run some of the world's stock markets. Linux is making big moves in the datacenter and getting some much needed exposure."
I would be very apprehensive about trying to graft the NonStop technology into the Linx kernel. Running Linux as a process under Guardian, just like IBM runs Linux under VM, makes a lot more sense.
-jcr
The only title of honor that a tyrant can grant is "Enemy of the State."
Further, IBM has spent enormous sums of money to ensure that Linux is reliable. IBM will soon discover that this aspect of Linux is the Achille's heel of open source. By using Linux, HP essentially gets a free ride from IBM and need not spend the money to ensure that Linux is reliable. IBM has already done the work.
I can already hear the grinding of the reduction-in-force axe at the OS department of HP.
Thanks for the correct link.
Having found the correct article, I'll be interested to see if this ever sees the light of day. I did spend a bit of time working on Tandem Non-Stop systems (since acquired by Compaq, and hence, by HP).
Working on Tandems was kind of like visiting another planet and seeing how an alien race might do operating systems. Hardware-wise, everything is redundant - from the CPUs, to the power supplies, to the system bus. Supposedly, a failure in any one component couldn't bring the system down. Everything was designed to survive a failure. Creating a fault tolerant system was supposed to be easy - except that all the software had to be designed to respond appropriately to a failure event.
The system could definitely use an upgrade using Linux. It was limited to eight character file names (no filename extensions) and you could use directories and subdirectories - only. There was no such thing as a subdirectory of a subdirectory. Just two levels.
The operating system was built around a messaging system that was fast enough for ATM transactions, but was useless for batch type data crunching operations (unfortunate, since somebody at this shop had selected it to do exactly that task.)
If they're thinking about this on the same lines as the original vision of the NonStop operating system, the version of Linux that comes of this will be completely non-applicable to any hardware but HP's. Everything will need to be rewritten/tweaked. Starting with Linux will help their other deficiencies, but will result in a really weird Linux derivative.
But in the end, IMHO, the whole concept is flawed because, while interesting, it only addressed component failure and not disasters such as fires or tornados, etc. At the same time I was working on this system, I read a story about a mass transit system in Denmark automatically (and successfully) failing over to another system in another city as a result of a fire. That seemed far more robust. And those systems were running OpenVMS.
These are systems that are really pretty cool. And really freaking expensive.
They have nothing to do with HP-UX or Unix of any kind. They are Tadem machines (feel free to look that up).
These are rather slow but super reliable machines with a bizzare OS that has had features for decades that mainstream os's still don't have. Take the current clustering and grid tech and meld it all together and you get something like the tandem. The company I work for came out of the tandem space. The typical intro to the machines for new hires is to note that you can smash one with a sledge hammer and you won't lose any transactions.
Who uses these things? Banks, Banks, Banks, Airlines, Governement, Dell, etc...
They (HP) have been working on a unixy layer to run on top of the tandem os for a number of years now. Apparently this hasn't been going too well. Sounds like Linux might help them do something similar to IBM and the VMs on the mainframe.
Later in S-series servers, the System got renamed to NonStop, the kernel got renamed to Guardian.
About loosing CPU,Memory/System Bus you are not even scratching the surface....With 2 systems operating in Tandem (hence the name),, you can even loose an entire system, and the other one takes over, and these 2 systems can have 2 geographically remote systems in tandem, giving you complete fault tolerence.
These systems talk to eachother over a proprietory network stack (defi. not TCP/IP) and do health monitoring. And uptime is measured in years, not months...
for the last time people, I am "frodo from middle eaRTH", not "middle eaST".