Storage and PVCs
How storage works on zCLOUD, and how to make sure your data survives.
Files that a task needs afterwards belong on a persistent volume claim (`PVC`) or in S3, not in the task's own container. [**Storage Management**](https://console.zettabyte.com/storage-manage/index) covers both, in the **PVC Storage Management** tab and the **S3 Object Storage** tab. Stat cards at the top summarise `PVC` quota, S3 quota, and overall usage.
The mental model
Think of a Storage Volume (`PVC`) as a persistent file system, like a network drive attached to your work. It exists independently of any single task and keeps your files between runs.
Storage Volumes (PVCs)
The **PVC Storage Management** tab lists shared volumes, also referred to as Storage Volumes elsewhere in the console. Each volume shows Name, Type, Usage, Capacity, Status, and Creation Time. Volumes are Kubernetes `PVCs`. The **Edit** item in the row menu opens **Update PVC**, where you can change the capacity.
- You can create `PVCs` with **Add PVC** and attach one or many to a task.
- A `PVC` holds folders and files (code, datasets, checkpoints, weights) that persist across tasks.
- Size and quota: a `PVC`'s size is bounded by the storage allocated to your tenant. Quota is per-tenant, and getting more capacity is handled through your distributor or account owner.
What persists vs. what's cleared
This is the one thing every user must know
When a task ends, anything not written to a persistent volume (a `PVC`) or to S3 is **deleted**. Ephemeral and in-container data do not survive. Always write outputs you care about (weights, checkpoints, logs you want to keep) to a mounted `PVC`.
Mounting storage into a task
In task, IDE, and deployment wizards, a Storage Volume mounts a `PVC` into your container at a path you specify.
- Attach a **Storage Volume** (`PVC`) and choose a mount directory, the path it appears at inside your container. On the task form, the field for this path shows **Enter container path**.
- Mount directories must be unique within a task.
- Example: mount a `PVC` at `/data`, then have your training write to `/data/checkpoints`.
Ephemeral volumes
An **Ephemeral Volume** is memory-backed scratch space, sized in GiB. Use it for temporary intermediate data. It is cleared when the task ends, so never store anything you need to keep here.
S3
The **S3 Object Storage** tab lists buckets with Bucket Name, Object Count, Storage Quota, Storage Usage, Access Permission, and Creation Time.
You can also bring your own object storage into a task with **+ S3** in the Storage section. Provide an access key, a secret key, a mount directory and an S3 path. This is useful for large datasets and artifacts you manage outside zCLOUD. S3 details are entered in each task, IDE, or deployment form that needs the bucket.
The object store is S3-compatible, so you can access it with the AWS SDK. From a job or IDE, create a client with your endpoint and keys:
import boto3
s3 = boto3.client(
"s3",
endpoint_url="YOUR_S3_ENDPOINT",
aws_access_key_id="YOUR_ACCESS_KEY",
aws_secret_access_key="YOUR_SECRET_KEY",
)
for bucket in s3.list_buckets()["Buckets"]:
print(bucket["Name"])
Limits
- Quota is per-tenant; increases go through your distributor or account owner.
Troubleshooting
- Data disappeared after a task: the files may not have been written to a mounted `PVC` or to S3. Write anything you need to keep to a mounted `PVC` or to S3.
- Cannot mount two volumes: mount directories must be unique. Give each volume a distinct path. See [Cannot mount two volumes on one task](https://docs.zettabyte.com/docs/zcloud/troubleshooting/cannot-mount-two-volumes).
- Out of space: the `PVC` is full, or your tenant quota is used up. The capacity of one `PVC` is changed in the **Update PVC** dialog described under Storage Volumes (PVCs). More tenant quota comes through your distributor or account owner.
Next steps
- [Run a training job](https://docs.zettabyte.com/docs/zcloud/tasks/run-a-training-job): mount storage into a task so outputs persist.
- [Bring your own model or dataset](https://docs.zettabyte.com/docs/zcloud/models-data-storage/bring-your-own-model-dataset): use your own weights or data.