PowerVC and Power Systems Cloud Trends

© 2015 IBM Corporation
Cloud Manager with
OpenStack for PowerJay Kruemcke
IBM Cloud
jayk@us.ibm.com
Kruemcke.com
@chromeaix @cloudrancher facebook.com/ibmpowervc LinkedIn PowerVC group
Power Cloud Trends
All statements regarding IBM's future direction and intent are subject to
change or withdrawal without notice, and represent goals and
objectives only
© Copyright IBM Corporation 2015.

IAAS?
PAAS?”
SAAS?”
Private?
Public?
Hybrid?
2

Why “Cloud”?
 When somebody say “We should be doing cloud computing?” –
what is the problem you are trying to solve?
– Speed
– Flexibility / Responsiveness
– Reduced expense
 Understand the dissatisfaction with IT that drives the crazy
interest in cloud computing.
 Understand what is going on with public cloud in your shop
Make sure you are a part of the cloud conversation
 IBM Power servers can provide cloud-like service delivery
3

Cloud IT is different
Traditional IT Cloud IT
Infrastructure provided availability Fault tolerant application design
Scale-up Applications Scale-out Applications
IT Controlled End User Empowered
Fine Control Coarse Control
Slow Fast
Explicit Resource allocation Automated Resource Allocation
Management Silos Integrated management

Businesses are choosing a variety of cloud models to meet
their unique needs and priorities.
Private cloud
Hybrid IT
Public cloud
Appliances, pre-integrated systems and
standard hardware, software and networking.
Traditional IT
On or off premises cloud infrastructure
operated solely for an organization and
managed by the organization or a third party
Available to the general public or a large
industry group and owned by an
organization selling cloud services.
Traditional IT and clouds (public and/or private) that
remain separate but are bound together by technology
that enables data and application portability
5

Building a Power Cloud
6
Cloud management
• Self-service provisioning
• Virtual systems & applications services
• Subscriber and account management)
• Sophisticated patterns of virtual machines
• Management interface: Cloud Manager With
OpenStack for Power(SCE), IBM Cloud
Orchestration
Base Virtualization management
• Create virtual machines
• Virtual network management
• Infrastructure monitoring
• Management interface: HMC or PowerKVM host
Advanced Virtualization management
• Virtual Image Management and Deployment
• Resource Pooling and Dynamic VM Placement
• Improved Utilization and VM Resilience
• Management interface: PowerVC
PowerVC
HMC OR PowerKVM
Cloud

Hardware Management Console
7
Base Virtualization infrastructure
• Create virtual machines
• Virtual network management
• Infrastructure monitoring
• Management interface: HMC or PowerKVM host
HMC OR PowerKVM
PowerVC
Cloud

PowerVM Simplification
8
Planning and
Sizing
Infrastructure
Setup
Virtualization
Environment
Provision Virtual
Machines
Monitor Virtual
Environment
Ongoing
Performance and
Capacity Planning
Serviceability
New PowerVM UI
CLI, APIs Performance Monitors, Advisors Platform Tools
 Single point of management from new PowerVM UI
 Planning, performance and capacity management tools
 Improved usability across entire management lifecycle
From This To This

PowerVM Management GUI
9
9
Single launch point for all PowerVM configuration
Management of all VIOS function
 No VIOS CLI needed
 Built in Performance monitoring
 Templates simplify defining new LPARs/VMs
 One touch deployment of new VIOS servers for quick server onboarding

Performance Monitoring – Shared Adapter Utilization
10
1
0

PowerVM Management GUI - Templates
12
1
2

HMC V8 R8.4.0 (2H 2015) Highlights
 Mobility:
– Support for Dedicated VIOS Ethernet SR-IOV virtualization including mobility
– LPM allowed when redundant VIOS is down
 AIX Live Kernel Update support for iFixes
 More Usability improvements
– SSP failover group and multiple tiers support
– Storage topology view
– Touch screen enablement
 Automatic conversion of permanent processor entitlement to
System Pool processor entitlement
 VLAN tag support for IBMi network install
 New HMC hardware (CR9)
 Virtual HMC
14

Virtual HMC Appliance (2H15)
 Environment / Hardware Supported
– Supports x86 hardware – similar to current HMC hardware appliance
– Not restricted to Lenovo / IBM x86 hardware
– Minimum configuration – 4 CPUs, 8 GB memory, 120 GB disk, 2 network interfaces
(vmxnet3 for Vmware)
 Requires x86 64 bit Hypervisor with hardware virtualization (VT-x / AMD-V)
