feat: fleet tab — download from public source or rsync to node when model is missing #64

Open
opened 2026-05-13 08:29:58 -07:00 by pyr0ball · 0 comments
Owner

Summary

When viewing a node in the fleet tab, models shown as ✗ (not installed) should offer two deployment paths:

  1. Download from public source — if hf_repo is set in the model registry, offer to initiate a HuggingFace download on the target node
  2. Rsync from another node — if the model exists on another cluster node, offer to rsync it across (faster than re-downloading from HF)

This allows one-click deployment from the Assignments deployment-status view.

UX sketch

Deploy ▾
  ├─ Download from HuggingFace  (if hf_repo set)
  └─ Sync from heimdall          (if model present on another node)

Backend needs

  • GET /api/assignments/deployment-status already cross-joins nodes × models
  • Need: endpoint to initiate HF download on a specific node
  • Need: endpoint to trigger rsync from node A to node B (or just provide the rsync command)
  • Consider: progress tracking / status polling for long-running downloads
  • avocet#63 (Assignments tab UI)
  • cf-orch#60 (task-model assignment layer spec)
## Summary When viewing a node in the fleet tab, models shown as ✗ (not installed) should offer two deployment paths: 1. **Download from public source** — if `hf_repo` is set in the model registry, offer to initiate a HuggingFace download on the target node 2. **Rsync from another node** — if the model exists on another cluster node, offer to rsync it across (faster than re-downloading from HF) This allows one-click deployment from the Assignments deployment-status view. ## UX sketch ``` Deploy ▾ ├─ Download from HuggingFace (if hf_repo set) └─ Sync from heimdall (if model present on another node) ``` ## Backend needs - `GET /api/assignments/deployment-status` already cross-joins nodes × models - Need: endpoint to initiate HF download on a specific node - Need: endpoint to trigger rsync from node A to node B (or just provide the rsync command) - Consider: progress tracking / status polling for long-running downloads ## Related - avocet#63 (Assignments tab UI) - cf-orch#60 (task-model assignment layer spec)
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference: Circuit-Forge/avocet#64
No description provided.