OpenStack has been making tremendous progress, with production deployments proliferating globally. But is OpenStack hardened and ready for the Enterprise? Is it mature enough to run production and mission critical workloads? Does it adequately address security and compliance requirements? We believe that the
answer is a resounding “yes”.
This session will deliver the insights you need to fully embrace OpenStack by addressing:
Common Pitfalls - common reasons why OpenStack deployments typically fail in enterprise environmentsInterop_Las_Vegas
Economics - total cost of ownership of a typical OpenStack footprint within the enterprise, and highlight the areas where benefits are primarily achieved
Ecosystem - the importance of the OpenStack ecosystem, and why this helps the enterprise in the short and long-term
Private, Public or Hybrid - where to deploy one of the models, and explain why OpenStack is the right choice for all of them
Real world enterprise case studies - successful deployment models
OpenStack in the Enterprise - Interop Las Vegas 2014
1. Making the case for OpenStack
in the Enterprise
Francesco Paola, CEO, Solinea
Seth Fox, VP Operations, Solinea
2. Cloud is the only domain we focus on, with vertical industry
and horizontal solutions specialization
Purpose-built
for cloud
Track record of success architecting, building and operating
production clouds – private and public – world-wide
Proven Delivery
Success
We understand cloud adoption challenges of global
companies
Enterprise IT
Experience
Integrated capabilities lifecycle: cloud strategy, architecture,
implementation and adoption services
Unique
Approach
!
!
Who we are
Accelerating Open Infrastructure Adoption
Built the first OpenStack production clouds and
contributors to the platform since its inception
OpenStack™
Experience
3. ● Cloud Orchestration Framework
○ Compute (Nova)
○ Object Storage (Swift)
○ Identity Services (Keystone)
○ Dashboard (Horizon)
○ Networking (Neutron)
○ Telemetry (Ceilometer)
○ More every day
● Collection of tools that have been around the Enterprise
○ Linux, KVM, Python, LDAP, L3 Routing, etc.
● Icehouse is the ninth release since its inception
● Foundation Managed
OpenStack – we’re all familiar with it…
4. Survey Profile
● 822 Responses
● 387 Deployments
● 539 Companies
Industries Included
● Information Technology
● Academic / Research
● Telecommunications
● Film / Media
● Government / Defense
● Manufacturing
● Industrial
● Retail
● Healthcare
● Financial Services
Who uses OpenStack?
Source: November 2013 OpenStack User Survey
6. 1. Agility – ability to innovate and compete
2. Openness – open platform with an
expanding ecosystem
3. Cost – lowers the LONG-TERM total cost of
ownership (TCO)
4. Operational Efficiency – OK, once you
get there, but this takes time…
Why are Enterprises adopting OpenStack?
What we see and hear…
7. Is OpenStack Ready?
• In Use Today
– Large Scale Enterprises – Top 10 Auto Manufacturer
– Financial Services - PayPal
– Telecommunications - Comcast, AT&T, Verizon
– SaaS - Concur, HubSpot
– Web 2.0 - eBay
– Film / Media - Digital Film Tree, Shutterstock
– Government - NSA
– Ecosystem in full swing
8. Supported
Distributions
Platform as a Service
integrations
Subscription
Models Management Tools
Training Range of Storage
Options
Virtual Desktop
Solutions Consulting Services
Vendor support for fully integrated
solutions
Ecosystem
Photo Credit: www.rling.com
9. A platform to support a wide range of tools and applications from
multiple business units
Open
Innovation
Data Analysis
Shared Data
Service
Development
Cost
Real-time
Build a data analytics capability to gain insights and competitive
advantages
Enable Data as a Service across the organization
Deploy new services quickly to respond to market demands
Enable response to quality issues and customers in real-time
Enable a cost effective infrastructure and software solutions
DescriptionRequirement
Case Study – Building the Car Cloud
10. § Pilot: 1 Rack
§ Deploy Big Data Platform and Analytics Use Cases
§ Build out the Production Cloud
ObjectivesPhase
§ Perform expansion of production Car Cloud
§ Initiate deployment of In-Car Services
§ Expand Production Car Cloud geographically
§ Internal functions deployment
Phase 1
§ Production Infra.
§ Big Data Analytics
Phase 2
§ Big Data Analytics
§ In-car Services
Phase 3
§ In-car Services
§ Global footprint
§ Half-rack deployment of OpenStack to run test use cases
§ Compare against a “Legacy Appliance” to justify investment
Proof of Concept
§ Big Data Analytics
§ In-car Services
Implementation Roadmap
11. PoC: half-rack with OpenStack
OpenStack
Components
• Nova
• Swift
• Glance
• Cinder
• Keystone
• Horizon
• Heat
• HA/Proxy
Use Cases
• Big Data
• Map App on
Swift
• Map Updates
• Auto Scaling
• Operator
Functions
Notes: RHOS, Apache Hadoop, KVM (CentOS), Quanta
12. PoC Comparison vs. Legacy Appliance
PoC
• Cost: $125K + Services
• Timeframe: 3 weeks
• Performance: 40 minutes
Legacy Appliance
• Cost: $1.2MM
• Timeframe: 2 weeks
• Performance: Did not
compute
Use Case Tested for Comparative Purposes:
• A predefined and parsed data TMU data set is preloaded on
Hadoop
• Map/Reduce transforms the data to a number of key and value
pairs
• The Map/Reduce job is submitted
• Job is monitored for completion
13. Key Success Factors
DescriptionSuccess Factor
ü Stand behind the cloud plan, revise it
quarterly, stay committed to the journey
Maintain Executive Sponsorship
ü Transition from a project/product approach to
a services and solutions offerings
Position for Services
ü Standardize solutions to enable repeatability,
minimizing customization
Standardize processes and
offerings
ü Review internal policies and procedures to
establish a Hybrid cloud strategy
Prepare for Hybrid (Public)
Cloud
ü Ensure BU’s, including IT & Operations, are
aligned on the Cloud objectives
Ensure cross-BU consensus
ü Invest in building the necessary governance
and cloud internal skills
Invest in the Cloud Competency
Group
14. § Isolate, then extend to the broader organizationIncubate
§ Independent of the legacy IT organization
§ Build COEs e.g. infrastructure, platform, data, devops etc
Create
Competency
Centers
§ Create a separate culture that is not tied to legacy IT – if possible
§ Treat the business as a client
Focus on the
Culture
§ Move to agile, but recognize that agile is a mindset, not a solution
§ Enable “fast fail cycles” and experimentation to drive innovation
Align to Business
Agility
§ Adapt Governance model to speed of change; strive for automation
Transform
Governance
Make OpenStack Work!
It’s not the technology… it’s everything else!