Skip to content

Creating Storage Volumes

Volumes (also known as Persistent Volume Claims, or PVCs) allow user workloads such as Jupyter Notebooks or VS Code instances to retain data across restarts. As an administrator, you can create and manage these volumes for users, or monitor and adjust existing volumes when necessary. This section describes how to create a new storage volume in the MemVerge AI platform.

  1. Navigate to the Storage page

    • In the left navigation bar, select Storage.
    • The Volumes tab displays a table of existing volumes, if any.

    Storage Volume Dashboard

  2. Click “+ New Volume”

    • In the upper-right corner of the Volumes dashboard, select + New Volume.
    • A New Volume dialog window will appear.

    Create a new Storage Volume

  3. Specify Volume Details

    • Name: Provide a unique identifier for the volume (e.g., jupyter-workspace or vs-code-pvc).
    • Project: Select the Project that owns or uses this volume. This determines which workloads can attach to it.
    • Storage Class: Choose an appropriate Storage Class. Examples might include nfs-client for NFS-based storage or any other preconfigured class.
    • Request Storage: Enter the size of the volume in GiB (e.g., 10 GiB). This is how much storage you request from the underlying storage provider.
    • Access Mode:
      • ReadWriteOnce (RWO): The volume can be mounted as read-write by a single node.
      • ReadWriteMany (RWX): The volume can be mounted as read-write by many nodes simultaneously (if supported by the chosen Storage Class).
      • ReadOnlyMany (ROX): The volume can be mounted as read-only by multiple nodes.
      • ReadOncePod (ROP): This access mode restricts a volume to be mounted as read/write by only a single pod for the duration of that pod’s lifetime. While different pods may still use the volume in sequence, only one pod at a time can have read/write access.

  4. Click “Create”

    • Once all fields are filled out, click Create.
    • The platform will generate a persistent volume claim (PVC) and provision the underlying storage.

  5. Verify Volume Creation

    • Return to the Volumes dashboard.
    • The newly created volume appears in the list with its Status (e.g., “Bound”), Request Storage, Capacity, and Access Modes.

Best Practices and Considerations

  1. Matching Workload Requirements

    • Choose an appropriate Storage Class and Access Mode based on your workloads. For instance, notebooks often require ReadWriteOnce, while shared data might need ReadWriteMany.

  2. Resource Constraints

    • Be mindful of the total available storage in your cluster. Requesting more storage than is physically available may lead to provisioning failures.

  3. Monitoring and Updates

    • Keep an eye on usage trends. If a workload outgrows the current volume capacity, you might need to resize or recreate the volume with more space (depending on the underlying storage provider).

  4. User Access

    • If end-users need to create or delete their own volumes, ensure they have the necessary permissions at the Project level.