o2r packaging: arize_phoenix layer - bootstrap container + Phoenix chart #48
Labels
No labels
burndown-2026-06
coherence-core
consult
headless
interactive
P0
P1
P2
P3
P4
No milestone
No project
No assignees
1 participant
Due date
No due date set.
Dependencies
No dependencies set.
Reference
coilyco-flight-deck/otel-a2a-relay#48
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Part of #45 (per-layer isolated-unit packaging).
Layer:
arize_phoenix(otel-a2a-relay-arize-phoenixv0.3.0) - Phoenix backend extension. Ships CLIso2r-harness,o2r-phoenix-bootstrap,o2r-view+ thevizGIF renderer. The "service" here is upstream Phoenix plus o2r's idempotent provisioner.Current
arize_phoenix/docker/docker-compose.ymlonly pulls the upstream Phoenix image. This issue adds o2r's own tooling image + a chart that deploys Phoenix and runs the bootstrap.Docker
o2r-phoenix-bootstrap,o2r-harness), built with thevizextra. Runs as a Job/init, not a long-lived server.192.168.0.194:30500/otel-a2a-relay-arize-phoenix:<git-sha>.Helm
arize_phoenix/chart/: upstream Phoenix Deployment + Service + a post-install bootstrap Job that provisions the annotation configs (relay_failure_class,task_outcome_correct) and datasets (relay-decisions-golden,relay-failures-regression) via Phoenix's REST API.Acceptance
helm installstands up Phoenix and the bootstrap Job leaves the expected annotation configs + datasets present (idempotent on re-run).Deferred per Kai (2026-06-02) - skip the Phoenix deploy for this packaging pass. Tracked under #45; reopen when the Phoenix leg comes back into scope.