Add Windows-specific configuration management details#3
Conversation
Fill in Windows coverage across the hardware platform config deck: - Slide 1: fix "managment" -> "management" in title text. - Slide 3: Windows uses image deployments locked to a ronin_puppet commit, matching the Azure worker method. - Slide 6 (how often): config locked to a commit until pool data changes; workers check on image deployment then every 2 hours, redeploying when idle or on next reboot after task completion. - Slide 7 (which config): worker reads config from the per-pool source of truth (worker-images pools.yml), each pool pinning a hash. - Slide 9: screen sharing on Windows available on request, not in the default config. - Slide 10: split self-check answer by platform; Windows self-checks config plus resolution/refresh, generic-worker, etc, rebooting then redeploying on failure. - Slide 14: fill in the Windows deploy-timing slide (was TBD), mirroring Mac/Linux with try-push verification and 0-2h redeploy. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
| - Self-checks its configuration, plus other checks: | ||
| - screen resolution / refresh rate | ||
| - generic-worker is running | ||
| - among others |
There was a problem hiding this comment.
Can we enumerate or drop the among others?
I'll change Mac/Linux to yes also... g-w checks minimum disk and won't start. g-w running check is easy - the client won't register if it's not running. Puppet convergence before every run is 'checking' the configuration.
| - e.g. `gecko_t_linux_2404_talos` -> `releng-hardware/gecko-t-linux-talos-2404` | ||
| - e.g. `gecko_t_osx_1500_m4` -> `releng-hardware/gecko-t-osx-1500-m4` | ||
| - Windows: the PXE server maps each host's MAC address to a role | ||
| - Windows: the worker reads its configuration from the per-pool source of truth file, starting at image deployment. |
There was a problem hiding this comment.
This slide is about roles and tc pools. Can we mention them?
Isn't this image based on a role?
image: "win11-24H2-NUC-01-16-2025"
I guess the exact worker pool and secrets are injected in at imaging time.
| - Windows | ||
| - Flash an image created with Puppet. | ||
| - Image deployments, locked to a specific ronin_puppet commit. | ||
| - Matches the configuration method of the Azure workers. |
There was a problem hiding this comment.
The idea behind this slide is "it's all puppet". I think the original captures what's happening from a high level. Thoughts on going into details in the later slides?
Fills in Windows coverage across the hardware platform configuration management deck. Walked the deck slide by slide and updated/corrected every Windows-relevant slide.
Changes
ronin_puppetcommit, matching the Azure worker method.worker-imagespools.yml); each pool lists its nodes and pins ahash.TBDWindows timing slide, mirroring Mac/Linux with try-push verification (~2h) and 0–2h for the worker to pick up and redeploy; notes an immediate pool-wide redeploy can be forced.🤖 Generated with Claude Code