RED HAT OPEN HYBRID CLOUD

1
RED HAT OPEN HYBRID CLOUD Workshop for
NIC OPEN CLOUD INFRASTRUCTURE BUILT ON RED HAT
TECHNOLOGIES
2
(No Transcript)
3

• Red Hat Enterprise Virtualization
• RHEV 3.2

4
Red Hat Enterprise Virtualization
5
Red Hat Enterprise Virtualization Architecture
6
Virtualization Performance specVirt
http//www.spec.org/virt_sc2010/results/res2012q4/
7
KVM Virtualization Scalability

• Up to 160(!) virtual cpu per single VM (RHEL6.3)
• Up to 2TB RAM per single VM (RHEL6.3)
• Up to 64k block devices using virtio-scsi
  (RHEL6.3-TP)
• Largest cluster of virtualization hosts w/ RHEV
• Accommodates high end demanding workloads
  facilitating bare-metal to virt use cases

8
Red Hat Enterprise Virtualization Manager Overview

• Centralized virtual infrastructure management
  (hosts, virtual machines (VMs), networking,
  storage, templates, etc.)
• Designed for large scale (500 hosts and 10,000
  VMs)
• Administrative interfaces include GUI, RESTful
  API with session support, Linux CLI, Python SDK

9
RHEV Features since 2.1 (Nov 2009)
 Feature Description
High Availability  Restart guest VMs from failed hosts automatically on other hosts
Live Migration  Move running VM between Hypervisor hosts with zero downtime
System Scheduler  Continuously load balance VMs based on resource usage/policies
Power Saver  Concentrate virtual machines on fewer servers during off-peak hours
Maintenance Manager No downtime for virtual machines during planned maintenance
Image Management Template based provisioning, thin provisioning and snapshots
Monitoring Reporting  For all objects in system VM guests, hosts, networking, storage etc.
10
RHEV 3.1 Highlights
11
RHEV 3.2 Highlights
12
RHEV 4.0 Planning
13
Integrating Red Hat Storage and Virtualization

• Live Virtual Machine Image Store
• RHEV Image store
• Supported as a pluggable file-system RHEV storage
  domain
• Multi-master Geo replication (Tech Preview
  RHS 2.1)
• Simultaneous writes to multiple geographically
  separated sites handled
• Eventually consistent semantics
• Conflict resolution policy to determine which
  writes win

14
Support from Hardware Partners

• RHEV 3.2 released (11. June 2013)
• Support from hardware partners and analysts
• Cisco
• HP
• IBM
• Dell
• IDC

15
Red Hat OpenStack
16
OpenStack and Red Hat The Perfect Combination
OPENSTACK - The ubiquitous Open Source cloud
computing platform for the Future RED HAT
- The Open Source Development Power House
Corporate contributions to OpenStack

• Heavily engaged in OpenStack community since 2011
• Established leadership position in community
• Both in terms of governance and technology
• Including PTLs on Nova, Keystone, Heat and
  Ceilometer
• Largest contributor to Grizzly
• Largest contributor to Havana

(04 APR to 16 OCT 2013)
NUMBER OF COMMITS
RED HAT
COMPANY / ORGANIZATION
Source Bitergia OpenStack Havana Analysis,
October 17, 2013 blog.bitergia.com/2013/10/17/the-
openstack-havana-release
17
What is OpenStack?

• OpenStack provides a massively scalable public
  cloud-like platform for managing and deploying
  cloud-enabled workloads
• Modular in nature, OpenStack is a combination of
  open source projects that control processing,
  storage, and networking resources
• OpenStack relies entirely on Linux as sole
  platform for workloads. Also vast majority of
  implementations rely on KVM
• In OpenStack's two year history, more than 200
  companies have joined the project including Red
  Hat in September 2011
• In a recent CIO Quick Pulse survey, 64 of IT
  Managers are either deploying or considering
  OpenStack

