docs: xu3-1 is not a build agent - record what it actually is - #601
Merged
Merged
Conversation
Measured on the box: up 87 days, zero users, no CI runner installed, and /home/swares contains only the Python 3.11 source tree compiled so Ansible could reach it. Its sole workload is being manageable. Everything else running is stock image - lightdm, cups, ModemManager, whoopsie - plus a containerd with no k3s membership. Every doc calls it a build agent and none says what it builds. HOSTMON-BUILD.md describes making it a runner as an unimplemented proposal. LAB-DESIGN.md had '(flaky - verify)' on the claim all along; one command settled it. The cost is special cases, not power: eight playbooks carry an exception for it, and two of this week's changes tripped over them - chrony skipped it, and the SSH hardening needed an entire second code path because its sshd predates Include. Frames the choice as retire or rebuild rather than keep, since the exceptions exist because of the 2016 OS. Records the one real argument for rebuilding, which the repo had never made: xu3-1 is wired gigabit while three of four DNS resolvers are on WiFi, and 'DNS needs a permanent host' has been open for months. Decision deliberately deferred.
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
1 participant
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.
Measured on the box: up 87 days, zero users, no CI runner installed, and /home/swares contains only the Python 3.11 source tree compiled so Ansible could reach it. Its sole workload is being manageable. Everything else running is stock image - lightdm, cups, ModemManager, whoopsie - plus a containerd with no k3s membership.
Every doc calls it a build agent and none says what it builds. HOSTMON-BUILD.md describes making it a runner as an unimplemented proposal. LAB-DESIGN.md had '(flaky - verify)' on the claim all along; one command settled it.
The cost is special cases, not power: eight playbooks carry an exception for it, and two of this week's changes tripped over them - chrony skipped it, and the SSH hardening needed an entire second code path because its sshd predates Include.
Frames the choice as retire or rebuild rather than keep, since the exceptions exist because of the 2016 OS. Records the one real argument for rebuilding, which the repo had never made: xu3-1 is wired gigabit while three of four DNS resolvers are on WiFi, and 'DNS needs a permanent host' has been open for months. Decision deliberately deferred.