Rulings of 2026-11-14 09:55 recorded: D80 (root CA copy), D81 (+ the stopgap), the N100's time service, the build order (09 §3 decisions 303-306)
gates / gates (push) Successful in 2m2s

This commit is contained in:
admin committed 2026-11-14 10:00:53 +01:00
1 parent ef8e23f42a
commit 561a4d98e9
3 files changed
+25 -7

No files matched your search

+1 -3
View File
@@ -32,8 +32,6 @@ Newest first. CC's pick is in the „Pick" column. Each row also has its full te
| # | Row | Question | Pick (why) | The other option costs | If you do nothing | Blocked |
|---|---|---|---|---|---|---|
| D81 | R-1392 | When an agent release changes no root file, should the hub stop calling the boxes' root files „behind"? | **Yes — the hub compares the files, not the bundle's label** (fixes every future release once; one hub change and deploy) | keep the hub: every release also sends a root-file job to each box (about 15 minutes per release, forever) | on 11-17 three alarm mails; the same after every agent release | — |
| D80 | R-1380 | How shall the agent trust Proxmox after its certificate changes: a copy of the box's own root CA, or a helper that follows the new fingerprint (your ruling of 11-11 13:17)? | **The root CA copy** (proven on demo-hp: the agent went through a new certificate with no hand step; no new privileged code) | follow the fingerprint: a root helper, a sudo rule and re-pin logic to write and test; trust stays on one exact certificate | nothing is built; the first box goes blind about 2028-07-02 | the fix of R-1380 |
| D66 | R-1365 | Should a security-watch source that stays down mail again every 7 days, as an open notice does? Today it mails once, then only the Monday summary lists it. | **Yes** (a real outage then cannot be forgotten; the seven pins that can never be read no longer count, so it stays quiet when all is well) | no: one line in a long Monday mail stays the only reminder | a source that stays down mails once; the Monday list still shows it | — |
| D38 | R-1235 | Put the newest golden (637 MB) into the nightly release copy on ep0 too? | **Yes** (a new install after a DooPlex loss needs it; it fits under the 3 GB cap) | leave it out: after a loss, no new install until a golden is rebuilt and vouched | the same | — |
| D37 | R-1236 | Raise Gitea's memory limit from 1 GiB to 2 GiB? It was killed for memory 4 times in 17 days, once during today's release. | **Yes** (DooPlex has the RAM; a DooPlex change, so yours) | keep 1 GiB: a restart in release hours fails box updates and CI for a minute | the same | — |
@@ -41,7 +39,7 @@ Newest first. CC's pick is in the „Pick" column. Each row also has its full te
| D7 | R-990, R-989 | Rule on the forum ideas and the selfh.st ideas now, or park them? | **Park them** (P4; nothing waits on them) | Rule now: about one hour of reading | nothing changes; the research gets old | — |
## Waiting on you — do
**2026-11-14.** Before 11-17: say „send the bundle" to clear the yellow (D81). If not: 3 alarm mails. **2026-11-11.** 1. N100, as root, one time: `apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.chronyd && systemctl restart chrony && chronyc tracking` (R-1301; not tested). If not: about mid-January 2027 it refuses every agent update. 2. Hub Hosts page: Discard appliance `3fb5fed3…` (11-11 test box). 3. Rotate login `kisfenyo`'s Gitea token into the store as `GITEA_GIT_TOKEN` (R-925); the push after `sec put` is in R-1390. 4. Home DNS: remove the `felhom.eu` override (R-1389). 5. Read the dates only you can read (R-1381). 6. Search Console read (R-1035, 11-18).
**2026-11-14.** Build order: four releases (dates, host, „hub tells you”, promises); no new gap-review list first. **2026-11-11.** 1. N100's time service: no hand step now; release 2 repairs it. If it is not live by 2026-12-15: `apparmor_parser -r -T -W /etc/apparmor.d/usr.sbin.chronyd && systemctl restart chrony` (R-1301). 2. Hub Hosts page: Discard appliance `3fb5fed3…` (11-11 test box). 3. Rotate login `kisfenyo`'s Gitea token into the store as `GITEA_GIT_TOKEN` (R-925); the push after `sec put` is in R-1390. 4. Home DNS: remove the `felhom.eu` override (R-1389). 5. Read the dates only you can read (R-1381). 6. Search Console read (R-1035, 11-18).
**Still needed? (yes/no)** — answer per line.
1. Look at `roms/roms/` on the N100's drive in the file manager (R-1099). (since 10-16)