Skip to content

Storage Volumes

In this quick start exercise, you will create, modify, and delete storage volumes (Persistent Volume Claims) in the MemVerge AI platform. Volumes are essential for persisting data generated by user Workspaces (e.g., Jupyter Notebook or VS Code) across restarts or cluster changes.

1. Create a Volume

  1. Open the Volumes Dashboard
  2. From the left-hand navigation, select Storage, then Volumes.

  3. Click + New Volume in the upper-right corner.

  4. Define Volume Properties

  5. Name: Provide a recognizable name for the volume (e.g., data-science-vol).
  6. Project: Choose which project will own the volume.
  7. Storage Class: Select a storage class suited to your needs (e.g., nfs-client, block-storage).
  8. Size: Specify the requested capacity (GiB).

  9. Access Mode: Pick ReadWriteOnce, ReadWriteMany, ReadOncePod, or the best option for your workload.

  10. Create

  11. Confirm your entries, then click Create.
  12. The volume will appear in the Volumes table with a status of Bound once successfully provisioned.

2. Modify a Volume

  1. Locate the Volume

  2. In the Volumes dashboard, find the volume you want to change.

  3. Edit Volume

  4. Click the Edit (pencil) icon under Actions.

  5. Update the Name, Project, or Requested Storage (resizing depends on the underlying storage provider’s capabilities).

  6. Confirm Changes

  7. Click Update to apply your modifications.
  8. Return to the Volumes dashboard to ensure the new settings are reflected.

3. Delete a Volume

  1. Stop and Delete Associated Workspaces

  2. Important: If a volume is attached to a Workspace, you should stop and remove that Workspace first. Deleting a volume that’s still in use can cause data corruption or application errors.

  3. Remove the Volume

  4. From the Volumes dashboard, locate the volume in the list.
  5. Click the X or Delete icon under Actions.

  6. Confirm in the pop-up dialog to permanently remove the volume.

  7. Verify Removal

  8. The volume will disappear from the table once deletion is complete.
  9. Check that no active Workspaces are referencing this volume.