OpenVMS hypervised as-is artedi e.U. Agenda I so what is - - PowerPoint PPT Presentation

▶
openvms hypervised as is
SMART_READER_LITE
LIVE PREVIEW

OpenVMS hypervised as-is artedi e.U. Agenda I so what is - - PowerPoint PPT Presentation

Apr 09, 2023 266 likes •668 views

OpenVMS hypervised as-is artedi e.U. Agenda I so what is Hypervision ? and why is it needed/used ? Types of Hypervision why not OpenVMS ? Processor Architectures artedi e.U. Mai-16 2 Agenda - II what else is

slide-1
SLIDE 1

as-is OpenVMS hypervised

artedi e.U.

slide-2
SLIDE 2

Agenda – I

  • so what …is Hypervision ?
  • and why is it needed/used ?
  • Types of Hypervision
  • why not OpenVMS ?
  • Processor Architectures

Mai-16

artedi e.U.

2

slide-3
SLIDE 3

Agenda - II

  • what else …is needed ?
  • Emulation, bringing things together
  • Types of Emulators
  • who does it for VAX and Alpha (VMS)?
  • Example, more detailed
  • Life Demo

Mai-16

artedi e.U.

3

slide-4
SLIDE 4

Hypervise, divide and conquer

  • hyper …ancient greek for ‚over‘
  • videre … latin word for ‚to see‘
  • Hyper+visor …the ‚overseer‘ /surveillant
  • controlled distribution by Monitor Machines VMMs

Mai-16 4

artedi e.U.

slide-5
SLIDE 5

Reasons for hypervision

  • Moneyoptimized use of HW expenses made
  • Resources  optimized use of HW infrastructure
  • Hardware evolves rapidly  miniaturization
  • Clock rates stall  rejected heat
  • Parallelism has its limits  synchronisation issues

Mai-16

artedi e.U.

5

slide-6
SLIDE 6

General Models

  • Divide in Groups (Virtual SystemsOSes)
  • which use their own groups(Processors/Interfaces)
  • Two types of Hypervisors/VMMs

(„Principles for Virtual Computer Systems“,Robert P.Goldberg/1972)

  • Type-1 native or Bare Metal
  • Type-2 hosted

Mai-16

artedi e.U.

6

slide-7
SLIDE 7

Hypervisor, Type-1 Bare Metal

  • doesn‘t need an underlying Software Infrastructure (Host OS)
  • Kernel which supports HW Infrastructure + Management

Interface

  • allows controlled distribution of given Infrastructure
  • is used by diverse higher level Infrastructure aka Guest OS

Systems ( like OpenVMS)

Mai-16 7

artedi e.U.

slide-8
SLIDE 8

X86 VM-4 OS-4 VM-3 OS-3 VM-2 OS-2 VM-1 OS-1

Hypervisors Type-1, practical use

  • Hardware (X86 most likely)
  • 8 Cores
  • the Hypervisor
  • 1st Virtual Machine (VM)
  • 2 Cores assigned
  • OS installed
  • others to follow

Mai-16 8

Hypervisor artedi e.U.

slide-9
SLIDE 9

Hypervisor, Type-2 hosted

  • needs supporting Software Infrastructure fully-fledged OS
  • does share HW Investment and electrical Power resources
  • has to share with other ‚normal‘ applications
  • is fully dependent on hosting OS
  • Patches
  • Security Updates
  • License prolongations
  • …

Mai-16 9

artedi e.U.

slide-10
SLIDE 10

X86

OS-4 OS-3 OS-2

Hypervisors Type-2, practical use

  • Hardware (X86 most likely)
  • 8 Cores
  • the Host OS( grabs Cores)
  • the Hypervisor (an aplication)
  • 1st Virtual Machine (VM)
  • one Cores assigned
  • OS installed
  • others to follow

Mai-16 10

Hypervisor artedi e.U.

OS-1

slide-11
SLIDE 11

Why not for OpenVMS ?

  • most of the Hypervisors use x86 (AMD64, iE64, x64)
  • VMS runs on VAX (CISC), Alpha (RISC) and Integrity (EPIC)
  • Hypervisors neither translate nor emulate
  • Type-2 Integrity based Hypervisors running on HP-UX

