Repository navigation
docs: the ISO store is built, and Saruman mounts it (#446) - #793
Merged
Merged
Conversation
build-the-nas.md §5b, done on 2026-10-01: - smaug: erebor/iso at recordsize 1M, owned by pippin (3003:3002), shared over NFSv4 to 10.0.30.110 alone with root mapped to pippin. - morpheus: `Allow NFS from Saruman to smaug` printed directly above igc0.30's Block access to CasaBonita in pfctl -sr -vv. - Saruman: the fstab mount shows the 500G quota, and smaug-iso is an active dir storage. A web-UI upload of virtio-win-0.1.302.iso landed owned by pippin, not root. - alexander and the monitoring host are refused on 2049. The igc0.40 tripwire reads 0 packets after 260,980 evaluations. The rule moves from specified to created in build-the-nas.md §0.5, network.md, security.md and stacks/media/README.md. network.md's ImaginationLAN notes now name the block, as build-the-backup-guest.md §4 asked. The roadmap entry folds into #440's: build from smaug-iso, and verify each ISO's checksum first. Also recorded: the step's apt install finished a half-configured alloy upgrade on Saruman, and /etc/default/alloy was kept. Closes #446. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
There was a problem hiding this comment.
Copilot review overview
🟡 Changes recommended
The changelog contains unresolved conflict markers, and two rule summaries remain inconsistent with the newly active NFS path.
Review effort: Balanced
Findings: 1
Open (3)
What changed in this PR
Records completion of the smaug ISO store and its use by Saruman.
Changes:
- Marks the NFS share, firewall rule, and Proxmox mount as created.
- Documents verification results and updates the automation roadmap.
- Adds the deployment to the changelog.
| File | Description |
|---|---|
stacks/media/README.md |
Marks the NFS access as active. |
docs/security.md |
Records the live rule and residual risk. |
docs/runbooks/build-the-nas.md |
Records §5b completion evidence. |
docs/roadmap.md |
Moves ISO consumption into #440. |
docs/network.md |
Documents rule placement and reachability. |
docs/changelog.md |
Adds the completed ISO-store entry. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
…#446) The previous commit carried stash conflict markers in changelog.md. A merge of main auto-stashed the edits, and the re-apply conflicted where #455's entry landed on the same date. Both entries are kept and the markers are gone, which is what failed Lint. Review on the PR: - network.md said "Six exist today" for the Hicks and Winterfell passes, but they were already seven: four, then 4533, 445 and 13378. It now says seven, and the NFS pass makes eight. - stacks/media/README.md names Saruman as a fifth consumer. It also says the 2049 export differs from the three media ports: CasaBonita can open the port, but the export answers 10.0.30.110 alone. Refs #446 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…-iso (#446) #792 merged while this branch was open. Its Packer defaults put the ISOs on local storage (iso_storage = local, local:iso/... file names), and no step verifies a checksum. The roadmap sentence said #440 builds from smaug-iso, which is not true yet. It now says what moving the builds there takes, and that the checksum step still has to come first. Refs #446 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Records
build-the-nas.md§5b as done on 2026-10-01. The pass moves from specified to created in the four documents in one commit, as §5b step 8 asks.What was proven
smaugerebor/iso, recordsize1M, 500 GiB quota.pippinis3003:3002. The share admits10.0.30.110alone, with maprootpippin.morpheusAllow NFS from Saruman to smaug(10.0.30.110 → 10.0.40.30:2049) prints directly aboveigc0.30's Block access to CasaBonita.Sarumanfstabmount shows500G, the quota.smaug-isois an activedirstorage.virtio-win-0.1.302.isouploaded through the UI and landed owned by3003:3002, not root.alexander,prometheus2049.igc0.40reads 0 packets after 260,980 evaluations.Also in this PR
network.md's ImaginationLAN notes now name Block access to CasaBonita as the block that passes tosmaugsit above, whichbuild-the-backup-guest.md§4 asked for.golem's pass goes there too.local. The entry says so, and says that moving the builds tosmaug-isoneeds a checksum step first.network.md's pass count was already stale at six. It now says seven from Hicks and Winterfell, and eight with this one.stacks/media/README.mdnamesSarumanas a fifth consumer. It also notes that the2049export, unlike the media ports, answers10.0.30.110alone even on CasaBonita.alloydpkg prompt onSarumanand why the answer is N.An earlier push carried stash conflict markers in
changelog.md, which failed Lint. They are removed, and both of that day's entries are kept.check_docs.pyand markdownlint pass.Closes #446.
🤖 Generated with Claude Code