A machine says little about itself, and only when the mesh asks it something #209

2026-09-30T08:36:42Z

jschoubben commented

2026-09-30 08:36:42 +00:00

Filed as a to-do — open is this repository's status for "written down, nobody has started"; there is no todo. Nothing is broken by it: every machine here is amd64 and reports so, and one architecture is enough for now.

More is already collected than it looks, including the architecture and kernel — and nothing reads either. Measured: all four machines report amd64 / linux, and node show prints the capabilities beside them without printing them.

Missing: memory, disk, the processor beyond its architecture, the distribution and version, virtual or physical, cores, uptime. Several are exactly what the placement code's own comment already imagines wanting.

Also missing: the refresh. A machine publishes after an apply and the five-minute reconcile publishes nothing, so the mesh's picture is as old as the last push — the same mechanism issue 087 wanted.

This is the third thing found in one day to be collected and read nowhere, after held resources and the host version. Whatever gets added should say in the same breath which surface shows it, or it will be the fourth.

Issue 159 gains the note that the architecture is already reported, so matching an artifact to a machine needs no new fact from the machine — only the comparison, and a compiler told what to target.

Filed as a to-do — `open` is this repository's status for "written down, nobody has started"; there is no `todo`. Nothing is broken by it: every machine here is amd64 and reports so, and one architecture is enough for now. **More is already collected than it looks**, including the architecture and kernel — and nothing reads either. Measured: all four machines report `amd64` / `linux`, and `node show` prints the capabilities beside them without printing them. Missing: memory, disk, the processor beyond its architecture, the distribution and version, virtual or physical, cores, uptime. Several are exactly what the placement code's own comment already imagines wanting. Also missing: **the refresh.** A machine publishes after an apply and the five-minute reconcile publishes nothing, so the mesh's picture is as old as the last push — the same mechanism issue 087 wanted. This is the **third** thing found in one day to be collected and read nowhere, after held resources and the host version. Whatever gets added should say in the same breath which surface shows it, or it will be the fourth. Issue 159 gains the note that the architecture is already reported, so matching an artifact to a machine needs no new fact from the machine — only the comparison, and a compiler told what to target.

jschoubben added 1 commit 2026-09-30 08:36:42 +00:00

A machine says little about itself, and only when the mesh asks it something a2542e51f8

Filed as a to-do. Nothing is broken by it: every machine here is amd64 and
reports so, and one architecture is enough for now.

When a machine joins, the mesh should collect what it reasonably can about
it and refresh that daily. It already asks what a machine can do; what it
is made of is the same question one level down.

More is already collected than it looks — eight capabilities, the links
that face outside, the host version, and on an adopted machine what it
holds, what is reachable and the firewall and tunnel it was found with.
The architecture and the kernel are in there too, and nothing reads
either: measured, all four machines report amd64 and linux, and node show
prints the capabilities beside them without printing them.

Missing: memory, disk, the processor beyond its architecture, the
distribution and its version, virtual or physical, cores, uptime. Several
are what somebody wants when deciding where a module goes, and the
placement code's own comment already imagines them.

Also missing: the refresh. A machine publishes after an apply, and the
five-minute reconcile publishes nothing, so the mesh's picture is as old
as the last push. Same mechanism 087 wanted.

This is the third thing in one day found to be collected and read nowhere,
after held resources and the host version. Whatever gets added should say
in the same breath which surface shows it, or it will be the fourth.

159 gains the note that the architecture is already reported, so matching
an artifact to a machine needs no new fact — only the comparison and a
compiler told what to target.

jschoubben merged commit 4f9dc3906e into main

2026-09-30 08:36:48 +00:00

jschoubben deleted branch issue/160-what-a-machine-says-about-itself

2026-09-30 08:36:48 +00:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: novox/hq#209