SUSE Cloud 5
Private Cloud based on OpenStack
Michał Jura
Senior Software Engineer
Linux HA/Cloud Developer
[email protected]
=
New solutions emerge:
Infrastructure-as-Service Cloud
SUSE Cloud
Why OpenStack?
Project History
• Provide components for Infrastructure-as-a-Service
• Started by Rackspace and NASA in July 2010
• Currently used for example by CERN
• Today: more than 500 companies involved in the
OpenStack ecosystem (including SUSE)
• Eleven releases so far (Austin, Bexar, Cactus, Diablo,
Essex, Folsom, Grizzly, Havana, Icehouse, Juno, Kilo)
• Next release: Liberty
• Under development: Mitaka
How is SUSE Participating?
Platinum Member Alan Clark
first Chairman of the Board
Promotion in
openSUSE Community
SUSE
®Cloud Overview
SUSE Cloud
SUSE Cloud is an open source software solution based on
the OpenStack and Crowbar projects that provides the
fundamental capabilities for enterprises to deploy an
Infrastructure-as-a-Service Private Cloud
End
Users
Self Service Portal
Image
Repository
APIs
Automated
●
Configuration
●
Optimized
Deployment
APIs Pool of Virtualized Servers
(Compute Storage Nodes)
OpenStack Distribution
Billling VM Mgmt Image Tool Portal App Monitor Sec & Perf
Cloud
Management
Orchestration
(Heat)
Dashboard
(Horizon)
Cloud APIs
(OpenStack and
EC2)
Required
Services
Message Q
Database
AUTH
(Keystone) Images
(Glance)
Hypervisor Xen, KVM Vmware, HyperV
Compute
(Nova)
Operating System
Physical Infrastructure: x86-64, Switches, Storage OpenStack Juno Management Tools OS and Hypervisor
Object
(Swift) Network
(Neutron)
Adapters
Block
(Cinder)
Adapters
Telemetry
(Ceilometer)
Install Framework
Physical Infrastructure SUSE Cloud Adds
Required
Services
RabbitMQ
Postgresql
Install Framework (Crowbar, Chef, TFTP, DNS, DHCP)
Hypervisor SUSE
Manager SUSE
Studio
Hypervisor Xen, KVM
SUSE Linux Enterprise Server 12
SUSE Product
Physical Infrastructure: x86-64, Switches, Storage
Billling Portal App Monitor Sec & Perf
Adapters Adapters Vmware, HyperV
Partner Solutions Ceph
Rados RBD
RadosGW
SUSE
®Cloud 5
SUSE Cloud Controller
• State Database (PostgreSQL)
• Image Service (Glance) for managing virtual
images
• Identity (Keystone), providing authentication and
authorization for all SUSE Cloud services
• Dashboard (Horizon), providing the Dashboard,
which is a user Web interface for the SUSE Cloud
services
• Nova API and scheduler
• Message broker (RabbitMQ)
SUSE Cloud Storage Nodes
• Pool of machines providing storage
• Object storage provided by swift or ceph
‒ optional
• Block storage provided by Nova Volume or ceph
‒ Multiple backends
SUSE Cloud and SUSE Storage
Ceph Project
• Ceph Overview
‒ Unified cloud storage ‒ object and block in a
single system
‒ An alternative for Swift, integrated with SUSE
Cloud Block Storage
• SUSE Cloud and Ceph
‒ Integrates with Nova for provisioning
‒ ReSTful API
‒ SUSE Cloud full support
SUSE Cloud Compute Nodes
• Pool of machines where instances run
• Equiped with RAM and CPU
• SUSE Cloud Compute (nova) service
‒ Setting up, starting, stopping, migration of VM's
SUSE Cloud 5 Hypervisor Support
• Linux hypervisors coming with SUSE Cloud 5:
‒ KVM
‒ Xen
‒ Docker
‒ ZVM (SUSE OpenStack Cloud 6)
• Microsoft Hyper-V
• VMware vSphere and Vmware NSX
• Mixed hypervisor support: different hypervisors in the
same cloud
• Baremetal install via Crowbar of nodes – incl. KVM,
OpenStack Neutron with VMware NSX
OpenStack Nova with VMware vCenter
SUSE Cloud Admin Server
• Installation Framework
‒ Physical server orchestration
‒ Chef and Crowbar open source projects
• Mission: “A Zero Touch Cloud Installer”
‒ Servers in boxes to full function cloud in under two hours
‒ Bare metal install including BIOS and RAID config
• Users Choose How Their System is Configured
(“barclamps”)
‒ Ongoing Operations Model (DevOps for Clouds)
‒ Leverages & Wraps Opscode Chef
Hours Days
Parameters
Components
6471
16
2
SUSE Cloud Admin Server - Workflow
Admin Node Cloud Node
Status (post)
PXE Boot
Run List
Config
State Machine
Software Mirror
DHCP/TFTP
Crowbar Chef
Server
Apps Apps
Network
Config Network
Config
SUSE Linux
Enterprise Server
Hardware Config
(via image discovery)
Chef Client
Chef Client
Chef ClientAutoYAST
SUSE Cloud 5 Highlights
• Based on OpenStack Juno
‒ Orchestration
‒ Telemetry (metering, measuring)
‒ Trove (DataBase as a Service)
• Features
‒ Docker support - in addition to KVM, Xen, VMware, Hyper-V
‒ Networking and block storage adapter support
‒
Cisco Unified Computing System
‒
Cisco Nexus, EMC, VMware NSX and others
‒ Full support for Ceph
• Platform for High Availability
SUSE Cloud HA
High Availability
Minimize system downtime
Minimize data loss
High Availability for SUSE Cloud
• First question: what are we trying to protect?
‒ Administration Server
‒ Control Plane
‒ Guests
SUSE Cloud components
HA Setup
SUSE Cloud components
Development approach
• Use SLE HA Components
‒ Pacemaker cluster
‒ Create single Pacemaker barclamp
‒ Modify existing barclamps to enable HA deployments
‒ HAproxy as load balancer
• Postgres
‒ Use DRBD + Pacemaker
• Control Node SKUs will include entitlement to SLE HA
HA: Simplified Structure
Control Node 1 Control Node 2
DRBD
PostgreSQL
RabbitMQ
Keystone
Glance
Nova
Dashboard
Neutron
HA: Cloud Diagram
Controller
Cluster Data
Cluster Network
Cluster Compute
Nodes
192.168.124.8{7,9}
192.168.124.10
Crowbar
Compute 1
Compute 2
192.168.130.1{1,2}
192.168.126.{2,3}
192.168.124.8{1,3}
192.168.130.1{0,-}
192.168.126.{8,-}
192.168.124.8{4,2}
192.168.126.{5,6}
192.168.124.8{5,6}
192.168.130.1{3,4}
High Availability
Component HA type
Data Base Active/Passive
RabbitMQ Active/Passive
Keystone Active/Active
Glance Active/Active
Cinder Active/Active
Neutron Active/Active
Nova-Service Active/Active
Horizon Active/Active
Heat Active/Active
Ceilometer Active/Active
Questions?
Dziękuję za uwagę!
Call to action line one
and call to action line two
www.calltoaction.com
SUSE w Polsce
ul. Postępu 21
+48 22 537 5020
Infolinia 800 22 6685
Dołącz do nas:
www.opensuse.org
Unpublished Work of SUSE LLC. All Rights Reserved.
This work is an unpublished work and contains confidential, proprietary and trade secret information of SUSE LLC.
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.