– VMware vSphere ESXi 5
– KVM, RHEL 6.4 and above
 Expecting to use software licensing (SWMA) for the virtual appliance
– Customer number and managed server MTMS needed for download from IBM
 Unsupported Functions
– Format media
– Call Home via modem
– Call Home of HMC hardware failures
 New vHMC functions:
– Activation engine – provides configuration on first boot
– Accept License, locale, network, SSH, NTP
– Allow second virtual disk multiple for /data
15

mHMC Smartphone management App
 View Only Access
 Requires v8 HMC
 Requires access to
HMC network
 Uses HMC REST APIs
to provide data
 Available in July for
Android & Apple devices
through App stores
©
16
Available Now!

NovaLink architecture: Power Systems Platform Management
17
Goal: Simplify PowerVM virtualization, accelerate cloud enablement, and improve scale
PowerVM
PHYP
FSP
HMC
VIOSVIOSVIOS
Controller
OpenStack
Nova
OpenStack
Nova
OpenStack
Nova
PowerVM
PHYP
FSP
Novalink
VIOSVIOSVIOS
Controller
Becomes
Key Benefits
Improved management scalability – support more virtual machines
Aligns PowerVM with the OpenStack community scale model – simplifying future OpenStack exploitation
Simplifies management configuration – HMC not needed for virtual machine deployment and configuration
Enables flexibility to use any OpenStack based manager to manage PowerVM
Uniform management for PowerVM and PowerKVM based systems
OpenStack
Nova

PowerVC – Power Virtualization Control
Advanced Virtualization management
• Virtual Image Management and Deployment
• Resource Pooling and Dynamic VM Placement
• Improved Utilization and VM Resilience
• Management interface: PowerVC
PowerVC
HMC OR PowerKVM
Cloud
18

Proprietary Open Source Only Open “Plus”
Limited flexibility for
cloud integration
‘Some Assembly
Required’
Enterprise-ready
out of the box
PowerVC – Different by design
19
• Easy to use
• Easy to install
• Upward integration

What Can PowerVC do for you?
20
“A simple tool to quickly roll out LPARs/Virtual Machines on Power Systems”
 Easily clone, resize, and relocate Power Systems virtual machines
– Increase agility and execution to quickly respond to changing business requirements
– Complete virtual machine provisioning including Storage, Compute, and Network
– Policy-based placement of new and relocated virtual machines
– Remote restart of Virtual Machines from failed physical hosts (POWER8 only)
 Quick and easy installation to get you up and running quickly
– One button verification of stack integration and operational environment
– Simplify operations by not having to logon to HMC, VIOS, or storage to provision virtual machines
– Easy to use user interface and completely programmable API
 Upward integration to cloud managers for private cloud management
– Build on OpenStack APIs for automation and extensibility
– Integration to Cloud Manager with OpenStack for POWER (formerly SmartCloud Entry)
– Planned integration to IBM Cloud Orchestrator (formerly SmartCloud Orchestrator)

Base provisioning and virtualization
• Rapid LPAR provisioning and
deprovisioning
• Storage provisioning
• Virtual network configuration
• Physical and virtual resource discovery
• LPAR resize (dynamic LPAR changes)
• LPAR migration (Live Partition Mobility)
• Image capture
• Image repository and authentication
services
Rapid provisioning and management
of VMs/LPARs on Power Systems
using an intuitive Web interface
Advanced capabilities
• Compute templates (“t-shirt sizes”)
• Storage templates
• Storage Connectivity Groups
• Placement policies
• Collocation rules
• SAN volume create/delete
• Maintenance mode
• Remote restart
PowerVC Functional Summary
21

Provisioning comparison
PowerVM Native (with HMC 8)
1. Plan – Select system to deploy to
2. Plan – Select storage to use
3. Plan – Select Network addresses
4. Request Network addresses
– Wait
5. Request Storage volume(s)
– Wait for SAN team to create LUNs, zone storage
and fiddle with WWPN etc.
6. Select template for VM/LPAR
7. Create Partition
8. Attach Data volumes (if needed)
9. Install AIX into empty VM
10. Post installation Customization and
application installation
Finished!
PowerVC
1. Select image(s) to deploy
2. Deploy image to create new VM including
AIX and applications
– Scheduler automatically selects physical host
– SAN volumes created and appropriately zoned
– Network allocated from range or addresses or DHCP
3. Automatic customization via Cloud-init on
first boot
Finished!
22
0 100 200 300 400 500 600 700
Traditional PowerVM (by an expert)
PowerVC managing PowerVM
Virtual Machine Deployment Duration*
User Input Deploy
*Does not include wait time for organization silos

