Volumes

Prev Next

Available in VPC

Get an overview the Volumes interface. From Volumes, you can create and delete volumes, or view a list of running volumes. You can also view the details and recent event history of running volumes.

Volumes

The Volumes interface includes the following components:

mlxp_console_volumes01_ko

Component Description
① Menu name Current menu name.
② Basic features Create/Delete a volume.
③ Volume list View the list and details of running volumes.

View volume list

View the list of running volumes and information on each server. The Volume list provides the following information.

  • Volume name: Name of the volume set when initially created.
  • Date of creation: Date of initial creation.
  • Status: Status of the volume.
    • Ready: The volume has been created and set up with the information you entered.
    • Unavailable: The volume has been created with the information you entered, but is not yet mounted.
    • Terminating: The volume is being deleted.
  • Size: Size of the volume.
  • Access mode: Set how the volume is accessed from GPU instances.
    • ReadWriteOnce: The volume is accessed from a single node.
    • ReadOnlyMany: The volume needs to be accessed from multiple nodes at the same time.
    • ReadWriteMany: The volume needs to be accessed from multiple nodes at the same time.
  • Storage class: Storage type for the created volume.
  • Used by: GPU instance where the volume is mounted.
  • Operation: View the details of each volume.
Caution
  • A local path volume provides NVMe storage. NVMe storage is physically connected to a specific host and is assigned directly to a GPU instance.
  • When a GPU instance is moved to another host via failover or host migration, the NVMe storage attached to the original host does not automatically migrate. As a result, you cannot access the existing NVMe data from the GPU instance that is moved to a different host.
  • We recommend using Data Manager, NCloud Storage, or Object Storage for data that require long-term retention.

Create a volume

To create a new volume:

  1. Click [Add].
  2. When the Create volume page appears, enter a name for the volume.
    • The name should be between 3 and 30 characters long and include lowercase letters (a-z), numbers (0-9), and hyphens (-).
    • Begin with a letter and end with a letter or number.
    • Duplication is not allowed.
  3. Enter the size of the volume.
  4. Select the storage class for the volume you want to create.
Caution
  • A local path volume is mounted directly on a GPU node and its capacity is managed by the user. Check the file system capacity using the df -k command and ensure usage remains below 80% of the total capacity.
  • A DDN volume provides a pre-agreed capacity. The total combined capacity of DDN volumes used across multiple projects cannot exceed the pre-agreed capacity per workspace.
  • To view available storageClass, use the following commands.
$ kubectl -n {project namespace} resourcequota
{resourcequota name} ... exa-h100-0.storageclass.storage.k8s.io/requests.storage: 0/300Ti

Local storage (NVMe) and high performance storage (DDN) have the following characteristics.

  • Local storage: This is storage that belongs to a specific host in the ReadWriteOnce mode and cannot be read or written from other hosts, and concurrent read/write on the same host is not possible. However, it can be read/written at the fastest speed than any other storage.
  • High performance storage: It is located on a remote server in the ReadWriteMany mode, which allows concurrent read/write from different hosts at high speeds. However, it is slower than local storage and can be slowed down by concurrent read/write from multiple nodes.
  1. Select an access mode.
    • ReadWriteOnce: The volume is accessed from a single node.
    • ReadOnlyMany: The volume needs to be accessed from multiple nodes at the same time.
    • ReadWriteMany: The volume needs to be accessed from multiple nodes at the same time.
  2. Click [Create].
Caution
  • It is normal for the status to display as Unavailable immediately after creation. You need to specify which node the volume should be assigned to. Once assigned to a specific node, the status also automatically changes.
  • You can either use the kubectl describe pvc <pvc-name> command or check the Event tab on the Volume details page for the message: "Waiting for first consumer to be created before binding."

Delete a volume

To delete a running volume:

  1. Select the volume you want to delete and click [Delete]
  2. In the Delete volume popup window that appears, enter the name of the volume to be deleted, and then click [Delete]
  3. Verify that the selected volume has been deleted from the Volume list.

View volume details

You can view the details of the selected volume. The details are divided into tabs.

Overview

These tabs include:

  • Access mode: Set how the volume is accessed from GPU instances.
    • ReadWriteOnce: The volume is accessed from a single node.
    • ReadOnlyMany: The volume needs to be accessed from multiple nodes at the same time.
    • ReadWriteMany: The volume needs to be accessed from multiple nodes at the same time.
  • Size: Size of the volume.
  • Storage class: Storage type for the created volume.
  • Volume mode: Filesystem
  • Volume name: Name of the volume set when initially created.
  • Owned by: Name of the project to which the volume belongs.
  • Pods mounted: Mounted PVCs.

Events

You can view the history of recent events for the selected volume.

  • Type: Type of the event that occurred.
  • Reason: Name of the event that occurred.
  • Created at: Date and time when the event occurred.
  • Message: Description of the event that occurred.

YAML

Shows the settings for the selected volume in the YAML format.

Note

You can only view these details, but not edit them, from the console.