With tremendous momentum and industry backing,
OpenStack is poised to become a major factor in
the emerging cloud system software market.
(IDC, July 2013)
18
OpenStack Powers Demanding Production Workloads
Worldwide
Web / SaaS/ eCommerce
Academic / Research / Government
Information Technology
Cloud Hosting / MSP / Telco
http//www.openstack.org/user-stories/
19
OpenStackCloud Infrastructure forCloud-Enabled
Workloads

• Modular architecture
• Designed to easily scale out
• Based on (growing) set of core services

20
Havana ReleaseOctober 2013

• Over 920 contributors to Havana, 40 increase
  over Grizzly release
• 400 new features added across compute, storage,
  networking and cross-platform services
• Major enhancements orchestration (Heat),
  monitoring (Ceilometer)
• 150 organizations contributed, 54 increase over
  Grizzly
• The OpenStack Foundation reportsthat 300 known
  enterprises haveadopted OpenStack as of Oct 2013
• Significant developer and customer traction that
  will only intensify withIcehouse release (April
  14) and beyond
• Red Hat will continue to help spearhead this
  momentum

21
OpenStack CommunityHistory Timeline
Austin October 2010 - Initial release - Object
storage production-ready - Compute in testing
Bexar February 2011 - Compute
production-ready - Initial release of Image
service - Focus on installation and deployment
Cactus April 2011 - Focus on scaling
enhancement - Support for KVM/QEMU, XenServer,
Xen, ESXi, LXC
Havana October 2013 - 400 new features - Heat
(orchestration) and Ceilometer (metering)
became core projects - Participation
from 150 organizations, a 54
increase over Grizzly
Diablo September 2011 - First production-ready
release
Essex April 2012 - Dashboard and Identity added
to core - Quantum incubated
Folsom October 2012 - Quantum added to core -
Cinder added to core
Grizzly April 2013 - Ceilometer and Heat
incubated - Focus on upgrade support
22
Red Hat OpenStack
23
Red Hat Community FocusHavana Release

• Broad and deep contributions to all core and
  incubating OpenStack projects 69 projects total
  87 engineers committing code

http//stackalytics.com/?releasehavanametriccom
mitsproject_typeopenstackcompanyredhat
24
Upstream community innovation -gt free project
integration -gt productization
25

• Making OpenStack consumable by developers POC
• Red Hat's free community OpenStack distribution
• Binary packaged for Red Hat Enterprise Linux and
  derivatives
• Audience Community of users, developers,
  technologists
• Six month lifecycle with limited updated follows
  upstream cadence
• No commercial support, no certifications, no
  ecosystem
• Is like Fedora is to Red Hat Enterprise Linux
• Download and community at openstack.redhat.com

26
Red Hat Enterprise Linux OpenStack Platform

• Enterprise grade OpenStack deployment with
  ecosystem, lifecycle, support that customers
  expect from Red Hat
• Based on RHEL and includes enhancements and
  required fixes in both OpenStack and RHEL
• Enterprise hardened OpenStack code
• Longer supported lifecycle
• includes bug fixes, security errata, selected
  backports
• Certified ecosystem (Red Hat Certified OpenStack
  Partner program and Red Hat Enterprise Linux
  ecosystem)
• Full support and Certifications for RHEL and
  Windows guest-based workloads
• Simplified installation / setup for large configs
  (incl. Neutron firewall)

27
Red Hat Enterprise Linux OpenStack Platform
Optimizations Impact

• Examples of RHEL optimized enablers for
  OpenStack
• KVM virtualized guest performance
• SELinux security policies for guest isolation
• Network virtualization (Neutron enablers)
  namespaces, OVS (opensvwitch), GRE and VXLAN
  tunneling, VLAN tagging
• Identity management for users, roles, and Active
  Directory integration
• Runtime languages support i.e. Python
• Volume management i.e. optimized snapshots
• The pairing of the Linux operating system and
  OpenStack is so tight that Red Hats combination
  can most effectively support functionality,
  performance, security, and ecosystem support

