Upload
others
View
5
Download
0
Embed Size (px)
Citation preview
CONSIDERATIONS FOR YOUR NEXT CLOUD PROJECT – CLOUDFORMS & OPENSTACK DO’S AND DON’TS
FREDERIK BIJLSMA
Cloud Business Unit Manager, EMEA6th December 2013
VIRTUALIZATION TO CLOUD CONTINUUM
ServerVirtualization
DistributedVirtualization
PrivateCloud
HybridCloud
VisibilityControl
OptimizationAutomation
AgilitySelf-Service
FederationBrokering
Consolidation Reduce Capital
Expense
Flexibility & Speed Reduce Operational Expense
Automation Less Downtime
Self-Serve Agility Standardization IT as a Business Usage Metering
Reduce Costs for Peak Loads Flexibility for Peak Loads
Portability of All Loads
Drivers
RECAP -WHY VIRTUALIZE THE SERVER?
DECREASE:
Server sprawl
Space and power
Management inefficiencies
Downtime
Maintenance and support
Hardware lock-in
INCREASE:
Service levels
Hardware abstraction
Agility and flexibility
Server utilization
Business continuity Staff productivity
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, managed via a web GUI
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)
Red Hat & OpenStackRED HAT & OPENSTACK
WHY RED HAT OPENSTACK?
• Red Hat brings what OpenStack really needs...
• Supportability
• Stability & Code Maturity
• Certified Ecosystem
• Lifecycle
• Support for the entire stack from one vendor• OpenStack Components• Stable, mature and trusted Linux Operating System• Secure, high performance virtualisation• Storage• Software Defined Networking
HAVANA RELEASE OCTOBER 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
RED HAT DEVELOPMENT POWERHOUSE
Source:Bitergia OpenStack Havana Analysis, October 17, 2013blog.bitergia.com/2013/10/17/the-openstack-havana-release
Corporate contributions to OpenStack
OPENSTACK HAVANA RELEASE
NUMBER OF COMMITSRED HAT
COMPANY / ORGANIZATION *
* Includes only the top 35.
(04 APR to 16 OCT 2013)
SERVICE MODELS / WORKLOADS
• TRADITIONAL WORKLOADS Stateful VMs, application defined in VM
Big VMs: vCPU, vRAM, local storage inside VM
Application SLA = SLA of VM
SLA requires enterprise virtualization features to keep VMs highly available
Lifecycle measured in years
VMs scale up: add vCPU, vRAM, etc.
Applications not designed to tolerate failure of VMs
CLOUD WORKLOADS
Stateless VMs, application distributed
Small VMs: vCPU, vRAM, storage separate
Application SLA not dependent on any one VM
SLA requires ability to create and destroy VMs where needed
Life cycle measured in hours to months
Applications scale out: add more VMs
Applications designed to tolerate failure of VMs
• PETS FARM ANIMALS
Credit : Tim Bell @ Cern Labs
Pets are given names likepussinboots.cern.ch
They are unique, lovingly hand-raised, and cared for
When they get ill, you nurse them back to health
Farm animals are given numbers like vm0042.cern.ch
They are almost identical to other farm animals
When they get ill, you get another one
SERVICE MODELS / WORKLOADS
TRADITIONAL VS CLOUD ENABLED WORKLOADS
Traditional apps can take years to write, live for decades, are monolithic, need to be protected against failure at all costs
− Failover and clustering designed for this purpose– failure of these apps could lead to business disaster
Newer cloud-enabled workloads are different− Disposable, stateless, modular− Can adapt quickly to changes in external environment− Examples: home grown customer facing apps, Netflix, Hulu,
and many popular web-based games
Organizations increasingly need to accommodate these two fundamentally different types of workloads
OPENSTACK & CLOUDFORMS DO´S AND DONT´S Classify IT Landscape
Workloads (Application Ready for OpenStack?) Data Security Tiers SLAs …
Greenfield or Brownfield installation? “Manager of Managers” might be required “Understand” your Brownfield in Real Time
Compare Software Support Models Look for experienced Partners in Implementation
CLOUDFORMS - CLOUD OPERATIONS MANAGEMENT
• Delivers an Open Cloud Management Platform that Supports Heterogeneous Private, Public and Hybrid Clouds
• Enables Evolution from Proprietary Infrastructures to Open, Hybrid Clouds
• Enables IT to Deliver IAAS and Broker Cloud Services, Optimize Resources and Reduce Costs
• Manages Service Deployment across Hybrid Clouds Using Policies, SLAs and Cost
• Provides Rich Integration into Existing Enterprise Management Systems and Processes
• Eliminates Proprietary Cloud Management Tool Vendor Lock-In
CLOUDFORMS CAPABALITIES
OPENSTACK ADMINISTRATION TRAINING
UPCOMING TRAINING FOR CLOUDFORMS
Coming soon: Red Hat CloudForms Hybrid Cloud Management
Note: This course will be launched early 2014. Course is based on CloudForms 3.0 and will be offered in a virtual training environment.
RECAP: DOS AND DONTS
Classify IT Landscape Workloads (Application Ready for OpenStack?) Data Security Tiers SLAs …
Greenfield or Brownfield installation? “Manager of Managers” might be required “Understand” your Brownfield in Real Time
Compare Software Support Models Look for experienced Partners in Implementation