bluejay/bluejay-infra
1
0
Fork 0
Code Issues Pull Requests 14 Actions Packages Projects Releases Wiki Activity

docs(openvox): document quadlet durability smoke #12

Merged
bluejay merged 1 commits from codex/sprint32-openvox-quadlet-push into main 2026-05-18 04:53:07 +00:00
Conversation 0 Commits 1 Files Changed 4 +232
bluejay commented 2026-05-18 04:18:46 +00:00
Owner
Copy Link

Summary

  • document the Sprint 32 noc1 openvoxserver durability apply state
  • add an opt-in recreate smoke that refuses to remove the production container unless OPENVOX_RECREATE_SMOKE=1 and a generated openvoxserver systemd unit exists
  • add five lint tests guarding the runbook and smoke-script safety gates

Live apply status

  • Direct noc1 host edit applied because host Puppet is not installed and the Quadlet is not Puppet-managed.
  • /etc/containers/systemd/openvoxserver.container now has the persisted-key GIT_SSH_COMMAND line.
  • /etc/systemd/system/openvoxserver-safeconfig.service is enabled and active.
  • /opt/puppet/r10k-deploy.sh self-heals safe.directory and core.sshCommand before fetch.
  • puppet-deploy.service exits 0 and the control repo reports HEAD == origin/master.

Validation

  • bash -n scripts/monitoring/openvox-recreate-smoke.sh
  • dotnet test tests/bluejay-infra-lint/BluejayInfraLint.Tests.csproj -c Release --no-restore --filter FullyQualifiedName~OpenVoxServerDurabilityTests (5/5)
  • Full lint suite has unrelated baseline failures in UpdateCenter public route POST allowlist and existing GitHub runner init-container assumptions.

Do not self-merge.

## Summary - document the Sprint 32 noc1 openvoxserver durability apply state - add an opt-in recreate smoke that refuses to remove the production container unless OPENVOX_RECREATE_SMOKE=1 and a generated openvoxserver systemd unit exists - add five lint tests guarding the runbook and smoke-script safety gates ## Live apply status - Direct noc1 host edit applied because host Puppet is not installed and the Quadlet is not Puppet-managed. - /etc/containers/systemd/openvoxserver.container now has the persisted-key GIT_SSH_COMMAND line. - /etc/systemd/system/openvoxserver-safeconfig.service is enabled and active. - /opt/puppet/r10k-deploy.sh self-heals safe.directory and core.sshCommand before fetch. - puppet-deploy.service exits 0 and the control repo reports HEAD == origin/master. ## Validation - bash -n scripts/monitoring/openvox-recreate-smoke.sh - dotnet test tests/bluejay-infra-lint/BluejayInfraLint.Tests.csproj -c Release --no-restore --filter FullyQualifiedName~OpenVoxServerDurabilityTests (5/5) - Full lint suite has unrelated baseline failures in UpdateCenter public route POST allowlist and existing GitHub runner init-container assumptions. Do not self-merge.
bluejay added 1 commit 2026-05-18 04:18:52 +00:00
docs(openvox): document quadlet durability smoke 29965c45d6
bluejay merged commit 89b147bbdd into main 2026-05-18 04:53:07 +00:00
bluejay deleted branch codex/sprint32-openvox-quadlet-push 2026-05-18 04:53:09 +00:00
Sign in to join this conversation.
Reviewers
No Reviewers
Labels
No items
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
bluejay
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: bluejay/bluejay-infra#12
Delete Branch "codex/sprint32-openvox-quadlet-push"

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?