28
RHEL-OSP Product Release Cadence

• Shipped June 2013 (Grizzly RHEL 6.4)
• Will be updated in December 2013 per Havana based
  release RHEL 6.5
• 6 month cadence
• Roughly 2 months AFTER upstream
• Time to stabilize, certify, backport
• Initially 1 year lifecycle
• Will increase lifecycle over time based on
  upstream stability and customer requirements
• Hardware and application certifications from RHEL
  carry over to Red Hat Enterprise Linux OpenStack
  Platform
• Consistent ecosystem of partners

29
OpenStack Progression

• Latest OpenStack software, packaged in a
  managed open source community
• Facilitated by Red Hat
• Aimed at architects and developers who
  want to create, test, collaborate
• Freely available, not for sale
• Six-month release cadence mirroring community
• No certification, no support
• Installs on Red Hat and derivatives

• Open source, community-developed (upstream)
  software
• Founded by Rackspace Hosting and NASA
• Managed by the OpenStack Foundation
• Vibrant group of developers collaborating on open
  source cloud infrastructure
• Software distributed under the Apache 2.0 license
• No certifications, no support

• Enterprise-hardened OpenStack software
• Delivered with an enterprise life cycle
• Six-month release cadence offset from community
  releases to allow testing
• Aimed at long-term production deployments
• Certified hardware and software through the Red
  Hat OpenStack Cloud Infrastructure Partner
  Network
• Supported by Red Hat

30
TYPICAL DEPLOYMENT
31
VIRTUAL MACHINE TYPES
TRADITIONAL CLOUD MIXED
Big stateful VM Small stateless VMs Combination of Traditional and Cloud VMs to provide application. Database may be hosted on traditional workloads, web front-end and logic layers on cloud workloads.
1 Application ? 1 VM 1 Application ? Many VMs Combination of Traditional and Cloud VMs to provide application. Database may be hosted on traditional workloads, web front-end and logic layers on cloud workloads.
Lifecycle in years Lifecycle hours to months Combination of Traditional and Cloud VMs to provide application. Database may be hosted on traditional workloads, web front-end and logic layers on cloud workloads.
Scale up (VM gets bigger) Scale out (add VMs) Combination of Traditional and Cloud VMs to provide application. Database may be hosted on traditional workloads, web front-end and logic layers on cloud workloads.
Not designed to tolerate failure of VM, so you need features that keep VMs up If a VM dies, application kills it and creates a new one, app stays up Combination of Traditional and Cloud VMs to provide application. Database may be hosted on traditional workloads, web front-end and logic layers on cloud workloads.
Application SLA requires enterprise virtualization features (migration, HA, etc.) to keep applications available Application SLA requires adding/removing VM instances to application cloud to maintain application availability Combination of Traditional and Cloud VMs to provide application. Database may be hosted on traditional workloads, web front-end and logic layers on cloud workloads.
32
ANALOGY PETS vs FARM ANIMALS

• PETS
• TRADITIONAL WORKLOADS

• FARM ANIMALS
• CLOUD WORKLOADS

• Pets are given names like
• rover.internal.redhat.com
• They are unique, lovingly hand raised and cared
  for
• When they get ill you nurse them back to health

• Farm animals have tag numbers like
  piggie242.redhat.com
• They are almost identical to each other
• When they get ill you get another one

Credit Tim Bell _at_ CERN Labs, Bill Baker _at_
Microsoft, and others
33
OPENSTACK CORE PROJECTS

• OpenStack Identity (KEYSTONE)
• Identity Service
• Common authorization framework
• Manages users, tenants and roles
• Pluggable backends (SQL, PAM, LDAP, etc)

34
OpenStack Identity (Keystone)
keystone
Token
Services
Token
Identity
35
OpenStack Identity (Keystone) Scaling
Load Balancer
...
keystone
keystone
keystone
36
OPENSTACK CORE PROJECTS

