Repository navigation
Conversation
d0a42b0 to
8e5ed11
Compare
8e5ed11 to
5d70d82
Compare
|
A few tradeoff questions before this becomes the contract other drivers build against:
|
Short version: for the driver-produced documents there is no channel to pull Where each document is needed:
The descriptor and boundary config also describe facts that belong to the Shared supervision already works the way you describe. The registration material What a hybrid could do: keep a small pushed bootstrap (trust anchor, gateway |
Fair question. Today the answer is In #5509 it is an optional dependency of I see three ways to deal with that:
I would choose the third: write binary protobuf on disk. That removes the On the golden files: the cross-language check has not been done yet. They are |
5d70d82 to
07c1910
Compare
3453142 to
e1708b9
Compare
e1708b9 to
f1ea65f
Compare
Add proto/sandbox_runtime.proto as the language-neutral specification of the runtime descriptor and the boundary configuration, written as binary protobuf. The file does not import compute_driver.proto, so it repeats ResolvedWorkloadIdentity and DriverFenceEvidence; a test in openshell-core fails if the copies drift. openshell-driver-contract generates the messages with ordered maps so that equal documents encode to equal bytes, exposes the descriptor set, and converts between the model types and the messages, validating on the way back. Golden protobuf JSON examples stand for the binary documents in a form that can be reviewed; the tests build the binary from them with a dev-only reflection helper and check both directions against the legacy examples. openshell-driver-sdk re-exports the generated messages. Signed-off-by: Evan Lezar <elezar@nvidia.com>
f1ea65f to
9f629e4
Compare
Summary
Specify the runtime descriptor and the boundary configuration as protobuf messages, written as binary protobuf, so non-Rust drivers and backends can produce and read them.
Related Issue
Part of #5456. Stacked on #5488.
Changes
proto/sandbox_runtime.proto. It does not importcompute_driver.proto, so it repeatsResolvedWorkloadIdentityandDriverFenceEvidence. A test inopenshell-corefails if the copies drift. Merging them is a follow-up.openshell-driver-contractgenerates the messages with ordered maps so equal documents encode to equal bytes, exposes the descriptor set, and converts between the model types and the messages, validating on the way back.openshell-driver-sdkre-exports the messages.Release Notes
None.
Testing
rust:deny:policy,buf lintandbuf breakingpass at this tip. Theopenshell-driver-vmtests were not run to completion: they needmke2fs, which was unavailable locally.Checklist