Jon Chery
4c2e59cf3f
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---
52 lines
1.1 KiB
Markdown
52 lines
1.1 KiB
Markdown
---
|
|
kind: Service
|
|
name: postgres
|
|
count: 1
|
|
runtime:
|
|
one_of: process
|
|
command: /bin/sleep 3600
|
|
ports:
|
|
- name: pg
|
|
port: 5432
|
|
restart:
|
|
mode: service
|
|
attempts: 5
|
|
delay: 10s
|
|
update:
|
|
strategy: blue-green
|
|
min_healthy_time: 60s
|
|
healthy_deadline: 10m
|
|
service:
|
|
name: postgres
|
|
port: 5432
|
|
health:
|
|
check_type: http
|
|
interval: 15s
|
|
timeout: 5s
|
|
unhealthy_threshold: 3
|
|
volumes:
|
|
- name: data
|
|
type: host
|
|
source: replicate:peer-b,peer-c
|
|
target: /var/lib/postgresql/data
|
|
read_only: false
|
|
constraints:
|
|
- node.role == "db"
|
|
- node.cpus >= 4
|
|
- node.memory >= 8192
|
|
env:
|
|
POSTGRES_DB: appdb
|
|
POSTGRES_USER: orca
|
|
PGDATA: /var/lib/postgresql/data
|
|
---
|
|
# PostgreSQL
|
|
|
|
Database service with a single replica, blue-green update strategy,
|
|
and volume replication via Syncthing (replicate:peer-b,peer-c). The
|
|
data volume is replicated to two peers for fault tolerance. Health
|
|
check on port 5432. Constraints require DB-role nodes with >= 4 vCPUs
|
|
and >= 8 GiB memory.
|
|
|
|
> **Production substitution**: replace `runtime.command` with your
|
|
> actual postgres binary, e.g.
|
|
> `/usr/lib/postgresql/16/bin/postgres -D /var/lib/postgresql/data`. |