OpenStack Silicon Valley - Enterprise Storage Trends Driving OpenStack Features
Transcript of OpenStack Silicon Valley - Enterprise Storage Trends Driving OpenStack Features
Enterprise Storage Trends Driving OpenStack Features Ed Balduf Cloud Solutions Architect SolidFire Inc. [email protected] @madskier5
Pets, Cattle and Chickens? § Traditional (Enterprise) infrastructure is individualized. § Cloud native applications are transitory and disposable. § Containers are more efficient, more numerous and more transitory than VMs.
§ Uptime responsibility shift § Enterprise (traditional) -> Infrastructure § Cloud and Containers -> Applications and DevOps
Enterprise Apps and IT orgs on cloud
Apps § Monolithic § Stateful § Shared Storage § Connected (LDAP, Org DB) § Long startup times § Multi-volume § Active-passive
IT Organizations § Business Driven § Politically driven § Cost burden (single) § Overworked § Hierarchical/divided § Legacy burden § Prized, expensive apps § Packaged software
How do you manage it all on a modern cloud?
Protecting Legacy Apps in the Cloud
§ Live Migration § Available in OpenStack today on both shared storage and block storage. § Some drivers are broke.
§ Replication § V1 in Kilo, V2 in work for Liberty.
§ Fibre Channel § Available in OpenStack today. 24 drivers of 37 block drivers as of 8/19
§ HA connections and Multi-Attach § HA: in process, maybe for Liberty. § Multi-attach: Cinder -> Liberty, Nova -> Mitaka (maybe)
§ Consistency Groups § In Juno. Only 6 drivers as of Kilo
§ Backup
Managing Enterprise in an Enterprise Cloud
§ Lack of Chargeback/lookback § Lack of Chargeback is holding the enterprise back. § No enforcement of what anyone uses.
§ QoS Quotas and/or Hierarchical quotas § How to do you Quota a Group or subgroup? § How do you extend quota s to QoS?
§ Custom catalogs § Private Volume Types are available in Kilo.
Higher Level cloud services § Horizon § Heat § Trove § Containers
§ OpenStack is probably the place to manage volumes for containers. § Whatever the host has, can be passed to the container § Volume services today.
§ Kubernetes – has it’s own volume service § Flocker is emerging as an option for HA. § Docker enhancements proposed
“No matter how much we try to change the expectation of users to align with ‘cloud,’ they still complain when I reboot things. So I gotta have live migration.”
Summary
§ Reluctance or inability to embrace cloud software architectures is driving change § Organizational structures are challenging
§ Lack of chargeback/lookback
§ OpenStack is changing to meet the demands § Much of what is needed is there already § Mitaka will see much of the remainder § ‘N’ will hopefully have the remainder
§ Containers do not have special interaction with storage. § Other mechanisms will have to manage storage for containers(OpenStack).
High performance storage systems designed for large scale infrastructure
Industry Leading Quality of Service (QoS)
Scale-Out Architecture • 4 – 100 nodes • 35TB – 3.4PB Usable Capacity • 200k – 7.5M Controllable IOPS
Simple all inclusive pricing model Direct Tier 3 Support
for every customer
Industry-standard hardware • 10 GigE iSCSI, 16/8 Gb FC
Powering the World’s Most Demanding Data Centers
The Most Complete AFA Feature Set • Scale-out Architecture • Self Healing High Availability • Guaranteed QoS • Complete System Automation • In-line Data Reduction
• 3rd Generation of Hardware • 7th Generation of Software
Innovative
Sales, Marketing, and Support : • Over 320 Employees • HQ: Boulder, Colorado • North America • EMEA • APJ
Global
Enabling Customer Success • Founded 2010 • Funding $150M, Series D • GA Product since Nov 2012 • Over 2500 nodes shipped • More than 45PB under mgt • Fueling over 58,000 business
Proven
#1 ALL-FLASH ARRAY CC 2014
Updated 1/30/15