2 Commits

Author	SHA1	Message	Date
Jon Chery	4c2e59cf3f	fix(P06): workloadToTaskSpecs command split + runnable examples ... Root cause: orca job run <example>.md failed with fork/exec: no such file or directory on every example. Two compounding problems: 1. workloadToTaskSpecs (internal/cli/job.go:340) passed the entire runtime.command string (e.g. "/usr/bin/httpd -f /etc/orca/web-app/ httpd.conf") as a single binary path to exec.Command, which then looked for a file literally named "/usr/bin/httpd -f ..." and failed. The v0.9 markdown parser stores command: as a raw string; the legacy HCL path had separate command+args fields. Fix: add splitCommand helper that splits on strings.Fields into binary+args, with /bin/true fallback for empty commands. 2. The example commands referenced binaries that don't exist on a bare Linux machine (/usr/bin/httpd, postgres, api-server, fluent-bit). Fix: rewrite the 5 example runtime.command values to use /bin/sleep 3600 (long-running services) or /bin/echo (one-shot job) so they run out-of-the-box. Each file has a Production substitution note showing the real binary to use in deployment. Verified: orca job run examples/full-stack/worker.md now succeeds (exit 0). All 4 services (web-app, api, log-shipper, postgres) start correctly (task started, pid assigned). 12 new unit tests pass (splitCommand: 7 cases, workloadToTaskSpecs: 5 cases). All 5 example jobspecs still parse + validate (gate C-20). make lint clean. ---ci--- project: orca phase: 6 milestone: v0.10 status: execute decisions: - id: D-195 decision: split command string via strings.Fields in workloadToTaskSpecs rationale: exec.Command expects binary path + args as separate elements; the v0.9 markdown parser stores command: as a single string with no args field (unlike legacy HCL). strings.Fields is dep-free and handles multiple spaces/tabs. Shell quoting (single/double quotes inside the command) is not handled — examples avoid sh -c with quoted strings. confidence: 0.95 alternatives: [shellquote.Split from mvdan/sh (adds dependency)] lessons: - The v0.9 markdown jobspec path needs the same command+args split that the legacy HCL path had via separate command/args fields. The parser stores command: as a raw string; the CLI must split it before passing to exec.Command. - Example jobspecs should use /bin/sleep and /bin/echo (binaries that exist on every Linux machine) so they run out-of-the-box. Descriptive production commands belong in a comment block, not in runtime.command. ---/ci---	2026-08-05 21:23:32 +00:00
Jon Chery	2c26a6d54f	docs(P03): full-stack examples — 5 jobspecs + rendered artifacts + walkthrough ... P03 — full-stack example with ingress configured (REQ-094; gate C-20). examples/full-stack/: - web-app.md: kind Service, process runtime, 3 replicas, Unix socket (default R-007), rolling update, constraints (node.role==web), affinity (zone==a weight 80), lifecycle hooks (post_start/pre_stop). - api.md: kind Service, process runtime, 2 replicas, TCP opt-in (service.bind: 127.0.0.1, R-007), canary update with manual promote, constraints (node.role==api, node.cpus>=2), env vars. - worker.md: kind Job, process runtime, one-shot, timeout 300s, env vars, lifecycle hooks (register/drain). - log-shipper.md: kind Service (DaemonSet workaround — parser gap), process runtime, constraints (node.role==logs), env vars. Notes the v0.9 parser gap (schedule: block not wired) in a callout. - postgres.md: kind Service, process runtime, 1 replica, blue-green update, volumes with replication (replicate:peer-b,peer-c via Syncthing), constraints (node.role==db, node.cpus>=4, node.memory>=8192). - rendered/: Traefik dynamic YAML (web-app, api) + systemd units (web-app, api, log-shipper) showing what Orca generates on target nodes. - README.md: end-to-end walkthrough (init -> node join -> capacity set -> ns create -> job run -> list --watch -> inspect rendered -> verify ingress -> drain/rollback). Cross-links to docs/ingress.md. - examples_test.go: Go test that parses + validates all 5 jobspecs against the current parser and schema validators (gate C-20). All 5 jobspecs pass jobspec.ParseFile + schema.ValidatorFor(kind). ---ci--- project: orca phase: 3 milestone: v0.10 status: execute ---/ci---	2026-08-05 20:59:33 +00:00