lei.chen/myxce
1
0
Fork 1
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs(steering): resource decision and question log (PR-1..3 proposals, R/P/N items)

Browse source 
Persistent log of the resource-design discussion: the user's proposals
(generic supply map incl. provisioned supply; a resource provider proxy
between the controller and upstream providers; datasets in the map with
staging as data provisioning) with analysis, the user's 2026-10-11 input
(duration/decay must-have but future; RBAC in the apiserver, discuss later;
OCI containers via application profiles; CSI compatibility preferred;
GPU/topology scheduler-first and extensible), the open R1-R9/P1-P9 items
and new questions N1-N4, C3. resource-model.md, the provisioner research,
roadmap and CLAUDE.md point at it.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
Rongsong Shen 2026-10-12 04:00:47 +00:00
parent bab73826f0
commit 5b05d51b7a
Signed by untrusted user: rshen
GPG key ID: 80533536B0EB651C
5 changed files with 99 additions and 21 deletions
Download patch file Download diff file Expand all files Collapse all files

21
.kiro/steering/resource-model.md
View file

@ -204,22 +204,5 @@ device-plugin **wire protocols** is open decision 4.
**Config-only now:** document the static custom resources that already
work.
## Open decisions (user, pending)
1. Phase 1 scope: `resource-distribution-mapping` option 2 now with option 3
as `custom-resource-reporting`, or option 3 in one spec?
2. Who reports runtime custom values: worker-run scripts (`posix_spawn`), a
separate reporter role, or both?
3. Are claims first-class REST/RBAC objects owned by a project from v1, and
do they count against project quotas?
4. Should XCE keep its own JSON provider contract, or be wire-compatible with
CSI and device plugins to reuse their drivers (gRPC sidecar, container
runtime coupling)?
5. How deep is the topology model: host plus switch block, or per-GPU/NIC
graphs?
6. Will OCI containers be an execution mode? It decides how dataset and
weights volumes are published into a job.
7. Who changes MIG layouts: a provider automatically, or an admin?
8. Should `rusage` `duration`/`decay` be honoured now (licenses need it)?
9. Is data staging part of `job-sandbox-execution`'s workspace work, or
`resource-claims`?
## Open decisions
Kept in `resource-questions.md`, the persistent decision and question log (R1–R9 from this document, the provisioner's P1–P9, new questions, and proposals PR-1 to PR-3 that may reshape the phases above: one supply map that includes provisioned supply, a resource provider proxy, datasets in the map with staging as provisioning). Check it before writing requirements for any phase.