(Integrity Virtual Machine)

  • most customers want x86

Mai-16

artedi e.U.

11

slide-12
SLIDE 12

Types of Processors

  • CISC … Complex Instruction Set Computing

PDP-11 (16bit),VAX (32 bit), x86

  • RISC … Reduced Instruction Set Computing
  • Alpha, MIPS, PA-RISC, Power(PC), SPARC,ARM (64bit)
  • EPIC … Explicit Parallel Instruction Computing
  • Integrity (Itanium) (64bit)
  • Hybrids … CISC to RISC (Emulators ?)
  • x86 starting with Pentium Pro

Mai-16

artedi e.U.

12

slide-13
SLIDE 13

Emulate

  • aemulare…lat.word for ‚to imitate‘
  • System/Software which imitates another System…in some

aspects

  • Imitation by Transformation
  • Emulators transform translated code for
  • different Processors with different ‚vocabulary‘
  • Emulators are the supporting pillars for bridging
  • different Architectures with different Infrastructures
  • transparent to the upper Layers (Operating Systems)

Mai-16 13

artedi e.U.

slide-14
SLIDE 14

Emulators, types of

  • Hardware Emulators
  • ICE …In Circuit Emulator
  • Printer Emulator  HP-PCL
  • Terminal Emulator
  • Processor Emulator
  • Alpha, VAX
  • HP 3000
  • SUN Sparc

Mai-16

artedi e.U.

14

slide-15
SLIDE 15

Emulators, practical use

  • original Hardware
  • original Operating System +

Apps (OS+)

  • new Hardware
  • Emulator
  • transfer OS (still original)
  • discard old Hardware

Mai-16 15

Hardware OS+ Emulator OS+ Hardware artedi e.U.

slide-16
SLIDE 16

hyperviseemulatetranslate

  • Hypervisors
  • divert a given Infrastructure and assign it to upper Layers
  • Emulators
  • ‚mask‘ the underlying Infrastructure
  • Translators
  • make HighLevelLanguages readable to the Processor

Mai-16 16

artedi e.U.

slide-17
SLIDE 17

Hypervisor

Mai-16

artedi e.U.

17

slide-18
SLIDE 18

OpenVMS and Tru64

  • n X86

AVTware

slide-19
SLIDE 19

Desires; to fulfil

  • keep OpenVMS based Applications alive
  • highly customized
  • high value
  • Mission Critical
  • Continuity Issue
  • reduce Operating Expenses
  • converge Infrastructure
  • reduce space requirements
  • reduce power consumption
  • reduce costs (and complexity) of Hardware Maintenance

Mai-16

artedi e.U.

19

slide-20
SLIDE 20

Obstacles; to overcome

  • no Code Migration, due to
  • Source Code missing
  • Application Vendor doesn‘t sell Migration
  • Application Vendor does sell, but is way to expensive
  • still risk of incompatibilities
  • Hardware Infrastructure to maintain
  • Storage Arrays
  • TapeDrives
  • FC-Switches to connect to

Mai-16

artedi e.U.

20

slide-21
SLIDE 21

Expectations to be met

  • no software changes
  • reliable & secure
  • support modern infrastructure
  • easy to manage
  • performance

Mai-16

artedi e.U.

21

slide-22
SLIDE 22

Solution; first choice  Bare Metal

  • get new Hardware
  • get and install Hypervisor
  • hook emulated Systems onto
  • transfer Systems currently in

use

  • copy disk content
  • continue with original SW

(OS+Apps)

Mai-16

artedi e.U.

22

x86

vtAlpha DS10 vtVAX 4000-90 vtAlpha ES40

vtServer

Tru64 OpenVMS VAX OpenVMS Alpha

slide-23
SLIDE 23

Bare Metal

  • Windows
  • Linux
  • other Hypervisor
  • Alpha/VAX Reliability
  • Single Point of Contact

Mai-16

artedi e.U.

23

no cost, no maintenance, no sync time delays

slide-24
SLIDE 24

Solutions; other Options(Type-2)

  • use existing Hardware
  • use existing Hypervisor
  • install vtServer onto it

(one to many)

  • create virtual Alphas and

VAXes (one to many)

  • Install System(s)
  • live migration

Mai-16

artedi e.U.

24

vtServer

VM X86

