NFS and Shared Filesystems as a Service
summary
Cloud Foundry adds a Volume Services API that lets apps bind NFS and other filesystems via standard service brokers and volume drivers deployed on Diego cells using garden bind mounts. Implementations include a local driver that symlinks directories (single‑cell only), an asynchronous broker for Amazon EFS on AWS, and an EMC Rex Ray driver that can provision Isilon volumes. Broker responses store mount payloads in the Cloud Controller and drivers perform the actual mounts. Current gaps include BOSH deployment friction and weak binding validation and logging.
AI-written summary · about
chapters (14)
- 0:00Introduction to NFS services
- 1:27Why volume services matter
- 5:04Architecture overview
- 9:04Using volume services in apps
- 11:32Local driver and broker
- 14:28SEFS implementation
- 15:52Amazon EFS driver
- 19:23EMC RexRay driver
- 23:00Building custom solutions
- 27:18Future of volume mounts
- 31:14Validation and error logging
- 33:01Planned deployments
- 34:05Standardization efforts
- 34:48Resources and Q&A
related talks
36mFile Systems as a Service
44mWhat's New in Cloud Foundry Volume Services
19mPersistence Arrives on Diego
30mA Guided Tour From Code Base to Platform - Aaron Spiegel, Paul C. Warren, Maggie Ambrose
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
09mShared cloud file storage, uses cases, and the latest Amazon EFS innovations
30mHow to Facilitate the Cloud Foundry Adoption with Object Storage - Denis Jannot, Dell EMC