feat(resources): cf-orch GPU VRAM orchestration — Plan A core #1
No reviewers
Labels
No labels
architecture
backlog
enhancement
module:documents
module:hardware
module:manage
module:pipeline
module:voice
priority:backlog
priority:high
priority:medium
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: Circuit-Forge/circuitforge-core#1
Loading…
Reference in a new issue
No description provided.
Delete branch "feature/cforch-core-orchestration"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Summary
circuitforge_core.resources— the cf-orch (CircuitForge Orchestration) VRAM lease management system(node_id, gpu_id)pair with asyncio lock; evicts lower-priority holders when VRAM is exhaustednvidia-smi, accepts/evictcalls (SIGTERM → grace → SIGKILL)OrchestratorClientwithvram_lease()async context manager for guaranteed releasecf-orchCLI (typer):start,agent,status,install-servicecompose.yml) for coordinator + agent with NVIDIA GPU device mappingTest Plan
pip install -e .[orch]→cf-orch statusdocker compose -f circuitforge_core/resources/compose.yml upon NVIDIA hostNotes
_call_agent_evictis a stub; real process eviction deferred to Plan B