-----Original Message-----
via Info-vax
Sent: December-23-20 8:16 AM
Subject: Re: [Info-vax] WHY IS VSI REQUIRING A HYPERVISOR FOR X86
OPENVMS?
Post by Phillip Helbig (undress to reply)Post by Andrew BrehmI don't see that they are requiring a hypervisor.
But I also don't see your point. In my experience bare metal
requirements cost more money because you need to buy and
support/install extra hardware for the platform. With a hypervisor
you can just add OpenVMS instances on your existing hardware.
Assuming that you have such existing hardware. So, cheaper for those
already rich. :-|
As others have said free versions of all the major Hypervisors are
available so
I can't see what cost there is. Even for the poor it will usually save
money.
If you already have a server that is not fully loaded and enough capacity
to
run VMS you can virtualize the exiting OS image and add VMS.
There are free tools to let you do this.
If you need to buy a new server, well I can't believe any one is going to
max
out even the cheapest modern server running VMS. So if you have to buy a
new server using a Hypervisor allows you to utilize the spare capacity.
You can run another OS or two instances of VMS so you have a test
environment.
You are taking to emulated hardware so your OS can easily be moved to
another platform.
I used to think like you, but these days, if I was installing almost any
server it
would be with a virtual hypervisor.
Dave
Imho, VSI adopting virtualization is a great move as they are responding to
the OpenVMS base requesting reduced support risks, costs, and deployment
flexibility - especially in dev/test environments. Yes, native OpenVMS on
X86-64 support is still critical because there are large OpenVMS Customer
environments that will demand native OpenVMS X86-64 support for performance
and/or security reasons.
Background - The reality is that industry server HW performance has
increased so much in the last decade+ that there are few server Apps on ANY
OS platform that requires a dedicated physical server for performance
reasons.
Security - yes, there are cases to be made to not add another layer of risk
and security patches management that is a fact when using virtualization.
And yes, there are cases where virtualization will not address all
performance sensitive application environments.
Back to past performance considerations. Historically, the reason for big
gap in low utilization levels of servers that was first seen on
Windows/Linux servers 25 years+ ago (pre-VMware) was partly because of the
culture of running one business app per server i.e., migration to three tier
models. When this culture was combined with the IT culture of green fielding
newer much more powerful (albeit cheaper) x86 servers every 3 years on a
one-for-one basis, it is easy to see that the overall utilization of these
x86 servers dropped after each green fielding upgrade was completed.
C level managers began to twitch and get cranky when their IT depts told
them that the servers they had less than 10-15% utilized in peak periods.
Hence - the reason why VMware became so popular. It allowed Customers to
increase the overall utilization of X86 servers, while at the same time,
maintain the culture of one bus app per server instance. Win-win for
everyone(?). Of course, the big winners were Microsoft and Red Hat who get
paid regardless of whether the OS is virtual or physical. The ease of
creating new OS instances with little creation / cleanup governance has led
to OS instance sprawl which again benefits Microsoft and Red Hat's license
model.
The performance utilization background is not only the case for Linux and
Windows servers, but also for OpenVMS servers. Most OpenVMS Customers today
upgrade from VAX and Alpha to IA64 for support and reduced support
costs/risks - not performance reasons. Most OpenVMS Customers are running
just fine on their current HW platforms - typically running at less than 50%
utilization in peak periods.
The primary migration driver for OpenVMS X86-64 migrations will be for
reducing support (end-of-life maint, license, security) risks and costs. As
an example - Oracle on OpenVMS X86-64 servers will enjoy the same PCF
(processor core factor) as Windows and Linux (0.5 x overall Oracle costs) as
opposed to the PCF of existing OpenVMS Alpha/IA64/PowerX HW platforms (1.0 x
overall Oracle costs).
Kerry
--
This email has been checked for viruses by AVG.
https://www.avg.com