Some reasons why Power clients are implementing PowerVC
 Faster time to deploy VMs
 Easier to use
 Lower administrator skill requirement
 Reduce need to custom deployment scripts
 Building block for efficient Power cloud
 Building block to self-service cloud
 Building block to sophisticated cloud deployment
 Management said “We need a Cloud!”
23

Resize
Attach Additional Volume
Migrate / LPM
DeployCapture
Full Virtual Machine Life Cycle
DeleteOn Board
24

What about Organization Silos?
 “Cloud” management does not allow for silos
 Cloud administrators must have the ability to control Compute,
Storage and Network resources
 Storage workarounds:
– Use Shared Storage Pools
– Limit access to a specific storage pool in VMAX
25

IBM Power Systems Management Transition
26
 Cross IBM Platform management
 Proprietary interfaces
 IBM Eco System only
 IBM provided resource support
 Monolithic design
 Broad functionality
 Built for in-house IT management
 Heterogeneous Management at the Cloud level
 Open, standard APIs
 Rich, diverse Eco System
 Hardware vendor provided device support
 Loosely coupled design
 Extendable, Fit-For-Purpose functionality
 Built for Private, Public, and Hybrid Clouds
The market shift to Cloud drove our adoption of Open
standards-based Systems Management

 Community led accelerated pace of innovation
 An open alternative to proprietary stacks for lower cost and more flexibility
 Vendors responsible for support of hardware and hypervisor resources
 Open APIs for greater flexibility and agility
Why OpenStack for Cloud?
27
Platinum Members
Gold Members
Sponsors

Extending OpenStack for Power Virtualization Management
28
PowerVC Stretches OpenStack to Provide
Enterprise Virtualization Management
Cloud
Infrastructure
Services
Dynamic Provisioning
Server, Storage, Network
Virtualization
Sharing and Over-Commitment
Rapid Provisioning and
De-provisioning
Multi-Tenant
Elasticity and Scale
Self-Service
Commodity HW
Building Blocks
Enterprise
Virtualization
Monolithic Applications
Application Affinity
Capacity on Demand
Vertical Scaled Applications
Steady-State
Management
SAN Storage
System capacity differences
Enterprise Class Systems
Onboarding
Services Catalog
Flexibility Constrained and
Prescriptive
Cloud Management
Billing and Charge-back
Cloud User
IT Admin
PowerVC provides the convergence of what are today different and purpose
optimized approaches
Mobility

PowerVC: Build on OpenStack with IBM Enhancements
29
Cinder Nova Neutron Virtualization Drivers
• Nova drivers for IVM
• Nova drivers for HMC
• Leverage ecosystem to
support broad range of IBM
and non-IBM storage and
network attached to Power
IBM Power Systems
Storage
IBM and 3rd Party
Network
IBM and 3rd Party
AMQP DBMS
New Mgmt Capabilities
• Monitoring & Events
• More granular VM Mgmt
• OVF Image Formats
• Configuration Patterns
Virtualization Mgmt UI
• Simple and Intuitive
• Targeting the IT Admin
New Management APIs
• Virtualization Management
• Monitoring & Events
PowerVC Virtualization Management Console
Platform Provides…
• Virtual Machine Placement
• Workload Aware Mgmt
• Performance Mgmt
• Availability Mgmt
Packaging and Simplification
• Simplified Install and Config
• Intuitive Administration Model
• Focus on day 0/1 TTV
OpenStack API
Security (KeyStone) Scheduler
Images Flavors
API Additions
Monitoring
VM Mgmt
Platform Projects
QuotasOVF
Power Driver Network Drivers
Storage Drivers
IBM DB2

IT Admin Applications
RHEL Linux
POWER8 System
NovaLink
AIX
…
Fiber Channel – NPIV & vSCSI
PowerVM*
Power System
Linux
AIX…
PowerVM
Power System
PowerV
C
AIX
…
PowerVM
x86 System
MCP Linux
HMC
Cinder
Drivers
REST APIs
Power
RHEL Linux
PowerVC
VIOS
VIOS
VIOS
VIOS
VIOS
VIOS
Manage From Linux, Manage Through HMC, Manage To Linux, AIX and IBM i
Storage
Storage
Provider
X86
• Management System Options…
•RHEL Linux on a separate x86 server
•RHEL Linux in a partition on Power
• Managed System…
• Power 6/7/7+/8
• Redundant HMC managed systems
• Novalink for POWER8 systems (optional)
• Multiple redundant VIOS servers
• NPIV, vSCIS and Shared Storage Pool
attached storage
PowerVC typical configuration
30

