File Systems as a Service
summary
SAP implements a managed volume service for Cloud Foundry that provisions an NFS share per service instance, mounts it into Diego cells via the Docker volume plugin API, and enforces per-share quotas by creating a UID-mapped user and using fuse NFS UID mapping. The broker is a Go-based custom broker that returns a volume_mount JSON with driver and source, while a slightly modified upstream NFSv3 driver performs mounts and a broker callback validates requests. The service works in production but requires high availability to avoid blocking app starts.
AI-written summary · about
chapters (4)
- 0:00Introduction and motivation
- 13:19Volume service architecture
- 20:28Implementation details and broker setup
- 32:46Lessons learned and Q&A
related talks
35mNFS and Shared Filesystems as a Service
19mPersistence Arrives on Diego
30mA Guided Tour From Code Base to Platform - Aaron Spiegel, Paul C. Warren, Maggie Ambrose
31mHitchhiker’s Guide to the Enterprise-Grade Platform
24mDualing Platforms: Building Services for Cloud Foundry and Kubernetes Using the Open Service Broker
30mOn-Demand Data Services with Cloud Foundry - Maria Ntalla & Simon Jones, Pivotal
22mMulti-Purpose Cloud Filesystem
36mMulti-Cloud with Cloud Foundry: Making It Real - Dmitry Bakaleinik, SAP & Sean McKenna, Microsoft