vtServer

vtAlpha ES40 vtAlpha DS10 vtVAX 4100 OpenVMS Alpha

slide-25
SLIDE 25

Solutions; and another one

  • use existing Hardware
  • use existing Hypervisor
  • host other guests
  • install vtServer as another

guest

  • create virtual Alphas and

VAXes (one to many)

  • Install System(s)

Mai-16

artedi e.U.

25

vtServer

VM X86

vtAlpha ES40 OpenVMS Alpha Windows Ubuntu

slide-26
SLIDE 26

Sizing; CPU

  • # Cores
  • virtual CPU = 1,5 Host CPU-cores
  • Intel/ AMD
  • Generation (Haswell)
  • Freqency, the more the better ( 3GHz +)
  • Hyperthreading

Mai-16

artedi e.U.

26

slide-27
SLIDE 27

Sizing; Memory

per virtual Alpha/VAX :

  • Virt.Mem + 25% +1 GB

1024 + (1024*0,25) +1024 = 2304

  • safety valve

Mai-16

artedi e.U.

27

slide-28
SLIDE 28

Infrastructure; Transparency

Mai-16

artedi e.U.

28

Storage Adapter Network Adapters Driver Driver Storage Network Storage Network vtAlpha vtVAX X86 vtServer Storage Network

slide-29
SLIDE 29

Infrastructure; Flexibility

Mai-16

artedi e.U.

29

X86 vtServer SCSI external internal SAS SATA iSCSI NFS SMB SAN

slide-30
SLIDE 30

Networking; Options

  • Alpha

DE435 DE450 DE500 DE600

  • VAX

DELQA DEQNA SGEC DEMNA

Mai-16

artedi e.U.

30

  • Combine links
  • VLAN support
  • Bonding support

Virtual Switch Virtual Switch Virtual Switch

Ethernet

DE500 DE435 DE500 Host Ethernet DELQA DEMNA DEQNA

slide-31
SLIDE 31

Licensing

  • licensed via LicenseKeys
  • presented via
  • License Dongles connected to USB Port
  • Network (TCP/IP) Link
  • limited Timeframe or perpetual
  • redundant License Keys to overcome SPOF

Mai-16

artedi e.U.

31

slide-32
SLIDE 32

Licensing; distributed

Mai-16

artedi e.U.

X86 X86 X86 vtLicense vtLicense vtAlpha vtAlpha vtLicense

slide-33
SLIDE 33

vtAlpha, Licensing

Mai-16

artedi e.U.

33

AlphaStation 200, 250, 255, DEC3000 AlphaServer 300, 400 vtAlpha-AS AlphaServer 800, 1000 AlphaStation 500, 600, DPW, XP900, XP1000 vtAlpha-BS AlphaServer 2000, 2100 AlphaServer 4000, 4100 vtAlpha-CS AlphaServer DS10, DS15 AlphaServer DS20, DS25 AlphaServer 1200 vtAlpha-DS AlphaServer ES40, ES45, ES47 vtAlpha-ES AlphaServer GS80, GS160, GS320 vtAlpha-GS (Q2/2015)

slide-34
SLIDE 34

vtVAX, Licensing

Mai-16

artedi e.U.

34

VAXstation II, GPX, 2000, VAXserver 3600/3900 vtVAXstation MicroVAX II, 2000 MicroVAX 3100 - 3900 VAX 4000 vtVAX-128 ( + AC ) MicroVAX 3100 VAX 4000 VAX 6000 vtVAX-256 ( + AC ) MicroVAX 3100 VAX 4000 VAX 6000 vtVAX-512 ( + AC ) VAX 6000 1 – 6 CPU, up to 3.5 GB memory VAX 7000 1 – 6 CPU, up to 3.5 GB memory vtVAX-7000

slide-35
SLIDE 35

Life Demo

Mai-16

artedi e.U.

35

Virtual Switch vtAlpha OVMS 7.3-2 ds25 vtAlpha OVMS 8.4-2

ds20

slide-36
SLIDE 36

.

still beats

slide-37
SLIDE 37

Sieve of Eratosthenes

Mai-16

artedi e.U.

37

10 1 2 3 4 5 6 7 8 9

slide-38
SLIDE 38

Mai-16

artedi e.U.

38