OpenSDS: Storage Challenges in a Cloud Native Era
summary
OpenSDS presents a policy-driven control plane that federates multi-vendor storage into a single catalog of storage profiles and virtual pools, selecting physical pools for placement and provisioning at runtime. It exposes a common API with connectors for CSI and Cinder/Manila, targets block now (file next, object later), runs clustered with Zookeeper/etcd for metadata, and already has early demos and a back-end implementation underway to automate lifecycle, placement and cross-vendor orchestration.
AI-written summary · about
chapters (15)
- 0:00Intro
- 1:26State of Storage Management - Fragmented
- 3:57Storage Pains
- 10:03Mission and Goals
- 12:56Key Value Propositions - For Developers
- 13:55Key Value Propositions - For Vendors
- 18:19Controller Project - The Universal Storage Controller
- 19:44Plug-ins Project - Compute Framework Plugins
- 20:45Design Goals
- 23:33Design Requirements
- 25:06Advance Storage Controls
- 26:26Concept
- 30:00Storage Profile and Request
- 30:19OpenSDS Architecture Blocks
- 31:07OpenSDS for Cloud Native
related talks
35mOpenSDS: The Autonomous Data Platform for Cloud Native
17mKeynote: OpenSDS – An Industry-Wide Collaboration for SDS Management
38mCloud Native Storage - a View of the Landscape, Projects...
25mKeep calm and store your data in OCS
14mMany Apps. Many Locations. One Storage Solution.
38mStorage WG Deep Dive
17mOpenStack Block Storage differs from traditional block storage
49mOperational Concerns for Openstack Manila