• OpenStack Compute (NOVA)
• Core compute service comprised of
• Compute Nodes hypervisors that run virtual
  machines
• Supports multiple hypervisors KVM, Xen, LXC,
  Hyper-V and ESX
• Distributed controllers that handle scheduling,
  API calls, etc
• Native OpenStack API and Amazon EC2 compatible API

37
OpenStack Compute (Nova)
nova-api
AMQP
nova-scheduler
nova-conductor
nova-compute
LibvirtKVM
DB
38
OpenStack Compute (Nova) Scaling
Load Balancer
nova-api
nova-api
nova-api
AMQP
nova-scheduler
nova-scheduler
nova-scheduler
nova-conductor
nova-conductor
nova-conductor
nova-compute
nova-compute
nova-compute
LibvirtKVM
LibvirtKVM
LibvirtKVM
DB
39
OPENSTACK CORE PROJECTS

• OpenStack Image Service (GLANCE)
• Image service
• Stores and retrieves disk images (virtual machine
  templates)
• Supports Raw, QCOW, VMDK, VHD, ISO, OVF AMI/AKI
• Backend storage Filesystem, Swift, Amazon S3

40
OpenStack Image Service (Glance)
glance-api
glance-registry
ReST
DB
Image Storage
41
OPENSTACK CORE PROJECTS

• OpenStack Object Storage (SWIFT)
• Object Storage service
• Modeled after Amazon's S3 service
• Provides simple service for storing and
  retrieving arbitrary data
• Native API and S3 compatible API

42
OPENSTACK CORE PROJECTS

• OpenStack Networking (NEUTRON formerly QUANTUM)
• Network Service
• Provides framework for Software Defined Network
  (SDN)
• Plugin architecture
• Allows integration of hardware and software based
  network solutions

43
OPENSTACK CORE PROJECTS

• OpenStack Block Storage (CINDER)
• Block Storage (Volume) Service
• Provides block storage for virtual machines
  (persistent disks)
• Similar to Amazon EBS service
• Plugin architecture for vendor extensions
• eg. NetApp driver for Cinder

44
OPENSTACK CORE PROJECTS

• OpenStack Dashboard (HORIZON)
• Dashboard
• Provides simple self service UI for end-users
• Basic cloud administrator functions
• Define users, tenants and quotas
• No infrastructure management

45
CLOUDFORMS
46
CLOUDFORMS Cloud Operations Management
Complete Cloud Service Lifecycle

• Automated Provisioning
• Simple/Multi-Tier, Full Stack
• Self-Service, Service Catalog
• Delegated Operations
• Power Operations, Console
• Reconfiguration
• Intelligent Optimization
• CPU, Memory Storage
• Demand-Driven Scaling
• Horizontal Vertical
• Start/Stop or Provision/Destroy
• Scheduled Retirement
• Fully Automated
• Multi-Phase

Automated Provisioning
Delegated Operations
Scheduled Retirement
Demand- Driven Scaling
Intelligent Optimization
47
RED HAT CLOUD VISION Open hybrid clouds from ALL
Infrastructure
PORTABILITY
PaaS
Application
Applications

Operating System
Linux Windows
Operating System and Hardware
IaaS
Infrastructure
Virtual or Physical
SELF-SERVICE Consumption with Control
CLOUDFORMS
HYBRID CLOUD
PRIVATE CLOUD
PUBLIC CLOUD
VIRTUAL RESOURCES
PHYSICAL RESOURCES
PUBLIC RESOURCES
VMware vSphere
Red Hat RHEV
Amazon EC2
Microsoft System Center
Rackspace
Red Hat Enterprise Linux
Microsoft Windows
Red Hat OpenStack
Red font denotes a future enhancement
48
CLOUDFORMSCloud Management Platform Capabilities
Overview
49
CLOUDFORMS Built for Enterprise Scale Cloud
Operations Management
50
CLOUD MANAGEMENT Usage Scenarios
51
IT CLOUD MANAGEMENT Seamless Self-Service
CLOUDFORMS

