Re: HP announces new Integrity Blade Servers - OpenVMS?
- From: Dave Froble <davef@xxxxxxxxxxxxx>
- Date: Fri, 16 Dec 2005 00:20:59 -0500
Main, Kerry wrote:
-----Original Message-----
From: JF Mezei [mailto:jfmezei.spamnot@xxxxxxxxxxxx] Sent: December 15, 2005 4:02 PM
To: Info-VAX@xxxxxxxxxxxx
Subject: Re: HP announces new Integrity Blade Servers - OpenVMS?
Re Blade servers.
Don't blade servers require special drivers on Windows so it can use the
special high speed interconnect between machines ?
If that is the case, then VMS would also need to use special drivers to
allow clustering via that (new to VMS) interface. And that means some
VMS version in the future.
Note that at the time HP announced this (a number of weeks ago), HP made
a point that IA64 units could be mixed with 8086 based units in the same
blade cabinet. So when people upgrade from IA64 to 8086, they can retain
their blade infrastructure.
And while, from a disaster recovery point of view, blades aren't useful,
they are useful for 7/24 operation since a cluster of VMS instances does
allow you to make software upgrades on one node while other nodes keep
on servicing users. (and then reboot each node to use the new software).
Re: blades .. From a purely speculative view :-)
- Think of a rack full of blades (e.g. 100) and how many system disk it takes. [hint, at least 1 local disk for each blade with Windows and Linux and most other UNIX's. Some OS's require local disks (esp for clusters) as they do not yet support full booting over SAN] Think about the effort to keep all of these systems in sync [hint tools need to autocopy stuff all over the place. Each disk is a separate OS upgrade]
With OpenVMS cluster this would be one system disk on the SAN for the entire rack (well, two if you wanted higher availability with rolling upgrades). Of course by one, I mean one HW partition on SAN. With OpenVMS, common files are updated once and change is immediately available to all systems because it's the same file.
- Think about how a rack of blades would access common storage with Windows/Linux. [hint - network access]
With OpenVMS cluster on blades, each blade would do direct IO via shared file system and DLM.
- think about how you would balance the batch jobs with rack full of blades. [hint - tough to do with Windows and Linux as there base batch capabilities on one system is limited, never mind balancing batch workloads across multiple systems]
With OpenVMS cluster, submitting jobs to generic queue would then result
in job being executed on blade with most available cycles.
Thinking about the above, perhaps HPTC, movies on demand, digital theatres etc might be something to think about ..
I guess my only question is, which of the above cannot be done on the platforms VMS currently runs on?
-- David Froble Tel: 724-529-0450 Dave Froble Enterprises, Inc. Fax: 724-529-0596 DFE Ultralights, Inc. E-Mail: davef@xxxxxxxxxxxxx 170 Grimplin Road Vanderbilt, PA 15486 .
- Follow-Ups:
- Re: HP announces new Integrity Blade Servers - OpenVMS?
- From: Larry Kilgallen
- Re: HP announces new Integrity Blade Servers - OpenVMS?
- References:
- RE: HP announces new Integrity Blade Servers - OpenVMS?
- From: Main, Kerry
- RE: HP announces new Integrity Blade Servers - OpenVMS?
- Prev by Date: RE: HP announces new Integrity Blade Servers - OpenVMS?
- Next by Date: Re: SRM memtest
- Previous by thread: Re: HP announces new Integrity Blade Servers - OpenVMS?
- Next by thread: Re: HP announces new Integrity Blade Servers - OpenVMS?
- Index(es):
Relevant Pages
|