Why move to VSI OpenVMS?

Transcription

1 Why move to VSI OpenVMS? OpenVMS Bootcamp 2017 Session 235 Colin Butcher CEng FBCS CITP Technical director, XDelta Limited Copyright XDelta Limited, 2017 Page 1 of 42

2 XDelta: Who we are VSI Professional Services Alliance member Independent consulting engineers since 1996: UK based with international reach Delivering OpenVMS based systems for 30+ years Technical leadership for business-critical systems Design, planning and implementation Mentoring and skills transfer Systems engineering background Gartner (2009): Identified XDelta as one of few companies world-wide capable of OpenVMS platform migration projects Copyright XDelta Limited, 2017 Page 2 of 42

3 Xdelta: The view from HPE Copyright XDelta Limited, 2017 Page 3 of 42

4 Part 1 1. Why move to VSI OpenVMS? 2. VSI OpenVMS on Integrity Servers 3. VSI OpenVMS on Alpha 4. Benefits of moving to VSI OpenVMS 5. Moving to VSI OpenVMS next steps Copyright XDelta Limited, 2017 Page 4 of 42

5 VSI OpenVMS: Evolution not revolution Need minimal risk of disruption to business: Availability, data integrity, scalability, performance, security Need supported systems to run business Want to reduce long-term cost of ownership Cost of redesign or replacement can be prohibitive Complexity and difficulty of moving applications and data can make it almost impossible to change platform Copyright XDelta Limited, 2017 Page 5 of 42

6 OpenVMS: Mission-critical platform Most OpenVMS systems purpose written: Bespoke applications Tightly integrated with operating system Extensive use of infrastructure features Multi-site mission-critical capabilities Stable - running 24x7 with minimal disruption Often first implemented long ago, gradually evolved Copyright XDelta Limited, 2017 Page 6 of 42

7 OpenVMS: Mission-critical platform Well engineered operating system: Well structured and well documented Scales well from small to large implementations Distinct culture: People who like to understand things People who like to do things properly Copyright XDelta Limited, 2017 Page 7 of 42

8 Availability - Performance - Security Multi-site disaster tolerance Operating system based synchronous data replication Scale-up with big blade hardware Scale-out with shared everything OpenVMS clusters Low IO latency, high IO throughput Secure object protection, alerting and auditing Copyright XDelta Limited, 2017 Page 8 of 42

9 VSI OpenVMS: Supported platforms HPE Integrity Servers: Next generation -i6 Kittson family in progress Current generation -i4 Poulson family Previous generation -i2 Tukwila family Earlier generation servers (rx2660, etc.) x port in progress HPE Alpha Servers: V8.4-2L1 (all Alpha Servers) V8.2-2L2 performance build (EV6 and later) Copyright XDelta Limited, 2017 Page 9 of 42

10 VSI OpenVMS Rolling Roadmap Copyright XDelta Limited, 2017 Page 10 of 42

11 HPE OpenVMS Service Support Roadmap Copyright XDelta Limited, 2017 Page 11 of 42

12 VSI OpenVMS IA64 x86 Serivce Roadmap Copyright XDelta Limited, 2017 Page 12 of 42

13 VSI OpenVMS Alpha Service Roadmap Copyright XDelta Limited, 2017 Page 13 of 42

14 OpenVMS: Platform migration why move? Urgency Small Alpha (eg: DS25) Mid-range Alpha (eg: ES45) Large Alpha (eg: GS1280) HP VM Small IA64 (eg: rx2660, rx2800-i2) Mid-range IA64 (eg: BL870c-i2) Large IA64 (eg: BL890c-i2) Small VAX (eg: microvax) Mid-range VAX (eg: VAX 4000) Large VAX (eg: VAX 7000) Platform type / scale Copyright XDelta Limited, 2017 Page 14 of 42

15 Part 2 1. Why move to VSI OpenVMS? 2. VSI OpenVMS on Integrity Servers 3. VSI OpenVMS on Alpha 4. Benefits of moving to VSI OpenVMS 5. Moving to VSI OpenVMS next steps Copyright XDelta Limited, 2017 Page 15 of 42

16 HPE Integrity -i4 servers: Highlights Same form factor as i2 servers (scalable blades + rack) Re-architected Poulson CPU design: 2.53 GHz 8 core processor with shared L3 cache Around 30 % per core greater throughput Reduced NUMA effects for same core count Better memory latency and bandwidth Improved floating point and integer performance Improved hyperthreading less stall time 32 cores - bl870c-i4 about 1.3x better than bl890c-i2 Copyright XDelta Limited, 2017 Page 16 of 42

