Skip to content

Define shared Slurm configuration and execution-plan contracts #873

Description

@nabinchha

Priority Level

High

Task Summary

Define the strict, versioned authored configuration and resolved-plan records shared across the optional Slurm package. These contracts must let planning, serving, image, client-worker, state, and benchmark lanes proceed without inventing incompatible boundary objects.

Technical Details & Implementation Plan

  • Define authored run configuration records for the Data Designer builder input, public invocation settings, client environment, deployments, and profile selection.
  • Define cluster-profile and deployment/server records needed by planning without embedding scheduler commands or runtime helper objects.
  • Define immutable resolved-plan records that pin shard intent, placement, resource requirements, artifact references, images, mount mappings, and public invocation inputs.
  • Define the shared image, semantic client-result, and benchmark records consumed by later implementation lanes.
  • Keep records strict, explicitly versioned, deterministic, and free of credential or secret values.
  • Add cross-record identity and digest checks plus sanitized golden JSON fixtures.

Acceptance criteria

  • Unknown fields, missing or invalid versions, malformed identities, and invalid digests fail clearly.
  • Equivalent authored inputs resolve to byte-for-byte deterministic plan records.
  • Shared records depend only on public Data Designer APIs and package-owned value types.
  • Secret material is represented only by external references or approved environment bindings, never serialized values.
  • Golden fixtures cover authored input, resolved plans, image references, client results, and benchmark intent.
  • The optional package remains importable without Slurm tools or runtime services installed.

Out of scope

  • Scheduler command execution or parsing.
  • vLLM serving resolution.
  • Image import/build operations.
  • Runtime persistence, retries, collection, or benchmark execution.

Investigation / Context

This is the remaining shared-contract foundation item in #850. Runtime and state records are tracked separately by #865.

Agent Plan / Findings

Freeze only records that cross package, process, or implementation-lane boundaries. Keep lane-local helper objects private to their implementation.

Dependencies

Depends on #851, #852, #853, and coordination with #865. Blocks the planning, serving, image, client-worker, state, and benchmark implementation lanes in #850.

Metadata

Metadata

Labels

taskInternal development task

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions