A talk by Shaun Murakami and Phil Estes at the OpenStack Summit Paris, Fall 2014. We look at real-world scenarios deploying and managing workloads in a multi-platform environment of compute architectures including IBM System z (traditional mainframe), POWER, and Intel architectures. Moving beyond a homogeneous data center to a mix of enterprise architectures adds potential complexities around hypervisor support, deployment capabilities, and management of disparate workloads--of which some might be CPU-centric while others are not.

1. Platinum Member of
OpenStack FoundationOpen by Design
Accelerating Enterprise OpenStack
© 2014 IBM Corporation
Beyond x86:
Multi-platform management with OpenStack
Phil Estes STSM & Lead Architect, IBM Cloud Performance
Shaun Murakami Senior Architect, IBM Cloud Performance
estesp@us.ibm.com @estesp
stmuraka@us.ibm.com @stmuraka

2. © 2014 IBM Corporation
2
Open by Design
Platinum Member of
OpenStack Foundation
Where are you on the OpenStack continuum?
Single-node
Multi-node
Distributed

3. © 2014 IBM Corporation
3
Open by Design
Platinum Member of
OpenStack Foundation
Single-node
Multi-node
Distributed
Single-node deployment
All-in-one
Devstack, commonly
Personal development system

4. © 2014 IBM Corporation
4
Open by Design
Platinum Member of
OpenStack Foundation
Multi-node deployment
Single service instances (no HA)
Multiple compute nodes
Multiple compute types
Single-node
Multi-node
Distributed

5. © 2014 IBM Corporation
5
Open by Design
Platinum Member of
OpenStack Foundation
Distributed deployment
Failover service instances (HA)
Multiple compute types
Hopefully automated/repeatable
Single-node
Distributed
Multi-node

6. © 2014 IBM Corporation
6
Open by Design
Platinum Member of
OpenStack Foundation
What concepts does OpenStack provide
to manage distributed, distributed cloud
deployments?
What are cells, regions, and availability zones, and how do I use them?

7. © 2014 IBM Corporation
7
Open by Design
Platinum Member of
OpenStack Foundation
A cell comprises a
single API endpoint for
compute, allowing for
more fine-grained
scheduling across a
group of compute
nodes
OpenStack Segregation Constructs
Cell
Region
Availability Zone
Host Aggregate
Discrete regions contain
fully separate API
endpoints and provides
no coordination
between regions.
Regions can be used to
segregate specific
physical geographies or
datacenters
Availability zones are
used to handle logical
separation within your
nova deployment for
physical isolation or
redundancy. Zones are
useful for implementing
HA patterns at the
application level
Host aggregates allow
for segregated
scheduling given a
group of compute hosts
with common physical
features (e.g. storage
backend, specific
hardware capability)

8. © 2014 IBM Corporation
8
Open by Design
Platinum Member of
OpenStack Foundation
OpenStack Segregation Example
Cell
Region 1
Availability
Zone 1
Host
Aggregate 1
Rack
Controller
Compute
Compute
Compute
Compute
Compute
Compute
Rack
Controller
Compute
Compute
Compute
Compute
Compute
Compute
Availability
Zone 2
API VIP
Host
Aggregate 2
Region 2
Cell
Availability
Zone 1
Host
Aggregate 1
Rack
Controller
Compute
Compute
Compute
Compute
Compute
Compute
Rack
Controller
Compute
Compute
Compute
Compute
Compute
Compute
Availability
Zone 2
API VIP
Host
Aggregate 2

9. © 2014 IBM Corporation
9
Open by Design
Platinum Member of
OpenStack Foundation
Distributed deployment
Multiple platforms ?
Single-node
Distributed
Multi-node

10. © 2014 IBM Corporation
10
Open by Design
Platinum Member of
OpenStack Foundation
More than 50% of all traditional x86 server
workloads virtualized - 451 Research, Gartner
KVM
Xen
Hyper-V
VMWare
Docker
x86_64
Architecture Hypervisors

11. © 2014 IBM Corporation
11
Open by Design
Platinum Member of
OpenStack Foundation
Why do we need other platform
architectures in the cloud?
Can’t we finish the migration to cloud on commodity x86 hardware?

12. © 2014 IBM Corporation
12
Open by Design
Platinum Member of
OpenStack Foundation
Optimization
Systems of Record
Innovation
Systems of Engagement

13. © 2014 IBM Corporation
13
Open by Design
Platinum Member of
OpenStack Foundation
Customer requirements demand other platform
architectures in the cloud.
IBM System z
POWER Systems
ARM Microservers