17 HPE Integrity -i4 servers: Hardware bl860c-i4: single blade, 16 cores, 384 GB, 4x 10GigE, 3x mezz, 1C2D SAS bl870c-i4: dual blade, 32 cores, 768 GB, 8x 10GigE, 6x mezz, 2C4D SAS bl890c-i4: quad blade, 64 cores, 1.5 TB, 16x 10GigE, 12x mezz, 4C8D SAS rx2800-i4: 2U rack, 16 cores, 384 GB, 4x 1GigE, 6x PCIe gen2, 1C8D SAS Copyright XDelta Limited, 2017 Page 17 of 42

18 Server hardware differences (-i2 to i4) Re-architected CPU, not just an updated design Higher clock rate (-i4 now 2.53 GHz, was 1.73 GHz) Out of order instruction execution Minimal stall time between co-threads with hyperthreading Double the core count (8 cores) Greater memory capacity Reduced memory latency Shared on-chip cache New 10GigE LoM for blades - LAN only, not FCoE New 16GigFC for rx2800-i4 (needs PCIe 3.0) Copyright XDelta Limited, 2017 Page 18 of 42

19 Chassis hardware c7000 / c3000 Virtual Connect (1GigE, 10GigE, 8GigFC) Flex10 LAN side of FlexFabric 10GigE chassis based switching 10GigE passthrough 1GigE passthrough 8GigFC chassis based switching 4GigFC passthrough Copyright XDelta Limited, 2017 Page 19 of 42

20 Infrastructure hardware HPE 3PAR and XP / XP7 fibrechannel arrays Multivendor fibrechannel storage SAS SSD devices for local storage SAN fabric switches at 8 GigFC / 16 GigFC Data network switches at 10 GigE Copyright XDelta Limited, 2017 Page 20 of 42

21 System architecture rx2800-i4 Copyright XDelta Limited, 2017 Page 21 of 42

22 Scalable blade architecture bl8x0c-i4 Copyright XDelta Limited, 2017 Page 22 of 42

23 QPI fabric bl870c-i4 and bl890c-i4 Copyright XDelta Limited, 2017 Page 23 of 42

24 High core count CPU 00 is the primary CPU - try to reduce its workload Consider physical layout RADs, NUMA and IO devices CPU choice for fastpath devices CPU choice for TCPIP (BG device) CPU choice for Pedriver CPU choice for dedicated lock manager Copyright XDelta Limited, 2017 Page 24 of 42

25 NUMA (non-uniform memory access) OpenVMS uses large shared memory regions: XFC (50 % available memory by default) RMS global buffers Global sections (especially database caches) Memory disc driver (MD devices) Set memory interleave behaviour with memconfig at EFI shell (requires reboot) Ensure physical memory installation is correct! Useful starting point for OpenVMS is mostly UMA Copyright XDelta Limited, 2017 Page 25 of 42

26 Memory architecture bl890c-i4 Copyright XDelta Limited, 2017 Page 26 of 42

27 Hyperthreading Hyperthreading is extremely workload dependent In general the OpenVMS scheduler does a better job Enable / disable hyperthreading with cpuconfig at EFI shell (requires reboot) CPU count will appear to double when enabled V8.4-2 supports 64 scheduling units V8.4-1H1 supports 32 scheduling units Can STOP/CPU <nn> to selectively shut down co-threads Copyright XDelta Limited, 2017 Page 27 of 42

28 Performance engineering Without good data you cannot do good performance work Avoid guesswork - run T4 all the time If needed, use T4 expert mode and SDA extensions A faster machine just waits more quickly! Don t make it go faster, stop it going slower The fastest IO is the IO you don t do The fastest code is the code you don t execute The idle loop is anything but idle Copyright XDelta Limited, 2017 Page 28 of 42

29 Part 4 1. Why move to VSI OpenVMS? 2. VSI OpenVMS on Integrity Servers 3. VSI OpenVMS on Alpha V8.4-2L1 release, all Alphas V8.4-2L2 performance release, Alpha EV6 or later 4. Benefits of moving to VSI OpenVMS 5. Moving to VSI OpenVMS next steps Copyright XDelta Limited, 2017 Page 29 of 42

30 VSI OpenVMS Alpha V8.4-2L1 / V8.4-2L2 Released early Simplified licensing: Base OS Layered products Bundled support services Aimed at support of existing customers Stepping stone to x86-64 V8.4-2L2 is a performance release for EV6 or later Copyright XDelta Limited, 2017 Page 30 of 42

