Proposed runner on a dedicated host: playbook, role bump, runbook
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>
This commit is contained in:
@@ -0,0 +1,12 @@
|
||||
---
|
||||
# Gitea Actions runner on a dedicated host outside the cluster (I3,
|
||||
# DevOps/software-infrastructure#45). The runner's settings live in the
|
||||
# ericomeehan.gitea role (defaults/main.yml, tasks/actions_host.yaml).
|
||||
- name: Gitea Actions runner host
|
||||
hosts: inspiron-3670
|
||||
become: true
|
||||
tasks:
|
||||
- name: runner on its own Docker daemon
|
||||
ansible.builtin.import_role:
|
||||
name: ericomeehan.gitea
|
||||
tasks_from: actions_host.yaml
|
||||
@@ -191,6 +191,32 @@ hand.
|
||||
6. Confirm a single runner shows **Idle** in the admin page and a test workflow
|
||||
succeeds.
|
||||
|
||||
## Proposed: runner on a dedicated host
|
||||
|
||||
Not deployed. Proposed in DevOps/software-infrastructure#45 as the answer to
|
||||
I3 and S3: run the runner on `inspiron-3670` instead of in the cluster.
|
||||
|
||||
- **Layout.** Docker Compose project `gitea-runner` in `/opt/gitea-runner`:
|
||||
`dind` (a private Docker daemon that holds every job container, with data in
|
||||
`/var/lib/gitea-runner/docker`), `runner`, and `prune` (the same cleanup
|
||||
script as in the cluster). Jobs never see the host's own Docker daemon or
|
||||
its other containers.
|
||||
- **Settings.** Capacity, timeouts, job images and cleanup are the same
|
||||
variables as the in-cluster runner. Host-only ones are `gitea_actions_host_*`
|
||||
in the role's `defaults/main.yml`: 4 CPUs and 16 GB for jobs, and a CPU
|
||||
weight below the host's other containers.
|
||||
- **Apply.** `ansible-playbook ci-runner.yaml`. The first run fetches a
|
||||
registration token from the cluster, registers, and deletes the token file.
|
||||
Rerunning recreates only containers whose settings changed; that cancels a
|
||||
running job.
|
||||
- **Logs.** On the host: `docker compose -f /opt/gitea-runner/compose.yaml logs
|
||||
runner` (or `dind`, `prune`).
|
||||
- **Roll back.** `docker compose -f /opt/gitea-runner/compose.yaml down` on the
|
||||
host. The in-cluster runner keeps serving jobs until it is removed
|
||||
separately.
|
||||
- **Note for jobs.** `nproc` inside a job reports all of the host's CPUs, not
|
||||
the 4-CPU cap, so builds that size `-j` from it oversubscribe.
|
||||
|
||||
## Related
|
||||
|
||||
- Roadmap: label `cicd` on DevOps/software-infrastructure, milestones
|
||||
|
||||
+1
-1
Submodule roles/ericomeehan.gitea updated: 4d7b0b9e01...9f768ed621
Reference in New Issue
Block a user