14. © 2014 IBM Corporation
14
Open by Design
Platinum Member of
OpenStack Foundation
Canonical adds ARM 64-bit server support and
OpenStack Icehouse in Ubuntu 14.04LTS
KVM64-bit ARM
Architecture Hypervisors
Microservers, while fairly new on the scene, hold promise for significant data center size
reduction and energy efficiency. Pooling and shared resource for media serving, among
other uses, have a predicted 62% CAGR over the next four years.

15. © 2014 IBM Corporation
15
Open by Design
Platinum Member of
OpenStack Foundation
POWER8 LE support added to Canonical’s Ubuntu
14.04LTS; PowerVM supports RHEL and SLES
PowerVM
KVM – available 04/14
Docker
POWER
Architecture Hypervisors
POWER CPU and memory architecture perfect fit for big data and analytics processing.
IBM Watson runs on the POWER architecture; traditional install base in ERP and CRM.

16. © 2014 IBM Corporation
16
Open by Design
Platinum Member of
OpenStack Foundation
Traditional z workloads transact a large percentage
of global financial and enterprise data today
zVM (LPAR) – since 1987
zKVM
Docker
System z
Architecture Hypervisors
Visa relies on System z for global transaction processing. Holiday season workloads at
Visa—handled by System z—reach upwards of 11,000 transactions per second.

17. © 2014 IBM Corporation
17
Open by Design
Platinum Member of
OpenStack Foundation
IBM System z
Performance
Availability
Security
Performance and availability needs require co-
locating new zLinux cloud workloads with existing
extreme-throughput transactional systems.
• Designed for extreme scalability: sharing of high-speed network, CPU, and memory
• Core consolidation rates on average of 30-to-1
• Multi-system clustering; ability to assign 32 physical IFLs per LPAR
• System z designed from day one with high availability and failover implemented
• System z has highest SLA compliance rate of any platform in existence
• Availability components exposed in all higher “layers” – e.g. Linux networking
• LPAR design of hypervisor has complete isolation from all other LPARs
• Significant capabilities for logging, monitoring, auditing built into the system

18. © 2014 IBM Corporation
18
Open by Design
Platinum Member of
OpenStack Foundation
An example: Colocation benefits from zEnterprise architecture"
4 CPUs
POWER
Separate
Physical
Servers
Separate LPARs "
Same server
3,650 tps
4,300 tps
WAS Linux
DB2 zOS
2 CPUs
System z
4 CPUs
System z
WAS Linux
DB2 zOS
2 CPUs
System z
An 18% performance increase!

19. © 2014 IBM Corporation
19
Open by Design
Platinum Member of
OpenStack Foundation
Challenge:
• Hundreds of standalone servers; constantly increasing IT costs
• Growing system complexity and incompatibility, maintenance and
licensing issues
• Customer service and time to deploy suffering as a result
Solution:
Consolidate distributed servers and migrated mission-critical SAP and
DB2-based applications to an IBM System z running zLinux, zOS & zVM
Consolidation cut energy costs from 40%-80%
Baldor: reduced data center floor space from 6,000 to 1,000 sq. ft.
Both experienced significant reduction in system administration and maintenance costs
Customers: Consolidation on z yields significant IT benefits

