Improving Storage Support in Apache Mesos using CSI
summary
Mesos adds a pluggable storage layer so CSI plugins talk to Mesos as resource provider instances, letting Mesos discover capacity, provision and publish volumes via controller and node gRPC services. REX-Ray already ships a CSI implementation (v0.10 released Sept 12) and supports many clouds; Mesos targets local RP in the next release (~2 months) and external/global RP afterward (4–5 months), enabling dynamic provisioning, quota-aware disk resources and looser coupling to vendor APIs.
AI-written summary · about
chapters (22)
- 0:00Introduction
- 8:06Goals of CSI
- 9:18Control Plane Interface
- 12:35Lifecycle Operations
- 13:28Identity Service
- 14:10Controller Service
- 15:55Node Service
- 17:01Resource Provider
- 18:57Storage Resource Provider
- 20:26Integration Architecture
- 22:48Roadmap
- 23:47XRay Overview
- 24:28XRay History
- 26:15XRay Plan
- 26:44Storage Plugins
- 29:31Vendor perspective
- 30:53Whos involved
- 31:36Whats not in CSI
- 32:28Getting involved
- 35:06Questions
- 36:32Architecture Slides
- 42:36Domain
related talks
39mContainer Storage Interface: Present and Future
47mHow Container Schedulers and Software-based Storage will Change the Cloud
27mCeph-CSI: The Engine Behind Persistent Storage in Kubernetes
25mYour ReadWriteMany (RWX) Storage in k8s with Manila CSI
40mCeph CSI Driver: Bridging Containers and Ceph
48mCSI in Kubernetes
25mConnecting ecosystems: How Cinder CSI, Ember CSI & Manila CSI leverage OpenStack bits in Kubernetes
59mBuilding Distributed Systems with Apache Mesos