Skip to content

Managing Storage Volumes

Overview
Storage volumes, also known as Persistent Volume Claims (PVCs), provide workloads with persistent storage that outlasts the lifecycle of individual containers or pods. Typical examples include Jupyter Notebooks retaining user data, databases storing files, or shared workspaces in a multi-user environment.

Why Use Storage Volumes (PVCs)?

  • Persistence: Data remains intact even if the workload restarts or the node reboots.
  • Scalability: Volumes can be sized and resized (if supported) to match growing or shrinking requirements.
  • Flexibility: Different storage classes (e.g., NFS, block storage) can be used to meet specific performance or availability needs.

Access the Storage Volume Dashboard

  1. Log In
    • Sign in to the MemVerge AI platform with administrator credentials.

  2. Open “Storage”

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

    Storage Volume Dashboard

Key Operations

  1. Create a Volume

    • Define the Name, Project association, Storage Class, Requested Storage, and Access Mode.
    • This is typically done via the + New Volume dialog.
    • See the detailed Creating a Volume documentation for step-by-step instructions.

  2. Modify a Volume

    • Update volume attributes such as the requested size or access mode (if the underlying storage supports it).
    • Modifications usually involve resizing the volume or changing its properties to accommodate evolving workload requirements.
    • Refer to Modifying a Volume for a comprehensive guide.

  3. Delete a Volume

    • Remove a PVC that is no longer required to free up storage capacity.
    • Ensure that no workloads are actively using the volume to prevent data loss or application errors.
    • Check the Deleting a Volume section for more details and best practices.

Best Practices

  • Align volume size and performance characteristics with your workloads to optimize cost and resource usage.
  • Use the appropriate Access Mode (e.g., ReadWriteOnce vs. ReadWriteMany) to match how your workload will access the data.
  • Monitor disk usage and storage performance regularly to ensure your projects have enough capacity and performance headroom.