[FEATURE] Build scenario workloads through the owned native graph #594

Open
opened 2026-11-08 11:07:53 +01:00 by erikinkinen · 0 comments
Owner

Problem and motivation

The complete native image graph cannot currently express the directory workload used by the VM scenario. Runtime configuration alone does not select its client features, C probes, Rootd factory policy or launch catalog. Replacing the normal Posixd product would also remove a required service.

Proposed behavior and scope

Add an explicit, source-bound scenario recipe to the owned native graph. Keep all 77 component roles and 79 existing actions, then add the directory client as a genuine registered ProcessRoot companion action. Its product has a distinct identity while retaining the original Posixd and libc source dependencies. Project the actual Rootd, Exsh, client, C probe and image policies from the selected recipe.

Reuse the existing owned ProcessRoot producer and current VFS installer and Exsh catalog implementations. Do not substitute a Cargo label, generic image or previously produced ELF for the companion build.

Authority, security and reliability

The same original graph owns source, compiler, library, companion-product and image inputs through their required lifetimes. Names, records and saved outcomes cannot recreate ownership. Preserve existing action bounds, aggregate deadlines, source identities, sticky refusal and cleanup. Additional work must be admitted explicitly under the existing graph allowance and the genuine producer's declared limits; it must not enlarge unrelated service budgets.

Acceptance criteria

  • Bind scenario selection and every recipe input to the selected original source.
  • Retain every existing role and action; add a distinct registered companion with complete source/library/tool dependencies and product custody.
  • Carry genuine client features, C probes, heap policy, Rootd launch policy, current VFS installer and Exsh catalog into the final image.
  • Reject substituted recipes, missing or extra products, incompatible metadata and restored inputs after a sticky failure.
  • Exercise real companion compilation and image assembly through defining owners, then boot the authenticated directory scenario and require its actual workload marker.
  • Document the interfaces, ownership boundaries and remaining acceptance limits.

Alternatives and tradeoffs

The established legacy scenario route can build the workload, but does not demonstrate the repaired same-owner graph-to-image path. Adding features alone misses the companion producer and its C inputs. A registered companion extends the graph with real work instead of replacing an existing service or imposing a fixed action-count ceiling.

Tracking and rollout

Depends on clean native image production, the current installer and explicit Exsh catalogs. Select the coordinated counted-name component revisions before the fresh image build.

## Problem and motivation The complete native image graph cannot currently express the directory workload used by the VM scenario. Runtime configuration alone does not select its client features, C probes, Rootd factory policy or launch catalog. Replacing the normal Posixd product would also remove a required service. ## Proposed behavior and scope Add an explicit, source-bound scenario recipe to the owned native graph. Keep all 77 component roles and 79 existing actions, then add the directory client as a genuine registered ProcessRoot companion action. Its product has a distinct identity while retaining the original Posixd and libc source dependencies. Project the actual Rootd, Exsh, client, C probe and image policies from the selected recipe. Reuse the existing owned ProcessRoot producer and current VFS installer and Exsh catalog implementations. Do not substitute a Cargo label, generic image or previously produced ELF for the companion build. ## Authority, security and reliability The same original graph owns source, compiler, library, companion-product and image inputs through their required lifetimes. Names, records and saved outcomes cannot recreate ownership. Preserve existing action bounds, aggregate deadlines, source identities, sticky refusal and cleanup. Additional work must be admitted explicitly under the existing graph allowance and the genuine producer's declared limits; it must not enlarge unrelated service budgets. ## Acceptance criteria - [x] Bind scenario selection and every recipe input to the selected original source. - [x] Retain every existing role and action; add a distinct registered companion with complete source/library/tool dependencies and product custody. - [ ] Carry genuine client features, C probes, heap policy, Rootd launch policy, current VFS installer and Exsh catalog into the final image. - [x] Reject substituted recipes, missing or extra products, incompatible metadata and restored inputs after a sticky failure. - [ ] Exercise real companion compilation and image assembly through defining owners, then boot the authenticated directory scenario and require its actual workload marker. - [x] Document the interfaces, ownership boundaries and remaining acceptance limits. ## Alternatives and tradeoffs The established legacy scenario route can build the workload, but does not demonstrate the repaired same-owner graph-to-image path. Adding features alone misses the companion producer and its C inputs. A registered companion extends the graph with real work instead of replacing an existing service or imposing a fixed action-count ceiling. ## Tracking and rollout Depends on [clean native image production](https://git.erikinkinen.fi/erix/integration/pulls/574), [the current installer](https://git.erikinkinen.fi/erix/integration/pulls/582) and [explicit Exsh catalogs](https://git.erikinkinen.fi/erix/integration/pulls/583). Select the coordinated counted-name component revisions before the fresh image build.
erikinkinen added this to the Alpha 1 milestone 2026-11-08 11:07:53 +01:00
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
erix/integration#594
No description provided.