20. © 2014 IBM Corporation
20
Open by Design
Platinum Member of
OpenStack Foundation
Incorporating multi-platform compute with OpenStack
[ zLinux on OpenStack ]
Today
Future
OpenStack
Controller
x86
Compute
(Proxy)
Other x86
Compute
{
{
Z Region
x86 Region
zLPAR
xCAT
zHCP
zLinux
zLinux
- OpenStack region per LPAR
- Proxy through an x86 node
- Communicates with xCAT to ZHCP
- Scheduler and CP provision image
OpenStack
Controller
Nova
Compute
zLPAR+KVM
zLinux
zLinux
Standard nova à libvirt à KVM

21. © 2014 IBM Corporation
21
Open by Design
Platinum Member of
OpenStack Foundation
Incorporating multi-platform compute with OpenStack
[ POWER on OpenStack ]
PowerVM
POWER KVM
OpenStack
Controller
IVM
Linux
AIX
Nova
Compute
compute_driver=nova.virt.powervm.PowerVMDriver
powervm_mgr_type=ivm
OpenStack
Controller
PowerKVM
Linux
Ubuntu
Nova
Compute
Standard nova à libvirt à KVM
- No HMC Support
- No IVM
- No AIX/i OS images

22. © 2014 IBM Corporation
22
Open by Design
Platinum Member of
OpenStack Foundation
What next?
Where can I find out more about OpenStack on POWER and z?
I (or my customers) already have POWER and/or z hardware? What’s required?
Check out RunAbove, providing
OpenStack-accessible POWER8
KVM compute nodes:
http://labs.runabove.com/power8/
• Come talk to us at the IBM booth and check out a POWER8 server
• Check out our OpenStack offerings that fully support managing z and POWER
compute: Cloud Manager with OpenStack and IBM Cloud Orchestrator
• IBM Hosted Orchestrator beta and RunAbove clouds have accessible z and
POWER compute today (SoftLayer will also be offering POWER compute)
• z10, zEnterprise EC12 and BC12, zEnterprise 114 and 196 hardware all supported, zVM V6.3 or greater
• PowerVM requires POWER7 or POWER8 systems, with IVM
• PowerKVM requires S812L or S822L POWER8 servers only; guests supported: RHEL7 (BE), SLES12 (LE),
Ubuntu 14.04, 14.10 (LE); no support for HMC
• Lots of detailed help and configuration guides available online: https://ibm.biz/BdEqev

23. © 2014 IBM Corporation
23
Open by Design
Platinum Member of
OpenStack Foundation
IBM Technical Sessions
IBM Sessions on Monday, November 3rd
15:20
R.251
When Disaster Strikes the Cloud: Who, What, When, Where and How to recover Ronen Kat, Michael Factor, and Red Hat
11:40
A.Blue
IPv6 Features in OpenStack Juno Xu Han Peng, Comcast, and Cisco
15:20
R252
Why is my Volume in 'ERROR' State!?! An Introduction to Troubleshooting Your Cinder Configuration Jay Bryant
16:20
A.Blue
Group Based Policy Extension for Networking
Mohammad Banikazemi, Cisco, Midokura, and
One Convergence
IBM Sessions on Tuesday. November 4th
11:15
R252
The perfect match: Apache Spark meets Swift. Gil Vernik, Michael Factor, and Databricks
15:40
R242
Docker Meets Swift: A Broadcaster's Experience
Eran Rom, and RAI
16:40
Maillot
User Group Panel: India, Japan, China Ying Chun Guo, Guang Ya Liu, Qiang Guo Tong
14:50
Passe
A Practical Approach to Dockerizing OpenStack High Availability
Manuel Silveyra, Shaun Murakami, Kalonji
Bankole, Daniel Krook
IBM Sessions on Wednesday, November 5th
09:00
R241
Monasca DeepDive: Monitoring at scale Tong Li , Rob Basham, HP and Rackspace
09:00
R242
Beyond 86: Managing multi-platform environments with OpenStack Shaun Murakami, Philip Estes
09:50
R253
Troubleshooting Problems in Heat Deployments
Fabio Oliveira,Ton Ngo,Priya Nagpurkar,
Winnie Tsang
11:50
R251
Keystone to Keystone Federation Enhancements for Hybrid Cloud Enablement
Steve Martinelli, Brad Topol, CERN, and
Rackspace
17:50
R253
Practical advice on deployment and management of enterprise workloads Jarek Miszczyk, Venkata Jagana

24. © 2014 IBM Corporation
24
Open by Design
Platinum Member of
OpenStack Foundation
IBM Sponsored Sessions on Wednesday, November 5th
9:50 in Room 243
Step on the Gas: See how Open Technologies are driving the future of the enterprise
Todd Moore, Director, Open Technologies and Partnerships
David Lindquist, Chief Technology Officer / Vice President Strategy and Architecture
11:50 Room 212/213
IBM and OpenStack: Collaborations beyond the code
Manuel Silveyra, Daniel Krook
13:50 Room 212/213
A Use Case Driven view of IBM’s OpenStack based Offerings
Moe Abdula, Vice President of Cloud Strategy
14:40 Room 212/213
IBM OpenStack Offerings in Action
Moe Abdula, Vice President of Cloud Strategy

25. © 2014 IBM Corporation
25
Open by Design
Platinum Member of
OpenStack Foundation
Learn more at these IBM sponsored sessions on Wednesday:
9:50 Room 243 Step on the Gas: See how Open Technologies are driving the
future of the enterprise
11:50 Room 212/213 IBM and OpenStack: Collaborations beyond the code
1:50 Room 212/213 A Use Case Driven view of IBM’s OpenStack based Offerings
2:40 Room 212/213 IBM OpenStack Offerings in Action
Stop by the IBM Booth (B4)
Demos, games and FREE tee
shirt.