-
-
Notifications
You must be signed in to change notification settings - Fork 91
Build a fleet rollout mechanism #4898
Copy link
Copy link
Closed
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is neededExtra attention is neededroadmapOn the Wave-2 agent-layer roadmap board (project 9)On the Wave-2 agent-layer roadmap board (project 9)
Milestone
Description
Metadata
Metadata
Assignees
Labels
gittensor:featureGittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.Gittensor-scored feature linked to a feature issue — scores a 0.25x multiplier.help wantedExtra attention is neededExtra attention is neededroadmapOn the Wave-2 agent-layer roadmap board (project 9)On the Wave-2 agent-layer roadmap board (project 9)
Decision (ratified 2026-07-21):
pinned_versionfield on the control-plane's tenant record. A rollout is updating one or more tenants'pinned_version; rollback is reverting it for the affected tenant(s). Each tenant's container reads its own pinned version at (re)start rather than always pulling:latest.Problem: There's no way today to stage a new version across a fleet of instances, target a rollout at one customer, or roll one back without affecting others — every self-hoster pulls the same image tag from the same release channel.
Area: ORB / Fleet ops. Buildable now: #7180's control-plane provisioning core is decomposed into 4 real pieces (#7653, #7654, #7851, #7852).
Deliverables:
pinned_versionadded to the control-plane's tenant record (control-plane/src/tenant-provisioning-driver.ts'sTenanttype), product-agnostic (same shape for ORB and AMS tenants).pinned_version, not a shared:latesttag.Acceptance criteria:
AMS Cloud Readiness cross-reference (added 2026-07-12)
See also #5221 in the AMS Cloud Readiness milestone — the AMS-side parallel to this exact problem. Keep both sides in sync if either design changes.
Contributor-eligible. Decision ratified above; the per-tenant-independence test requirement is the safety guardrail against the fleet-wide blast-radius concern.