Repository navigation
Conversation
This was referenced Oct 26, 2026
zibi-pplx
force-pushed
the
pr943
branch
3 times, most recently
from
October 26, 2026 15:41
b993b9c to
5ec96f7
Compare
zibi-pplx
force-pushed
the
pr943
branch
2 times, most recently
from
October 26, 2026 22:07
f6c5dcf to
2d84180
Compare
## Summary Add node-local device enrollment, membership, allocation and active-claim tables, plus persisted sandbox device requirements. Separate physical parents from execution allocations so whole-device ownership does not require one owner field on the parent. Composite foreign keys enforce membership, and exclusive claims prevent two active exclusive holders of the same member. ## Validation Device-store tests exercised fenced admission, release, reset recovery, ownership snapshots and rollback guards during implementation. The migrations were applied on the dedicated development node used for the GPU lifecycle smoke test. Full workspace testing remains with CI. ## Severity and risk New additive SQLite schema. Deploy before the consumers in this stack. Down migrations refuse while enrollment/ownership history or sandbox requirements remain; binary rollback cannot silently turn device-bearing work into CPU-only work. No control-plane PostgreSQL change or automatic device enrollment. ## Stack GPU execution, after the CPU-only Cloud Hypervisor group. #962 is the first PR in this group and supplies the SQLite schema before #945 and the device consumers. Requirements, artifact delivery, fenced ownership, operator visibility and GPU smoke coverage follow. Device-bearing requests remain standalone-only. The scrub candidate in #950 is unqualified; this stack does not claim production-safe tenant reuse. Earlier review discussion remains in #944; this PR carries the same implementation in its new stack position. AI assistance: Codex implemented and validated the changes and drafted this description.
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add node-local device enrollment, membership, allocation and active-claim tables, plus persisted sandbox device requirements. Separate physical parents from execution allocations so whole-device ownership does not require one owner field on the parent. Composite foreign keys enforce membership, and exclusive claims prevent two active exclusive holders of the same member.
Validation
Device-store tests exercised fenced admission, release, reset recovery, ownership snapshots and rollback guards during implementation. The migrations were applied on the dedicated development node used for the GPU lifecycle smoke test. Full workspace testing remains with CI.
Severity and risk
New additive SQLite schema. Deploy before the consumers in this stack. Down migrations refuse while enrollment/ownership history or sandbox requirements remain; binary rollback cannot silently turn device-bearing work into CPU-only work. No control-plane PostgreSQL change or automatic device enrollment.
Stack
GPU execution, after the CPU-only Cloud Hypervisor group. #962 is the first PR in this group and supplies the SQLite schema before #945 and the device consumers. Requirements, artifact delivery, fenced ownership, operator visibility and GPU smoke coverage follow. Device-bearing requests remain standalone-only. The scrub candidate in #950 is unqualified; this stack does not claim production-safe tenant reuse.
Earlier review discussion remains in #944; this PR carries the same implementation in its new stack position.
AI assistance: Codex implemented and validated the changes and drafted this description.
Stack created with Sapling. Best reviewed with ReviewStack.
Base: #924, the separate Cloud Hypervisor installation stack.