Introduction to OpenStack and Building Highly-Available clouds

1. OpenStack 101
Building a Highly Available
Cloud
Rick Ashford
Sr. Technical Specialist
rashford@suse.com

2. OpenStack 101

3. 3
Why an Open Source Cloud?
Drivers Concerns
Cost Savings
Open Standards
No Vendor Lock-In
Portability
Flexibility
Lack of Support
Security
Ecosystem
Integration
Maturity

4. 4
The OpenStack Transformation
• Leading open source project for building IaaS clouds
• Active developer community
• Rapid innovation: 2 integrated projects to 10
• Massive industry ecosystem
• Growing enterprise adoption
• OpenStack Foundation ensures long-term viability

5. 5
What is OpenStack?

6. 6
What is OpenStack?
You are not installing a
single project. You are
coordinating the
installation of multiple
inter-dependent projects

7. 7
Cheat Sheet
What do all these names mean?
Generic Project
Compute Nova
Identity Keystone
Image Glance
Block Storage Cinder
Network Neutron
Object Storage Swift (or Ceph)
Orchestration Heat
Telemetry Ceilometer
Dashboard Horizon
Database Trove

8. 8
What is OpenStack?
Not something you
just drop off at the
edge of the driveway
and take off.

9. Why SUSE?

10. 10
Linux is free! As long
as your time is worth
nothing to you.

11. 11
http://blog.adamspiers.org/2014/11/05/ruler-of-the-stack/

12. Management
(Crowbar, Chef, TFTP, DNS, DHCP)
12
OpenStack Distribution
Billing VM Mgmt Image Tool Portal App Monitor Sec & Perf
Cloud
Orchestration
(Heat)
Dashboard
(Horizon)
Cloud APIs
(OpenStack and
EC2)
Identity
(Keystone)
Images
(Glance)
Compute
(Nova)
Hypervisor
Operating System
Physical Infrastructure: Switches, Storage
VMware, Hyper-V
OpenStack Icehouse
Object
(Swift)
Telemetry
(Ceilometer)
Network
(Neutron)
Block
(Cinder)
Adapters Adapters
SUSE Cloud Adds
Required
Services
RabbitMQ
Postgresql
Install Framework
SUSE
Manager
SUSE
Studio
Xen, KVM
SUSE Linux Enterprise Server 11 SP3
SUSE Product
Rados
RBD
RadosGW
Ceph
Adapters
Highly Available Services
SUSE® Cloud 4
Physical Infrastructure: x86-64, Switches, Storage
Partner Solutions

13. High-Availability
Considerations

14. 14
High Availability for OpenStack
● First question: what are we trying to
protect?
● Control Plane
● Guests

15. 15
High Availability Directions
• Control Plane
‒ Hot standby for Control Nodes
‒ Ensures that cloud continues to operate
• Guest vs. Server
‒ Cloud 101 – Plan for infrastructure failure, or
‒ Enterprise 101 – build a reliable infrastructure
• High availability guests
‒ Use high-availability tools in VMs
‒ Failover VM is physically separated
‒ Application does not need to be changed
• High availability compute nodes
‒ Use high-availability tools on physical nodes
‒ Failover machine is in same availability zone, but could be geographically different
‒ All workloads on server are backed up

16. 16
OpenStack Distribution Components

17. 17
Component failure impact
• Admin server
‒ New cloud nodes require manual addition and configuration
‒ Currently no ability to rediscover existing nodes on restart
‒ No impact on currently operating cloud
• Control node
‒ Cannot start or stop guest instances
‒ No ability to rediscover existing nodes or guest VMs on restart
‒ No impact on currently deployed instances
• Compute Node
‒ Loss of VMs on that node
‒ Recovery is by restart and re-provisioning of physical server
‒ Can be mitigated through application design

18. 18
Component failure assessment
• Control Node
‒ Highest priority
‒ Recovery realistically requires complete cloud restart
• Compute Node
‒ Application level recovery is normal practice for existing clouds
‒ Not existing “enterprise” expectation, but workaround exists for
new workloads
• Admin Server
‒ Least impact on deployed system
‒ Operation can continue with no impact on end users

19. 19
Cloud Structure
Control VM VM VM VM ... VM VM VM VM
Node
Cloud Orchestration
Host
Server
Host
Server
Host
Server
Host
Server
Host
Host
...
Server Server

20. Control VM VM VM VM ... VM VM VM VM
Node
Control
Node
20
Cloud Structure – HA Control Cluster
Host
Server ...
Zone A Zone B
Control
Cluster
Cloud Orchestration
Host
Server
Host
Server
Host
Server
Host
Server
Host
Server

21. What about the workloads?

22. Control VM VM VM VM ... VM VM VM VM
Node
22
Cloud Structure – Availability Zones
Cloud Orchestration
Host
Server
Host
Server
Host
Server
Host
Server
Host
Host
...
Server Server
Zone A Zone B

23. Control VM VM VM VM ... VM VM VM VM
Node
Control
Node
Host
Server ...
Control
Cluster
Zone A High Availability Cluster Zone B 23
Cloud Structure – Host Cluster
Cloud Orchestration
Host
Server
Host
Server
Host
Server
Host
Server
Host
Server

24. Control VM VM VM VM ... VM VM VM VM
Node
Control
Node
24
Cloud Structure – VM Cluster
High Availability Cluster
Host
Server ...
Zone A Zone B
Control
Cluster
Cloud Orchestration
Host
Server
Host
Server
Host
Server
Host
Server
Host
Server

25. Cluster Architecture

26. Network
Links Client
26
3 Node Cluster Overview
VM
1
Apache
IP
Host
cLVM2+OCFS2
DLM
Pacemaker
Corosync + openAIS
VM
2
Host Host
s
Storage

28. Unpublished Work of SUSE. All Rights Reserved.
This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE.
Access to this work is restricted to SUSE employees who have a need to know to perform tasks within the scope of
their assignments. No part of this work may be practiced, performed, copied, distributed, revised, modified, translated,
abridged, condensed, expanded, collected, or adapted without the prior written consent of SUSE.
Any use or exploitation of this work without authorization could subject the perpetrator to criminal and civil liability.
General Disclaimer
This document is not to be construed as a promise by any participating company to develop, deliver, or market a
product. It is not a commitment to deliver any material, code, or functionality, and should not be relied upon in making
purchasing decisions. SUSE makes no representations or warranties with respect to the contents of this document,
and specifically disclaims any express or implied warranties of merchantability or fitness for any particular purpose. The
development, release, and timing of features or functionality described for SUSE products remains at the sole
discretion of SUSE. Further, SUSE reserves the right to revise this document and to make changes to its content, at
any time, without obligation to notify any person or entity of such revisions or changes. All SUSE marks referenced in
this presentation are trademarks or registered trademarks of Novell, Inc. in the United States and other countries. All
third-party trademarks are the property of their respective owners.

29. Thank you.
33
Call to action line one
and call to action line two
www.calltoaction.com