mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-06 02:54:26 +00:00
kevinveenbirkenbachandClaude Opus 4.8
c76c6da6a8
svc-storage-nfs-server gains a backend flavor selected by services.nfs-server.flavor (default "{{ 'ganesha' if RUNTIME in ['dev','act'] else 'kernel' }}"). The ganesha flavor installs nfs-ganesha + FSAL_VFS and renders /etc/ganesha/ganesha.conf (NFSv4, Pseudo == Path so clients mount the real paths unchanged, Root_Squash on the export base and No_Root_Squash on the state subdir), reloaded via systemctl restart. It runs in the dev/act DinD swarm-test, where the host kernel nfsd is not network-namespaced and a privileged node driving exportfs would wedge it into a D-state. The kernel flavor keeps nfs-kernel-server + exportfs -ra for production and every non-dev/act runtime. 01_core dispatches on the flavor, 03_prepare holds the shared export preparation, flavor/{kernel,ganesha}/main.yml hold the per-backend install/render/service steps, and handlers gains the ganesha restart.
docs/agents/action/iteration: role.md renamed to compose.md (Compose Loop); new swarm.md for the swarm deploy loop split out of workflow.md; workflow.md trimmed to GitHub Actions workflow iteration; all cross-references updated; the duplicated README gotcha removed; the NFS gotcha rewritten to the ganesha design.
Also drops a retired-flag history comment in group_vars/all/01_modes.yml and a redundant comment in the init selection script, and allows WebFetch(repology.org) used during ganesha packaging research.
Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
1.0 KiB
1.0 KiB
Requirements
When asked to work on a requirement, you MUST follow this page.
Reading a Requirement
- You MUST read the full requirement file before writing any code or plan.
- You MUST identify the User Story and every Acceptance Criterion before acting.
- If a criterion is ambiguous, you MUST ask the user to clarify before proceeding.
Processing
- You MUST treat each unchecked criterion (
- [ ]) as a discrete unit of work. - You MUST follow Compose Loop for the edit-deploy-validate loop while implementing criteria.
- You MUST NOT mark a criterion as done (
- [x]) until its behavior is verified end to end. - You MUST check off each criterion in the requirement file as soon as it is verified. Do not batch them.
- You MUST NOT close or skip a criterion that has not been explicitly verified, even if the implementation looks complete.
Definition of Done
A requirement is complete when:
- All criteria are checked (
- [x]). - The implementing changes are committed and the PR references the requirement file.