PowerVC Resources
31
Images
Virtual Machines
Hosts (Physical servers)
Networks
Storage Volumes (and storage providers, fabrics

© Copyright IBM Corporation 2015.32
Features-PowerVC
Product Identifier 5765-VCS
HMC Prerequisite 8.3.0 or 8.4.0
VIOS Prerequisite 2.2.3.52 or 2.2.4.10
POWER8
POWER7/POWER7+
POWER6



Managed VM Type
AIX
IBM i
RHEL (BE or LE)
SUSE (BE or LE)
Ubuntu (LE)
Managed From OS
RHEL 7.1
(Power BE or LE & X86)
Highly available VIOS configs 
Host groups & sophisticated placement 
Storage Supported
vSCSI, Shared Storage
Pools, V7000/SVC, EMC
VNX, EMC VMAX, XIV
US List price per managed core
$80/$120/$160
(Small/Medium/Large)
 PowerVC Standard Edition
Simplified lightweight advanced
virtualized management for any
HMC-managed Power System
PowerVC Standard Edition V1.3.0 Offering Information
PowerVC Standard Edition is bundled with AIX EE so most enterprise clients already
have PowerVC licenses
32

PowerVC – Managed OS
AIX
(6.1 & 7.1)
SLES 11 RHEL
6.4, 6.5 BE
7.1 BE & LE
IBM i
(7.1 TR7 & 7.2)
SLES 12
LE
Ubuntu 14, 15
LE
35

PowerVC Storage Support
Cisco SAN
(IOS 6.2) IBM XIV
EMC VNX EMC VMAX
Image Import / Export
between storage devices
Multiple I/O Groups
VSCSI
(VIOS 2.2.3.4)
Brocade SAN
V7000 &
SAN Volume Controller
Shared Storage Pools
(VIOS 2.2.3.3)
36
IBM DS8870

PowerVC Multi-disk capture and deployment
38
Multi-disk capture and deployment allows capture and
deployment of boot and data volumes
• Works with AIX, IBM i or Linux VMs
• Boot and data volumes can be captured separately and
combined and deployed together
• Disk volumes do not have to be on the same device
• Mirrored boot volumes are captured and deployed
• Up to 64 volumes supported
Deploy
Capture

PowerVC Host Groups
40
Host 4
Host 5 Host 6
Host 1
Host 2 Host 3
Host 7
Host 13 Host 14
Host Groups allow the PowerVC administrator to
create a logical boundary around a group of physical
servers
• Each server can only be in one host group
• Deployment, mobility and remote restart are only
allowed within the group
• Each group has its own placement policy
• Hosts are placed in the default group when added
“PCI” Host Group
“POWER8” Host Group
“Austin” Host Group
Default Host Group
Host10
Host11
Host 12
Host 8 Host 9
“Sandbox” Host Group

PowerVC Advanced Placement
41
Host 5Host 2 Host 7
Host 13 Host 14
The PowerVC scheduler takes the capacity of servers
into account to determine which host to deploy or
relocate VMs to. Hosts with the greatest free CPU or
memory allocation becomes the target of the next VM.
The scheduler can also take host CPU utilization into
account when scheduling VMs
Host10
Host11
Host 8 Host 9
CPU MEMORY
CPU MEMORY
CPU MEMORY
Scheduler support VM placement based on CPU & Memory capacity
and CPU Utilization
Scheduler
choice
Scheduler
choice
Free CPU / Memory Capacity
Host CPU Utilization

PowerVC VM Collocation Affinity and Anti-affinity
42
Host 1 Host 2 Host 3
Affinity and Anti-affinity provide
control over which VMs can be placed
on the same host
- VMs with Affinity must be deployed
to the same host
- VMs with Anti-Affinity must not be
placed on the same physical host
VM with no affinity requirements – can go anywhere within the host group
VMs with affinity – must be placed on the same host
VMs with anti-affinity – cannot be placed on the same host

PowerVC Remote Restart
4343
Host 1 Host 2 Host 3
PowerVC Remote VM Restart enables restarting VMs from a
failed host on another server
• Requires a human decision to perform restart using PowerVC
• Host Group policy controls VM placement
• Supports both PowerVM and PowerKVM
• Requires POWER8 with firmware 8.20
Improved recovery from unexpected system failures

Availability tools coverage
 PowerHA provides complete coverage and lowest recovery times
 PowerVC Remote VM Restart provides additional coverage for
server hardware Issues
Coverage
Hardware
Guest OS
Application
PowerHA
Seconds 5 – 30 minutes
Recovery
Time
VM
PowerVC Remote
VM Restart
44

Cloud-Init for AIX image activation at deployment
 PowerVC V1.2.3 will support CloudInit for image activation on AIX
– Image activation is the process that automatically runs when a new VM image
is deployed to customize the VM instance
• For example, to set the hostname, networking configuration, and SSH keys
– PowerVC formerly only supported the proprietary VSAE activation engine
 CloudInit has become the defacto standard for activation
– Open source project used by OpenStack, AWS and other clouds
– CloudInit supports a much richer activation technology
• Supports passing in customer activation scripts
• Built in modules for Chef, Puppet, and user creation, etc.
– Upstream cloud managers are highly dependent on CloudInit
– Multiple clients have requested CloudIinit support for AIX
– PowerVC has supported CloudInit for Linux deployments since 2014
 PowerVC engineering team worked with the AIX team to deliver
CloudInit for AIX
45

OpenStack Community Release Strategy
46
20172013 2014 2015 2016
Spring Fall SpringFall Spring Fall Spring Fall
Grizzy
4/13
10/13
10/14
4/14
https://wiki.openstack.org/wiki/Releases
4/15
Havana
IceHouse
Juno
Kilo ly
Fully Supported
Security fixes only
OpenStack strategy is move a release
to “Security fixes only” when the next
release (N+1)becomes available.
The release goes to EOL when the
n+2 release becomes available (or the
community decides otherwise)
10/15
Liberty ly

PowerVC Release Strategy Timeline*
47
20172013 2014 2015 2016
Fall Spring Fall Spring Fall Spring Fall Spring Fall Spring Fall Spring Fall Spring Fall Spring
2018 2019 2020 2021
FP
1.2.1
FP
OneYear
Lifespan
18 Month
Lifespan
FP
1.2.0
FP
1.2.2
FP
1.2.3
FP
FP
FP
Two Year Paid
Service Extension
Extended for 3
year life for
1.2.3
*All statements regarding IBM's future direction and intent are subject
to change or withdrawal without notice, and represent goals and objectives only.
Havana
Icehouse
Juno
Kilo
1.3.0
FP
Liberty
Mitaka
‘N”
‘O”
‘P”

PowerVC 1.3.0 Summary Available 4Q 2015
 Enhanced storage support
– Increase size of data volumes
– Support for up to 26 SAN fabrics
– DS8870 storage support (NPIV & vSCSI)
 Exploitation of PowerVC Novalink architecture management interface
– Alternative to HMC for POWER8 servers
– Provides increased management scalability
 Support for PowerVC Multiple Shared Processor Pools
–Improved control for applications that need to control processor capacity for software
licensing
 Dynamic Resource Optimizer automatic workload balancing
– Relocate VM to less loaded servers
– Move server capacity between servers using Enterprise Capacity on Demand
 Based on the OpenStack “Liberty” release
49

PowerVC 1.2.3 Fixpack 2 Multiple Shared Pools support
50
Multiple Shared Pools (Logical Shared Pools)
provide control over that amount of capacity available to
several VMs
- Typically used to control license costs for
middleware such as Oracle DB
- Capacity can flow between the VMs in the pool, but
the aggregate capacity used cannot be more than
the logical pool capacity
VM with no sub capacity requirements – can potentially
use all capacity in the system
VMs that need capacity control
Physical Shared Pool
64 cores
Logical Shared Pool
16 cores

© Copyright IBM Corporation 2015.Host 2
PowerVC V1.3.0 Dynamic Resource Optimizer
5151 Host 1 Host 3
PowerVC Dynamic Resource Optimizer allows for automated rebalancing
of workloads between servers
• Server workload can be automatically balanced two ways:
• Relocating Virtual Machines between servers
• Moving processor capacity between servers using Enterprise
Capacity on Demand
Policy-based automation to balance workloads
Relocate VM
Relocate VM
Move server
Capacity with COD

Workload Management Initial
Placement
Runtime
Optimization
Packing
Pack workload on fewest physical servers
Maximizes usable capacity, reduces
fragmentation, reduce energy consumption
YES
4Q
2015
Striping
Spread workload across as many physical
servers as possible
Reduce impact of host failures, higher
application performance
YES
4Q
2015
CPU
Utilization
Place VMs on the hosts with the lowest CPU
utilization
2Q
2015
4Q
2015
CPU
Balance
Place VMs on the hosts with the most non-
allocated CPU
2Q
2015
4Q
2015
Memory
Balance
Place VMs on the hosts with the most non-
allocated memory
2Q
2015
4Q
2015
Affinity
Affinity specifies that VMs should be placed on
the same host or few hosts
Useful for collocating VMs on the same host(s)
2Q
2015
N/A
Anti-Affinity
Do not place VMs on same host
Useful for ensuring VMs are not collocated
Availability cluster support (e.g. PowerHA)
2Q
2015
N/A
Dynamic
Resource
Optimization
Rebalancing workload across physical hosts by
relocating VMs or using Capacity on Demand N/A
4Q
2015
PowerVC Placement Policies and VM Location Rules
52

Learn more about PowerVC
55
PowerVC LinkedIn Group
https://ibm.biz/powervclink
PowerVC on Facebook
https://ibm.biz/powervcface
PowerVC channel on Twitter
Follow @cloudrancher and hashtag #PowerVC
PowerVC channel on YouTube
http://ibm.biz/powervcyoutube
PowerVC on Service Management Connect…
https://ibm.biz/smcpowervc
PowerVC Hosted Trial – Try out PowerVC in our environment for FREE
https://ibm.biz/powervchosted
Download PowerVC – Download PowerVC for free trial
https://ibm.biz/powervctrial

© Copyright IBM Corporation 2015.56
Cloud Management
Cloud management
• Self-service provisioning
• Virtual systems & applications services
• Subscriber and account management)
• Sophisticated patterns of virtual machines
• Management interface: Cloud Manager With
OpenStack for Power(SCE), IBM Cloud
Orchestration
Cloud
PowerVC
HMC OR PowerKVM

