jochen
8bcf787258
A VPN client rewrote the laptop's resolver file and nothing said so. The engine now states its machine's networking; the controller keeps it with the machine's health (migration 0077) and raises the rewrite as its own finding naming the writer, the machine's own faults as machine.<m>.network, and what several machines cannot reach once, there. The gate waits on a rewrite it did not make rather than putting back a good build.
11 lines
813 B
SQL
11 lines
813 B
SQL
-- A machine says how its network is (novox/hq ADR 0241, which extends ADR 0240 from what a module runs to
|
|
-- the machine it runs on).
|
|
--
|
|
-- Beside the state of every long-running resource, each machine's node-engine states its own networking:
|
|
-- the resolver file the uplink holder declared and who rewrote it, the names through every resolver it
|
|
-- lists, the tunnel's handshake with the hub, the bus and the default route — the worst of them, since
|
|
-- when, and each part. Kept with the machine's newest statement, replaced with it, so `node show`, the
|
|
-- gate and a controller started again read the same word. Null for a machine whose node-engine is older
|
|
-- than this judging: its network is not known — never healthy, never a reason to raise anything.
|
|
alter table node_health add column network jsonb;
|