14 Commits

Include renames

Author	SHA1	Message	Date
jschoubben	1cdb4d1a29	Say a module found running on its own have again at the agent's start, so its health is this engine's and not an older engine's unknown ... xorg's have on g14 and shanks kept the unknown an engine before 958ccbd wrote: the baseline believed the have and never handed the module to the session, so no look rewrote its health, and the assigner held every module requiring x11-display back.	2026-10-25 15:27:23 +01:00
jschoubben	16f84b53da	Leave the node's own copy of a module's resource out, and carry the kept declaration's filled paths (issue 1945) ... The node's own composition and a module's both declared the same files, and the joined declaration was refused whole ("2 resources declare X"): the node's own copy is now left out when joining and at the node's own apply, and said once (1945/AC17). A module still running from the kept declaration now carries its filled paths, so the filling no longer refuses them as not named as filled (1945/AC18).	2026-10-25 14:10:52 +01:00
jschoubben	8343c4fb36	Apply the revision of a composition key whose digest the want names, from the revisions the bucket keeps (issue 1945)	2026-10-25 12:42:20 +01:00
jschoubben	c46937da04	Apply a module again when the engine holds no record of its resources or its health says one is missing, and move a module with nothing to back up without a backup (issue 1944, issue 1945)	2026-10-25 10:59:21 +01:00
jschoubben	ecf142e451	Let only a module's wanted or newest composition hold the node's own apply back, never a stale refused one (issue 1945)	2026-10-25 02:01:24 +01:00
jschoubben	fa9e4483c8	Hold back the node's own apply while a module's composition cannot be read or is refused, naming it (issue 1944, issue 1945)	2026-10-25 02:56:20 +02:00
jschoubben	e62c32c8c3	Leave a record another module's composition now holds, whatever its type, instead of removing it in the node's own apply; a removed module holds nothing back (issue 1944, issue 1945)	2026-10-25 02:54:58 +02:00
jschoubben	2bfde7d659	Hold out a module whose own composition waits to be applied, so the node's own apply never removes the resources it moved there (issue 1944, issue 1945)	2026-10-25 02:52:10 +02:00
jschoubben	4e6b756bd2	Refuse an apply that would write a provisioner's file empty, read the node's own filled paths, and name the node's own composition when its apply fails (issue 1944, issue 1945)	2026-10-25 01:49:00 +02:00
jschoubben	be5f31ce66	What runs is the agent's compositions plus the kept declaration's rest: health, filling, take act, directories and the others held out of an apply read it; a restart trusts the node-engine's own haves; the bed tests run off Arch (review round 1)	2026-10-24 18:13:40 +02:00
jschoubben	96d0322498	The node-engine reports reads-wants; a failed apply is said; the have's fingerprint and digest follow its health (R6-A A6)	2026-10-24 16:43:26 +02:00
jschoubben	b2003e7a38	A composition is applied only when the controller or the operator signed it; the node agent's integration tests on an embedded bus (R6-A A9, A1, A5)	2026-10-24 16:42:11 +02:00
jschoubben	3303797bfb	The node agent runs in the node-engine: watches the wants and compositions on the link, applies one module's composition, asks the backup, writes the haves (R6-A A1, A5, A6)	2026-10-24 16:39:51 +02:00
jschoubben	d5dd7761c6	The node agent: follows the wants and the node's compositions, applies one module at a time, backs a data module up first, holds it on a failed backup (R6-A A1, A2, A5, A6)	2026-10-24 16:36:21 +02:00