Conceptual View:
Cross Platform Cloud Management based on OpenStack
57
Storage
Management
Networking
Management
PowerVM
IBM Cloud Manager with OpenStack
Upward Integration via OpenStack or proprietary APIs
Power HMC
Power
Compute
HMC
OpenStack APIs
X86 Compute
and
Chassis
VMware
KVM
Power
Proprietary hardware
management
PowerVC
KVM
X86HyperV
ManagedResources
Cloud
Management
Hypervisors
Platform
Management

Virtualization/Cloud Management
for Power Systems
Manage Virtualization
 Simple UI and Setup
 Resize VMs and Migration
 Capture & Deploy VMs
 Policies for placement
 Manages PowerVM &
PowerKVM
Basic Cloud
 Self-Service Portal with Process
Automation
 Metering and Billing of Usage
 Catalog of VMs and Images
 Open access to OpenStack APIs
 Manages Hybrid Private Clouds
Advanced Cloud
 Capacity management
 Advanced usage
metering/accounting
 Virtual system and application
patterns
 Runbook Automation
 Manages Hybrid Private/Public
Clouds
Increasing Automation & Function
IncreasingbusinessOptions
Advanced
Virtualization Management
IBM Cloud Orchestrator
IBM Cloud Manager with
OpenStack
58