• Role-based Delegation
• Self-Service Portals
• Service Catalogs
• Automated Provisioning
• Quotas Chargeback

52
IT CLOUD MANAGEMENT Single Pane of Glass
Operations
CLOUDFORMS

• Configuration Management
• Resource Management
• Capacity Utilization
• Dashboards, Timelines
• Change Drift Tracking

53
IT CLOUD MANAGEMENT Executive Management
CLOUDFORMS

• Financial Management
• Governance Compliance
• Forecasting Planning
• Health, Availability

54
IT CLOUD MANAGEMENT Integration
Enterprise Service Catalogs
Management Reporting
Event Consoles
CLOUDFORMS
CMDB
ITPA/RBA
55
CLOUDFORMS Cloud Management Platform Capabilities

• Directory Integration, Role-Based
• Classification-Driven Access Control
• Self-Service Admin Portals

Access Control
Automation
Integration

• Process
• Runbook
• Task
• Orchestration
• Workflows
• Approvals
• Policy Enforcement
• Provisioning
• Retirement
• Reclamation
• Classification
• Optimization
• Workload Management

• Service Catalogs
• Service Modeling Designer
• IaaS/PaaS Provisioning
• Lifecycle Management
• Financial Management

Service Management

• CMDB
• Service Catalog
• Incident
• Change
• Runbook
• Event Console
• SEIM
• Helpdesk
• Portals
• Web Services

• Monitoring Alerting
• Capacity Planning
• Self Learning Analytics
• Quota Enforcement
• Resource Pooling

Resource Management

• Automated Provisioning
• Dynamic Reconfiguration
• Capacity Planning

Infrastructure Management

• Federation
• Brokering
• Abstraction

Hybrid Cloud
56
CLOUDFORMSUnique Patent-Pending Technology
Built for Clouds
57
CLOUDFORMS User - Dashboard
58
CLOUDFORMS Executive - Chargeback
59
CLOUDFORMS Operations - Dashboard
60
CLOUDFORMS Operations - Monitoring
61
CLOUDFORMS Executive - Planning
62
Red Hat Cloud Infrastructure (RHCI)

• RHCI meets the needs of our customers at
  each step to the cloud. It is a single
  subscription offering consisting of three
  products

• Red Hat Enterprise Virtualization (RHEV),
  datacenter virtualization solution for
  traditional Linux and Windows scale up workloads
  virtualization consolidation.
• Red Hat Enterprise Linux OpenStack Platform
  (RHEL-OSP), a massively scalable-out IaaS build
  from an optimized pairing of Red Hat's OpenStack
  and Red Hat Enterprise Linux.
• Red Hat CloudForms, allows customers to deploy,
  monitor, and manage cloud services across RHEV,
  VMware vSphere, RHEL-OSP, and an increasing
  number of public cloud providers (including AWS)

63
MANAGE TRADITIONAL WORKLOADS

• SCENARIO
• Traditional applications currently on bare metal
  or virtualization
• Need enterprise virtualization features for
  application availability
• Want additional private cloud functionality
  self-service, charge-back, governance, compliance
• Planning to use OpenStack in future

• SOLUTION
• DEPLOYMENT

64
MANAGE TRADITIONAL WORKLOADS ON MIXED
INFRASTRUCTURE

• SCENARIO
• Investment in VMware vSphere
• Want to extend virtualization footprint at lower
  cost
• Want additional private cloud functionality
  without locking in to a single-vendor stack
• Planning to use OpenStack in future

• SOLUTION

• DEPLOYMENT

65
DEPLOY MIXED-MODEL APPLICATIONS

• SCENARIO
• Traditional application provides core service
  (DB, transaction processing) for application
• Cloud-enabled application provides load balancing
  web front end

• SOLUTION

• DEPLOYMENT

66
RED HAT OPENSTACK 2013
67
THANK YOU