A public OIDC client (PKCE S256, no secret) for the WikiDeck testnet UI
and the Capacitor apps. Its redirect URIs are the three private testnet
nodes on poweredge-r350 and the dev.eom.wikideck custom scheme. The
www-membership client stays gated on www_dex_client_secret, as before.
Rendered with Ansible against both secret cases. Prepared by the sso agent
(claude/wikideck#7) and reviewed and applied by the coordinator.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bumps debian, libvirt-guest, ingress-nginx, grafana, nextcloud, minio,
tor-controller and mediawiki to commits that add only a manual-only
lint caller, a lint baseline and (tor-controller, mediawiki) a fixed
role name in tests/test.yml. Nothing these roles deploy changes.
adding-ci.md: rollout table, test results, and a note not to baseline
syntax-check findings.
Refs DevOps/software-infrastructure#54
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
CI files only (.gitea/workflows/lint.yaml and .ansible-lint-ignore);
nothing the roles deploy changes. ansible-role-discourse got the same
caller but isn't a submodule here.
Refs DevOps/software-infrastructure#53
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Galaxy-skeleton tests/test.yml files name the role either by its repo
name (ansible-role-x) or its bare name (x). ansible-role-eom uses the
bare name, which made syntax-check fail, and syntax-check can't be
baselined. Link both aliases to the linted copy. Update the documented
baseline command and the test table.
Refs DevOps/software-infrastructure#53
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ansible-lint was flagging callers' workflow files (yaml[truthy] on `on:`),
which actionlint already checks. Exclude .gitea/ in the reusable workflow
and in the documented baseline command. Note that .ansible-lint-ignore is
per file and rule, not per line.
Refs DevOps/software-infrastructure#53
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- reusable-helm-lint: new `render-defaults` input (default true) for charts
whose templates require values the defaults leave empty.
- Lint each values set, not only the defaults.
- Render to a named .yaml file and fail if nothing rendered; kubeconform
passes on empty input and skips files without a .yaml extension.
- docs/ci-cd/adding-ci.md: placeholder-values convention, G7 rollout table,
test results.
Refs DevOps/software-infrastructure#55
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
.gitea/scripts/check-playbooks.sh runs ansible-playbook --syntax-check on
every top-level playbook and ansible-lint (production profile, with
yamllint's rules) on the repo's own files, in a temporary copy with empty
secrets stubs, so it never touches a real secrets file. Roles are excluded;
they're linted in their own repos.
Baselines so the check passes today and fails on new problems:
- .gitea/playbooks-skip.txt: nine playbooks that fail the syntax check now
(missing roles, an unknown module, an unfinished playbook), with reasons.
- .ansible-lint-ignore: 110 existing file/rule findings.
The workflow (.gitea/workflows/playbooks.yaml) is manual-only until S8 passes
and the ci-tools image is published; its header has the push/pull_request
trigger. Docs: docs/ci-cd/playbook-checks.md.
Refs DevOps/software-infrastructure#51
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Three workflow_call workflows that run in the shared CI tools image (G1):
- reusable-ansible-role-lint: ansible-lint (which includes yamllint's
rules) on a copy of the role named as the playbooks use it, with the
repo name also resolvable for galaxy's skeleton tests/test.yml.
role-name is a warning; .ansible-lint-ignore baselines are honoured.
- reusable-helm-lint: helm lint, then helm template | kubeconform for
Kubernetes 1.31.2, with optional extra values files.
- reusable-dockerfile-lint: hadolint on every Dockerfile, threshold
warning by default.
docs/ci-cd/adding-ci.md has caller templates, inputs, the baseline
command, and what was and wasn't tested.
Tested locally by running each workflow's steps verbatim in a local build
of the tools image: ansible-role-gitea fails as-is (48 findings), passes
with a baseline and fails on a new bad task; helm-jamulus passes, a
missing-value template and an invalid Service fail; the tools Dockerfile
passes and an unpinned one fails. Not yet run on the runner, and
cross-repo uses: is untested. No callers added, so no runs start.
Refs DevOps/software-infrastructure#50
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add a reusable workflow that downloads a pinned, checksum-verified gitleaks
and scans the pushed commits, the PR's commits, or the current tree. Logs
show only a count, never the rule, file, line or value, because the logs
are public. This repo's caller is manual-only until S8 passes.
.gitleaks.toml extends the default rules and allowlists Helm checksum/*
annotations. docs/ci-cd/secret-scanning.md covers usage, what to do when it
fails, and the policy for history scans (done privately, not in CI).
Tested locally by running the step verbatim in a container against
throwaway repos: a planted fake token fails on push, new-branch push and PR;
clean ranges, checksum annotations and this repo's tree pass; a bad
checksum fails; the value never appears in the output. actionlint and
yamllint pass.
Refs DevOps/software-infrastructure#57
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add images/ci-tools: one image with ansible 14.6.0 (core 2.21.6),
ansible-lint, yamllint, helm 3.22.1, kubeconform, actionlint, hadolint,
gitleaks and node 24 for JavaScript actions. Python tools are pinned in
requirements.txt; binaries are pinned by version and the SHA-256 from
each release's checksum file. VERSION starts at 1.0.0.
Add a manual-only ci-tools-image workflow that builds and smoke-tests
the image, and publishes an immutable version tag only when Eric enables
CI_TOOLS_PUBLISH and adds a registry token (after S8 and P1). A sample
job then uses the published image as its container.
Tested on the workstation: image builds, every tool reports its pinned
version, hadolint/actionlint pass on the new files, and syntax-check
passes for gitea.yaml, ci-runner.yaml and prometheus.yaml inside it.
Refs DevOps/software-infrastructure#49
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/ci-cd/credentials.md: no Actions secrets exist yet, rules for
adding them, which role variable serves which purpose, and how to
give each its own value safely.
- Bump the gitea role: gitea_mailer_password and
gitea_postgresql_password, defaulting to the current value.
Refs #47
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- docs/ci-cd/actions-inventory.md lists every `uses:` in the DevOps,
Gaming and claude repos, which of those workflows run on this Gitea,
and what needs a mirror (only actions/checkout today).
- deployLibvirt.yaml: pin actions/checkout (v4.4.0) and
dawidd6/action-ansible-playbook (v2.8.0) to commit SHAs.
- Bump the gitea role for the same pin in its demo workflow.
Refs #46
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds docs/ci-cd/soak/soak.yaml (20 soak jobs plus a control failure, for a
cicd-test repo) and docs/ci-cd/soak-test.md with preconditions, pass
criteria and the first evidence lining up silent job failures with runner
evictions. The runbook now says to cancel orphaned in-progress jobs before
rerunning.
Refs DevOps/software-infrastructure#41
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
ci-runner.yaml deploys the Gitea Actions runner on inspiron-3670 with
the gitea role's new actions_host.yaml (private Docker daemon for jobs,
same capacity, timeouts, job images and cleanup as the cluster runner).
Not applied; waiting on a decision in the issue.
Refs #45
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Add docs/ci-cd/runner.md: architecture of the shared Gitea Actions runner,
how to apply role changes, where to read logs, recovery steps for a stuck
queue, an evicted runner or a full Docker disk, and how to replace the
registration token without handling its value.
Describes the configuration committed for S3-S5; it becomes accurate for the
live runner once those are deployed. The S7 alerts already link here.
Refs DevOps/software-infrastructure#42
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bumps ericomeehan.www to d1084c7 and sets the public client IDs. The
client secrets come from www_membership_secret_data in the vault.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
data.log was a saved `kubectl get pods` listing with no purpose in the
repo. Ignore logs, Ansible retry files, merge leftovers, editor swap files
and Python caches so they don't get committed again. The rest of the root
is playbooks, inventories and config, all intentional.
Closes#60
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
funkwhale.yaml and harmony.yaml take the mail/LDAP password from
funkwhale_admin_password and harmony_admin_password (Vault); the roles keep
the accounts and their groups. Bumps ericomeehan.dex (harmony connector),
ericomeehan.funkwhale and ericomeehan.harmony.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds the ericomeehan.harmony role (DevOps/ansible-role-harmony) and
harmony.yaml, and bumps ericomeehan.dex for the harmony client. Vault:
harmony_dex_client_secret (new); mail reuses listmonk_smtp_password.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bumps the Dex role (funkwhale connector limited to the Funkwhale Users
LDAP group) and the funkwhale role (contrast fixes).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Adds the ericomeehan.funkwhale role and its play, and bumps the Dex role
for the new funkwhale client.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Pulls in DevOps/ansible-role-gitea@5fb2d9c: CPU and memory for the
runner and DinD, capacity 1, runner job and shutdown timeouts, pinned
job images, and Gitea's Actions zombie, endless and abandoned job
timeouts with log and artifact retention.
Refs #37
Refs #39
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The runner can now be applied with
`ansible-playbook gitea.yaml --tags actions` without touching the main
Gitea release, and the Gitea chart is pinned to 12.7.0.
Refs #35
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Agent-pool work kept the Tesla T4 at 94 C after the agents were
paused, and killing the backend only made it reload. Enable the busy
watchdog so no single request can hold the GPU indefinitely.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
A resident model holds the passively cooled Tesla T4 in P0 at about
30 W, which keeps the poweredge-t640 fans near 4,800 RPM. Unloading
idle models lets the card return to P8 at about 15 W.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The www membership app is the only checkout now. The plugin sold the same
Stripe prices with subscriber_level_0..4 groups that are off by one from the
site's Level 1-5 and bypassed the LDAP tiers. It is already disabled live
(discourse_subscriptions_enabled=false; it had 0 customers).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Bump the localai role to the commit that keeps agent, KB, config and backend
state on the models PVC and patches hostNetwork and the p2p token secret.
Set the playbook to p2p/federated off to match the live deployment: Eric
chose T4-only after p2p workers broke model loads.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Cluster-internal, read-only MCP servers (Gitea, Grafana, Nextcloud,
Discourse) for the LocalAI agent pool, acting as LDAP user localai.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>