VMWare vRealize now supports Power and System z
Provisions & orchestrates virtualized IBM Power & z Systems
workloads
• Infrastructure as a Service (IaaS)
vRA passes workload management
requests via OpenStack API’s (Juno) to
IBM’s PowerVM, PowerKVM, z/VM and
KVM on IBM z
• Platform as a Service (PaaS)
Install scripted applications and
workflows via IBM Cloud Builder
Services
KVM on z
IBM Cloud
Manager
(OpenStack)
PowerVC
PowerVM
VMware
vRA 6.2
zVM
Power
KVM
AIX
RHEL
SUSE
RHEL RHEL
SUSE
SUSE
SUSE
**
** PowerKVM provisioning via PowerVC planned for 1Q 2016
Ubuntu
*Testing/verification of IBM i is planned for later in 4Q
*IBM i
Ubuntu

Thank You
62
Cloud Manager with
OpenStack for Power

PowerVC and Power Systems Cloud Trends

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (20)

Andere mochten auch

Andere mochten auch (20)

Ähnlich wie PowerVC and Power Systems Cloud Trends

Ähnlich wie PowerVC and Power Systems Cloud Trends (20)

Mehr von Jay Kruemcke

Mehr von Jay Kruemcke (11)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

PowerVC and Power Systems Cloud Trends