tao-data-io
tao-data-io
Get data to and from the compute container. Decide the storage tier first —
under strategy A (pre-positioned mount) no bytes move at all — and when a
fetch is needed, move it host-side with aws/s5cmd/boto3/huggingface-cli/ngc
directly — no nvidia-tao-sdk, no in-container runtime. Other platform skills
call this skill to stage inputs before launch and sync outputs after. It never
launches a container itself. The chosen tier is stamped into the job-record at
submit.
When NOT to invoke this skill: if the inputs are already readable from the compute frame (a local path on the execution host, an existing Lustre/PVC/bind mount), that IS tier A — record it and skip this skill entirely; there is nothing to move. Air-gapped hosts: tier A is the only tier — never attempt an S3/HF/NGC fetch; anything missing (datasets, checkpoints, and the container images themselves) must be pre-positioned by the operator, and the preflight's readability check is the only data step that runs.