Available in VPC
This guide describes the Volumes interface. In Volumes, you can create and delete Volumes and view the list of active Volumes. You can also view details and recent event history of active Volumes.
Volumes
The Volumes interface includes the following components:
| Component | Description |
|---|---|
| ① Menu name | Current menu name. |
| ② Basic features | Create and delete a Volume. |
| ③ Volume list | View active Volumes and their information. |
View Volume list
You can view the list of active Volumes and information by server. The Volume list includes the following information:
- Volume name: Volume name set at creation.
- Creation date: Initial creation date and time.
- Status: Volume status.
- ready: Volume creation and configuration are completed based on the information you entered.
- unavailable: Volume creation is completed based on the information you entered, but the Volume is not mounted.
- terminationg: Volume deletion is in progress.
- Size: Volume size.
- Access Mode: Access method configured for GPU instances.
- ReadWriteOnce: Access from a single node.
- ReadWriteMany: Access from multiple nodes simultaneously.
- Storage Class: Storage type used to create the Volume.
- Used by: Mounted GPU instance.
- Operation: View details for each Volume.
Caution
- Local Path volumes provide NVMe storage. NVMe is storage physically attached to a specific host and is directly assigned to GPU instances.
- If a GPU instance moves to another host due to failover or host migration, the NVMe storage connected to the original host does not automatically move with it. As a result, the GPU instance moved to another host cannot access the existing NVMe data.
- Therefore, for data requiring long-term storage, use Data Manager, NCloud Storage, or Object Storage.
Create a Volume
To create a new Volume:
- Click [Add].
- In the Volume creation interface, enter a Volume name.
- Enter 3-30 characters using lowercase letters (a-z), numbers (0-9), and hyphens (-).
- It must start with an English letter and end with an English letter or a number.
- Duplicate names are not allowed.
- Enter the size.
- Select a Storage Class for the Volume.
Caution
- ML expert Platform currently provides NVMe-based Local Path volumes and DDN-based high-performance storage.
- Local Path volumes are mounted directly to GPU nodes. You must manage their capacity manually. Use the
df -kcommand to check filesystem capacity and ensure that you maintain usage below 80% of the total capacity. - If Local Path volumes use the full disk size allocated to all nodes, the Pod may be evicted by the default Kubernetes behavior.
- DDN volumes provide capacity agreed upon in advance. The total DDN capacity used across multiple projects cannot exceed the capacity agreed in advance for each Workspace.
- You can access DDN volumes only if the image UID/GID is set to 500.
- Do not set
fsGroupin thesecurityContextof Pods that mount DDN volumes. SettingfsGroupcauses Kubernetes to recursively change the ownership of all files in the mounted volume. For high-performance storage containing large amounts of data, this can make Pod initialization extremely slow. - Use the following command to check available
storageClass:
$ kubectl -n {project namespace} resourcequota
{resourcequota name} ... exa-h100-0.storageclass.storage.k8s.io/requests.storage: 0/300Ti
Local Path volumes (NVMe) and DDN volumes have the following characteristics:
- Local Path volume: Supports
ReadWriteOncemode. As this storage is tied to a specific host, you cannot read from or write to it from other hosts. However, it offers the fastest read/write speeds compared to any other storage type. - DDN volume: Supports both
ReadWriteOnceandReadWriteManymodes. Since this is remote storage, you can perform high-speed simultaneous read/write operations across different hosts. However, it is inevitably slower than local storage. Read and write performance may decrease when reads and writes occur concurrently across all nodes.
- Select an Access Mode.
- ReadWriteOnce: Access from a single node.
- ReadWriteMany: Access from multiple nodes simultaneously.
- Click [Create].
Caution
- After creation, it is normal for the status to appear as Unavailable. You must specify which node to assign the Volume to. The status changes as soon as the Volume is assigned to a specific node.
- In the Event tab of the Volume details interface or when using the
kubectl describe pvc <pvc-name>command, you may see the message, "Waiting for first consumer to be created before binding."
Delete a Volume
To delete an active Volume:
- Select the Volume to delete, then click [Delete].
- When the Delete Volume popup appears, enter the name of the volume to delete, then click [Delete].
- Confirm that the Volume has been removed from the Volume list.
View Volume details
You can view details for the selected Volume. The information is organized into tabs.
Overview
The selected Volume includes the following information:
- Access Mode: Access method configured for GPU instances.
- ReadWriteOnce: Access from a single node.
- ReadWriteMany: Access from multiple nodes simultaneously.
- Size: Volume size.
- Storage Class: Storage type used to create the Volume.
- Volume mode: Filesystem
- Volume name: Volume name set at creation.
- Owned by: Name of the project to which the Volume belongs.
- Pods Mounted: Information on the mounted PVC.
Events
You can view the recent event history of the selected Volume.
- Type: The type of event that occurred.
- Reason: The name of the event that occurred.
- Created At: Date and time when the event occurred.
- Message: Description of the event that occurred.
YAML
This tab displays the configuration of the selected Volume in YAML format.
Note
You can only view it in the console. You cannot edit it.