Configuring Lite Cluster Storage
The available storage space is determined by dockerBaseSize when no external storage is mounted. However, the accessible storage space is limited. It is recommended that you mount external storage to overcome this limitation.
You can mount storage to a container in various methods. The recommended method depends on the scenario. Table 1 lists the details. For details about container storage, see Storage Basics. You can learn about data disk space allocation by referring to Space Allocation of a Data Disk and adjust the data disk size as required.
Method |
Scenario |
Description |
Operation Reference |
---|---|---|---|
EmptyDir |
Training cache |
Kubernetes ephemeral volumes, which are created and deleted together with Pods following the Pod lifecycle. |
|
HostPath |
This method is suitable for:
|
Node storage. Multiple containers may share the storage, causing write conflicts. Deleting a Pod does not clear its storage. |
|
OBS |
Training dataset storage |
Object storage. The OBS SDKs are used to download sample data. Due to the large storage capacity being far from nodes, direct training speed is slow. To improve this, data is typically pulled to a local cache before training. |
|
SFS Turbo |
Massive amounts of small files |
|
|
SFS |
Persistent storage for frequent reads and writes |
This method applies to cost-sensitive workloads which require large-capacity scalability, such as media processing, content management, big data analytics, and workload analysis. SFS Capacity-Oriented file systems are not suitable for services with massive amounts of small files. |
|
EVS |
Persistent storage |
Each volume can be mounted to only one node. The storage size depends on the size of the EVS disk. |
Feedback
Was this page helpful?
Provide feedbackThank you very much for your feedback. We will continue working to improve the documentation.See the reply and handling status in My Cloud VOC.
For any further questions, feel free to contact us through the chatbot.
Chatbot