Address nodes by their own name, not the shared one - #35
Merged
Merged
Conversation
Every service URL here pointed at owl.local. That name is answered by every node on the network at once, so on a site with more than one it reaches whichever replies first, which is not what someone reading a table of a specific node's services is asking for. The managed-node table now uses ret<node_id>.local, the address derived from the Mender node_id that never changes for the life of the board, with owl.local described for what it is: a way to find a node rather than a way to reach one. The SSH section matters most. owl.local resolving to different hosts between connections trips REMOTE HOST IDENTIFICATION HAS CHANGED, so that instruction was actively going to bite someone. STANDALONE is a different case and had the same URLs wrongly. It covers running the stack on any Linux host, where neither owl.local nor ret<node_id>.local exists, so it now points at the host's own address and mentions the mDNS names only as something owl-os adds. Co-Authored-By: Claude Opus 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
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.
Why
Every service URL in these docs pointed at
owl.local. That name is answered by every node on the network at once, so on a site with more than one it reaches whichever replies first, which is not what someone reading a table of a specific node's services is asking for.What changed
README now uses
ret<node_id>.localfor all five service URLs, the address derived from the Mender node_id that never changes for the life of the board.owl.localis described for what it is: a way to find a node rather than a way to reach one.The SSH section matters most. It said
ssh node@owl.local. That name resolving to different hosts between connections tripsREMOTE HOST IDENTIFICATION HAS CHANGED, so the instruction was going to bite someone.STANDALONE.md had the same URLs but needed a different fix. Its intro says the stack runs on owl-os or any Linux system, where neither
owl.localnorret<node_id>.localexists, so pointing it atret<node_id>.localwould have been wrong in a new way. It now uses the host's own address and mentions the mDNS names only as something owl-os adds.Scope
Documentation only, two files, no code. Independent of the mDNS work in offworldlabs/owl-os#53 and offworldlabs/retina-gui#75, and can merge on its own schedule, though the names it documents only exist once owl-os#53 ships.