Fuzzball Documentation
Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Toggle Dark/Light/Auto mode Back to homepage

Storage Provisioners

Fuzzball V4 uses storage provisioners to manage how volumes are created, accessed, and stored on your cluster. A provisioner is a single entity that combines a storage driver configuration with access policies and optional annotations — replacing the separate storage driver and storage class entities from V3.

V4 storage model:

        ┌──────────────────────┐
        │  StorageProvisioner  │
        │  · driver config     │
        │  · access policies   │
        │  · annotations       │
        └──────────┬───────────┘
                   │
      ┌────────────┼────────────┐
      │            │            │
      ▼            ▼            ▼
┌──────────┐ ┌──────────┐ ┌──────────┐
│ volume-1 │ │ volume-2 │ │ volume-3 │
└──────────┘ └──────────┘ └──────────┘

Each provisioner embeds one of Fuzzball’s built-in storage drivers:

Driver TypeUse CaseBackend
NFSOn-prem multi-node clustersNFS server export
HostpathSingle-node or clustered filesystems (Lustre, GPFS)Local filesystem path
EFSAWS cloud deploymentsAWS EFS access points
FilestoreGCP cloud deploymentsGCP Filestore share
Azure FilesAzure cloud deploymentsAzure Files NFS share
OCI FSSOCI cloud deploymentsOCI File Storage system
OCI Managed LustreOCI HPC and AI deploymentsOCI Managed Lustre file system
Fuzzball V4 does not require installing external container-based drivers. All supported storage drivers are built into the Fuzzball platform.

Provisioners are managed at the organization level by organization owners. Group members can create and access volumes based on the provisioner’s access policies.

In this section

If you are upgrading from Fuzzball V3, your existing storage classes are automatically migrated to provisioners during the upgrade. See the V3 to V4 Storage Migration Guide for details on post-upgrade steps.