HDS TECHNOLOGY DEMONSTRATION Steve Sonnenberg May 12 2014

INTRODUCTION § Hitachi Data Systems (HDS) is a wholly owned subsidiary of Hitachi global § HDS develops solutions using Hitachi hardware (storage and servers) and resells this equipment outside of Japan § Together we collaborate on Open. Stack and other projects ‒ Hitachi storage drivers covering all storage offerings ‒ Research and collaboration on other Open. Stack issues of global concern 2

HITACHI AND OPENSTACK: ENABLING OUR PLATFORMS NOVA | KVM Compute Compatible with Icehouse, Support from Havana Storage Cinder | i. SCSI 3 Cinder | FC & FCOE Cinder | i. SCSI & NFS Swift

INTRODUCTION ‒ A way to add a compute node to an Open. Stack cluster in a couple of minutes ‒ Normally a server needs to be PXE-booted, load a bare OS or puppet agent, copy the OS, reboot and then perform configuration (e. g. to become a hypervisor) ‒ Elapsed time 5 -30 min ‒ Demonstration consisted of: ‒ Maintaining a set of ‘compute-host’ templates in Cinder volumes ‒ Represent multiple flavors of hypervisors, etc. ‒ Doing a high-speed volume clone and dynamically setting the i. SCSI boot volume ‒ The configuration was part of the template. ‒ Open. Stack will register a new compute server when presented with a new IP addresses ‒ Elapsed time < 2 min 4

PREPARATION FOR PROVISIONING Create boot image for Virtual or Physical Server Management Portal １ＯｐｅｎＳｔａｃｋ Storage （Ｃｉｎｄｅｒ） Server Manager （Ｎｏｖａ） Hitachi Storage Plugin ２ Create Boot Template Physical Server Virtual Server ＶＭＶＭ Hypervisor ＶＭＶＭ・・・ Hypervisor Hitachi Storage Boot Disk ・・・ 5 ・・・ Boot Disk for Virtual Server Physical Server Templates 5

PREPARE TO BOOT NEW SERVER Clone boot volume for new server (snapshot-create) Management Portal 1 ＯｐｅｎＳｔａｃｋ Storage （Ｃｉｎｄｅｒ） Server Manager （Ｎｏｖａ） Hitachi Storage Plugin Physical Server Virtual Server ＶＭＶＭ Hypervisor ＶＭＶＭ・・・ Hypervisor ・・・ Hyper Attach disk as Boot volume Hitachi Storage 3 Boot Disk ・・・ Create Boot disk using HTI Snapshot 2 Boot Disk for Virtual Server 6 6

LAUNCH NEW SERVER; NOW ACTIVE HYPER Management Portal １ Launch new Server (IPMI) ＯｐｅｎＳｔａｃｋ Storage （Ｃｉｎｄｅｒ） Server Manager （Ｎｏｖａ） Hitachi Storage Plugin Register Service 2 Physical Server Virtual Server ＶＭＶＭ Hypervisor ＶＭＶＭ・・・ Hypervisor ・・・ Hyper Hitachi Storage Boot Disk ・・・ 7 ・・・ Boot Disk for Virtual Server Physical Server 7

THIS YEAR’S CHALLENGE § Leverage the Hitachi LPAR (logical partitioning) capabilities of its server line ‒ Launch instances directly into LPARs 8

IMPORTANCE OF VIRTUALIZATION § Open. Stack features support for a wide range of hypervisors ‒ Using the Nova ‘Bare. Metal’ driver and future Ironic support, Open. Stack also supports bare-metal provisioning ‒ Why use bare metal? (just when virtualization was going to save the world) § HDS high-end and mid-range blade servers support a unique type of hardware provisioning known as LPAR (logical partitioning) ‒ It provides most of the benefits of bare metal without the cost 9

LPAR VS. HYPERVISOR VIRTUALIZATION § Logical partitioning (LPAR) ‒ Logically dividing compute resources ‒ Similar to mainframe ‒ Devices are directly accessible from guest OSs for better isolation ‒ Implemented in firmware for security and performance ‒ Memory is never shared § Virtual machine (VM) ‒ Emulation generates virtual devices ‒ Independent from server hardware constraints ‒ Apps and drivers may need to be written to address virtual devices Divides Server Hardware LPAR Physical CPU Physical Memory Physical I/O Physical Server Generates Virtual Devices VM VM Virtual CPU Memory Phys. CPU Virtual I/O Phys. Memory Physical Server 10 LPAR Phys. I/O

HIGH EFFICIENCY HITACHI LPAR LOGICAL PARTITIONING § Hitachi LPAR feature logically divides physical compute resources ‒ Resources can be dedicated to a partition for performance or shared for dynamic load balancing § Up to 30 LPARs per blade § Benefits ‒ Near-native performance ‒ Securely isolate partitions for sensitive multi-tenant environments ‒ Optimize efficient use of compute resources ‒ Respond dynamically to changing workloads (in shared mode) 11 © Hitachi Data Systems Corporation 2014. All Rights Reserved.

HITACHI DEMO PORTAL SERVER EXTENDS HORIZON FOR OPENSTACK MANAGEMENT 12

LAUNCHING AN INSTANCE INTO AN LPAR (HORIZON) FLAVOR IS USED TO SELECT AN LPAR 13

RUNNING LPARS An instance running in an LPAR can be managed like a VM 14

ON THE BLADE SERVER… LPARs are defined prior to usage 15

SOME FUNCTIONS AREN’T FULLY INTEGRATED 16

LPAR DELETION 17

UNDERLYING TECHNOLOGY § The majority of the launch time is normally spent in copying the image from glance to ephemeral storage ‒ Also impacts the footprint of compute servers by requiring local storage § Using LPARs, a daughter card (mezzanine) provides shared fibre-channel or CNA functions which can be shared (or dedicated) to LPARs Mezzanine Card § To address the significant delay in copying an image into storage for execution… 18

INTRODUCING HITACHI ENTERPRISE STORAGE Hitachi provides some of world’s Best storage solutions. ENTERPRISE STORAGE CAPABILITIES 19

KEY TECHNOLOGIES • Extreme Performance/Reliability • Storage Virtualization • Dynamic Storage Pools • Intelligent Storage Tiering • Data Protection (local/remote) • Data Migration 20

REDUCING LAUNCH TIME § Bootable images are maintained as volumes § ‘Bare. Metal’ driver creates a high-speed clone using HTI (Hitachi thin image) and lets the LPAR do a FC boot ‒ HTI uses controller-based copy-after-write technology (time to prepare the images is in seconds) 21

STARTUP TIME ENTERPRISE SERVERS HAVE CONSIDERABLE POST DELAYS § Hitachi servers don’t have quick boot option ‒ (if it has memory, it needs to be tested) § Fortunately, LPARs have minimal POST requirements 22

THE RESULT… § Very fast machine startup time § High isolation between instances § Ability to match VM density / server § Stronger guarantees for performance / latency § Better utilization of constant server improvements 23

THANK YOU 24