31 Alpha: Next steps Plan and test upgrade to VSI OpenVMS for Alpha. V8.4-2L2 can give 20% or greater more performance Understand the support issues and regulatory / legal implications if you choose to stay with old hardware and old versions of OpenVMS Consider the surrounding infrastructure as well, especially storage subsystems Copyright XDelta Limited, 2017 Page 31 of 42

32 Alpha: Potential issues with staying Becomes easy to put off moving to Integrity can create a bigger challenge later when moving to x86-64 Big system performance is hard to deliver from an emulator Limited hardware capabilities of Alpha platforms: 1Gbps or 2Gbps fibrechannel (KGPSA). Nemonix provide a 4Gbps fibrechannel interface, supported by VSI OpenVMS. Greater risk of hardware failures Hardware support becoming more difficult and expensive Space, power, cooling, etc. Copyright XDelta Limited, 2017 Page 32 of 42

33 Alpha: Potential ways forward Extends support past HPE deadline for organisations still reliant on Alpha with VSI OpenVMS Move to supported OS without changing hardware Move to later hardware (or emulator) and supported OS without changing applications or overall system structure Greater performance on EV6 and later Buy time to complete migrations to Integrity Get current on Alpha before migrating to Integrity or x86-64 Continue with Alpha until OpenVMS on x86-64 is available as a production ready system Copyright XDelta Limited, 2017 Page 33 of 42

34 Part 5 1. Why move to VSI OpenVMS? 2. VSI OpenVMS on Integrity Servers 3. VSI OpenVMS on Alpha 4. Benefits of moving to VSI OpenVMS 5. Moving to VSI OpenVMS next steps Copyright XDelta Limited, 2017 Page 34 of 42

35 VSI OpenVMS: V8.4-2L1 and beyond Future OpenVMS releases from VSI: hardware platforms: Alpha, IA64, x86-64 new features and enhancements up-to-date components (eg: SSL, Java) prepares the way for transition to OpenVMS on x86-64 Support by VSI for VSI releases of OpenVMS: Security patches, bugfix patches, patch rollup updates, new versions of OpenVMS and layered products Support beyond end 2020 Copyright XDelta Limited, 2017 Page 35 of 42

36 VSI OpenVMS: V8.4-2L1 SSL1 update Updated SSL1 based on 1.0.2h, recent patch kit to 1.0.2k APIs have changed in OpenSSL implementations Updated components that use SSL1: Encryption algorithms Key exchange mechanisms TLS 1.2 Co-existence mechanism with earlier SSL Copyright XDelta Limited, 2017 Page 36 of 42

37 VSI OpenVMS: New TCP/IP stack Some of the major updates include: SSH (V1 & V2) NFS V4 DHCP V3 IPv6 (complete application protocols supported) IPSEC (full support) Bind 9.9 Kerberos 5 Advanced features such as IPS, paired network interface support, and improved performance monitoring capabilities Copyright XDelta Limited, 2017 Page 37 of 42

38 VSI OpenVMS: HPE Integrity -i4 servers Significant step up from HPE Integrity -i2 servers: rx2800-i4 (16 cores) > 2x rx2800-i2 (8 cores) - same space bl860c-i4 (16 cores) > bl870-i2 (16 cores) - half space bl870c-i4 (32 cores) > bl890-i2 (32 cores) - half space bl890c-i4 (64 cores) > 2x bl890-i2 (32 cores) - same space Per-socket licences Significant step up from AlphaServer GS1280, with modern storage and network infrastructure Copyright XDelta Limited, 2017 Page 38 of 42

39 Part 6 1. Why move to VSI OpenVMS? 2. VSI OpenVMS on Integrity Servers 3. VSI OpenVMS on Alpha 4. Benefits of moving to VSI OpenVMS 5. Moving to VSI OpenVMS next steps Copyright XDelta Limited, 2017 Page 39 of 42

40 Upgrade and integrate Evolution is lower risk than revolution Migrating to VSI OpenVMS now will help you migrate to x86-64 when it becomes production ready Retain best of existing investment Code compatibility and data portability Phased approach over time, not rip and replace Copyright XDelta Limited, 2017 Page 40 of 42

41 It s easy to proceed Licences, support and services direct from VSI, or partners VSI operating system and layered products active development and release streams OpenVMS patches and improvements, especially security ISV layered products HPE servers and multivendor infrastructure Copyright XDelta Limited, 2017 Page 41 of 42

42 Why move to VSI OpenVMS? OpenVMS Bootcamp 2017 Session 235 Colin Butcher CEng FBCS CITP Technical director, XDelta Limited Copyright XDelta Limited, 2017 Page 42 of 42