openstack cinder, implementation today and new trends for tomorrow
TRANSCRIPT
![Page 1: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/1.jpg)
OpenStack Block Storage Cinder – Implementations for Today and Trends for Tomorrow
Ed Balduf, Cloud Solutions Architect - OpenStack, [email protected] @madskier5
![Page 2: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/2.jpg)
● Ephemeral ● Non-Persistent ● Life Cycle coincides with an Instance ● Usually local FS/QCOW file
● Object
● Manages data as.. well, an Object ● Think photos, mp4’s etc ● Typically “cheap and deep” ● Commonly SWIFT
● Shared FS
● We all know and love NFS ● My be managed by Manila
● Glance???
OpenStack = Many Storage Pieces
● Block
● Foundation for the other types
● Think raw disk
● Typically higher performance
● Cinder
![Page 3: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/3.jpg)
Let’s talk Cinder!
![Page 4: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/4.jpg)
Cinder Mission Statement
To implement services and libraries to provide on demand, self-service access to Block Storage resources. Provide Software Defined Block Storage via abstraction and automation on top of various traditional backend block storage devices.
To put it another way... Virtualize various Block Storage devices and abstract them in to an
easy self serve offering to allow end users to allocated and deploy storage resources on their own quickly and efficiently.
![Page 5: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/5.jpg)
How it works ● Plugin architecture, use your own vendors backend(s) or use the default
● Backend devices invisible to end-user ● Consistent API regardless of backend ● Filter Scheduler let’s you get get fancy ● expose differentiating features via custom
volume-types and extra-specs
![Page 6: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/6.jpg)
![Page 7: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/7.jpg)
![Page 8: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/8.jpg)
Storage Services ● Extend Volume ● Snapshot/Clone ● Change Volume type ● Backup/Restore ● Create Image/upload Image ● Manage/Unmanage ● Migrate ● Replication? ● Consistency Groups?
![Page 9: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/9.jpg)
Reference Implementation Included ● Includes code to provide a base implementation using LVM ● Just add disks ● Great for POC and getting started ● Sometimes good enough ● Might be lacking for your performance, H/A and Scaling needs (it all depends) ● Can Scale by adding Nodes ● Cinder-Volume Node utilizes it’s local disks (allocate by creating an LVM VG) ● Cinder Volumes are LVM Logical Volumes, with an iSCSI target created for each
➔ Typical max size recommendations per VG/Cinder-Volume backend ~ 5 TB ➔ No Redundancy (yet)
![Page 10: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/10.jpg)
Look at a deployment
![Page 11: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/11.jpg)
Sometimes LVM Isn’t Enough
• CloudByte • Coraid • Datera • Dell (Eql + Stor Cntr) • EMC (VMAX, VNX, XtremeIO) • Fujitsu Eternus • GlusterFS • Hitachi (HUS, HUS-VM, VSP, HNAS) • HP (3PAR, LeftHand, MSA) • Huawei T (v1, v2, v3) • IBM (DS8K, GPFS, StoreWize, NAS, XIV)
• LVM (reference) • NTAP (FAS, E-series) • Nexenta • NFS (reference) * • Nimble Storage • Pure Storage • Quobyte • RBD (Ceph) • Scality • SMB • StorPool
• SolidFire • Symantec • Tintri • Violin Memory • Vmware • Windows Srv 2012 * • X-IO Tech • Zandara • Solaris (ZFS) * • ProphetStor
* Partial
Plugin Architecture gives you choices (maybe too many) and you can mix them together:
![Page 12: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/12.jpg)
Only Slightly Different
![Page 13: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/13.jpg)
cinder.conf file entries #Append to /etc/cinder.conf enabled_backends=lvm,solidfire default_volume_type=SolidFire [lvm] volume_group=cinder_volumes volume_driver=cinder.volume.drivers.lvm.LVMISCSIDriver volume_backend_name=LVM_iSCSI [solidfire] volume_driver=cinder.volume.drivers.solidfire.SolidFire san_ip=192.168.138.180 san_login=admin san_password=solidfire volume_backend_name=SolidFire
![Page 14: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/14.jpg)
A Deeper Look
![Page 15: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/15.jpg)
Creating types and extra-specs (GUI)
![Page 16: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/16.jpg)
End users perspective (GUI)
![Page 17: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/17.jpg)
Web UI’s are neat, but automation rules! ebalduf@bdr76 ~ $ cinder create -‐-‐volume-‐type SF-‐Silver –-‐display-‐name MyVolume 100 or in code:
>>> from cinderclient.v2 import client >>> cc = client.Client(USER, PASS, TENANT, AUTH_URL, service_type="volume") >>> cc.volumes.create(100, volume_type=f76f2fbf-‐f5cf-‐474f-‐9863-‐31f170a29b74) [...]
![Page 18: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/18.jpg)
Or Heat Templates! resources: server: type: OS::Nova::Server properties: name: { get_param: "OS::stack_name" } … storage_volume: type: OS::Cinder::Volume properties: name: { get_param: "OS::stack_name" } size: { get_param: vol_size } volume_type: { get_param: vol_type } volume_attachment: type: OS::Cinder::VolumeAttachment properties: volume_id: { get_resource: storage_volume } instance_uuid: { get_resource: server }
![Page 19: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/19.jpg)
Where is Cinder headed next?
![Page 20: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/20.jpg)
Pets <- Cattle(Cinder) -> 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
![Page 21: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/21.jpg)
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?
![Page 22: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/22.jpg)
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
![Page 23: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/23.jpg)
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.
![Page 24: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/24.jpg)
“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.”
![Page 25: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/25.jpg)
Making choices can be the HARDEST part!
● Each has their own merits ● Some excel at specific use cases
● Maybe you already own the gear ● TCO, TCO, TCO
Ask yourself: ➔ Does it scale?
➔ Is the architecture a good fit? ➔ Is it tested, will it really work in OpenStack?
➔ Support?
➔ What about performance and noisy neighbors? ➔ Third party CI testing?
➔ Active in the OpenStack Community? ➔ DIY, Services, both/neither
(SolidFire AI, Fuel, JuJu, Nebula….)
![Page 26: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/26.jpg)
Cinder – Liberty ● Brick (Multi-attach, HA-connections) ● Volume Migration: Support Ceph ● Replication ● Universal Image caching ● Import/export snapshots ● Force delete backups ● Volume Metadata enhancements ● Nested Quotas ● Guru reports, better accounting for operators ● RemoteFS: (NFS, Gluster) Snapshots, Clones, and assisted Snapshots ● Support iSCSI HW offload ● DB: Archive, DB2
![Page 27: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/27.jpg)
The All-Flash Array for the Next Generation Data Center
A few words from our sponsor...
![Page 28: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/28.jpg)
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
Scale-Out Infrastructure
Agility
Guaranteed Quality of Service
Complete System
Automation
In-Line Data Reduction
Self Healing High Availability
![Page 29: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/29.jpg)
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 • 8th Generation of Software
Innovative
Sales, Marketing, and Support : • Over 400 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
#1 ALL-FLASH ARRAY CC 2015
![Page 30: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/30.jpg)
Related Resources
● OpenStack Solution Page ● OpenStack Solution Brief ● SolidFire/Cinder Reference Architecture ● OpenStack Configuration Guide ● SolidFire/Rackspace Private Cloud
Implementation Guide ● Video: Configuring OpenStack Block Storage w/
SolidFire
● Blogs ● OpenStack Summit Recap: Mindshare
Achieved, Market Share Must Follow ● Separating from the Pack ● Why OpenStack Matters
![Page 31: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/31.jpg)
How to get involved?
● It’s Easy, Start Here ● https://wiki.openstack.org/wiki/
How_To_Contribute
● Any questions? ● Technical
● Partnership ● [email protected]
● Sales ● [email protected]
![Page 32: OpenStack Cinder, Implementation Today and New Trends for Tomorrow](https://reader031.vdocuments.net/reader031/viewer/2022021500/58e929471a28ab15428b56d5/html5/thumbnails/32.jpg)
1620 Pearl Street, Boulder, Colorado 80302 Phone: 720.523.3278 Email: [email protected] www.solidfire.com