[Info-vax] HP SAN switch question
Kerry Main
kerry.main at backtothefutureit.com
Thu Feb 18 12:51:15 EST 2016
> -----Original Message-----
> From: Info-vax [mailto:info-vax-bounces at info-vax.com] On Behalf Of
> Stephen Hoffman via Info-vax
> Sent: 18-Feb-16 12:04 PM
> To: info-vax at info-vax.com
> Cc: Stephen Hoffman <seaohveh at hoffmanlabs.invalid>
> Subject: Re: [New Info-vax] HP SAN switch question
>
> On 2016-02-18 16:31:15 +0000, Kerry Main said:
>
> > Imho, once OpenVMS is available on ProLiants, HPE will become more
> > interested in OpenVMS as HPE will not care what OS is running as long
> > as it has ProLiant on the front of the server.
> >
>
> IMHO, server commoditization will continue, and HPE will become
> another
> server vendor competing for generic server hardware sales.
>
> HPE might deign to perform or fund the testing of specific models of
> ProLiant with OpenVMS (analogous to what happened with Solaris and
> Linux distros and the associated testing), though OpenVMS will be
> little more than a rounding error in the HPE server and storage sales.
> Other vendors and quite possibly some hosting providers may or will do
> some qualification, too. I'd be surprised if Nemonix didn't get into
> this business.
>
VSI might decide to adopt a similar strategy as Microsoft when MS had
their certified hardware list i.e. here is a list of hardware that has been
tested and is now fully supported. All other server HW should work, but
if it doesn't, then it falls under the umbrella of "best effort".
This cert'ed list could initially be a mix of popular tier 1 HP & Dell rack,
blade and standalone systems.
That is the trade-off Customers will make between getting certified
systems vs. cheaper no name equivalent server products.
To your point, VSI might also engage another vendor to assist in adding
to the VSI certified list.
VSI might also devise a process for compatibility /stress testing in order
to get support. This might allow the Tier2 vendors to do their own cert
testing (thinking of things like modified UETP testing perhaps?)
From a support perspective, they could also adopt a financial model which
provides Incentives to using standard systems - similar to what outsourcers
provide to their Customers. Basically, if you are using a standard system, the
monthly support charge per OS instance is $1,000. If you are using a non-std
system that has passed the tier 2 compatibility testing, then the monthly
charge per OS instance is $2,500 (using fictitious numbers).
> I've seen HPE recommending with and assisting with various application
> ports off of OpenVMS and over on ProLiant, and then the replacement
> generation deploys on SuperMicro, Dell or some other vendor. Several
> of the customers involved were (separately) marveling at how HPE was
> assisting their own customers over to a platform that they'd inevitably
> lose control of. (But that's what short-term requirements and
> conflicting sales goals and multiple cost centers tends to produce,
> too.)
>
When a company gets too big, it's not just multiple CC's, it essentially
becomes different companies. It gets worse when the corporate types
adopt a ERP system like SAP which typically allows very little flexibility
to deal with customers that want custom solutions - things that require
capabilities like revenue sharing between BU's and/or depts.
> This all assuming that VSI doesn't go to OpenVMS-specific x86-64
> servers, and that can also run Windows or Linux x86-64. Possibly in
> conjunction with Nemonix and/or with other corporate partners. There
> is precedent for this, of course. Might also mean the end of the
> OE-like PAKs, too.
>
As Clair stated, they are looking at potential license model changes - tbd.
Regards,
Kerry Main
Kerry dot main at starkgaming dot com
More information about the Info-vax
mailing list