mirror of
https://github.com/kevinveenbirkenbach/computer-playbook.git
synced 2026-11-08 03:38:23 +00:00
evangelostsak
152588b511
The pass that runs over the mesh reaches every host by SSH where the pass before it used the container connection, and it pays that difference once per task. Measured in a container: an exec through a warm multiplexer costs 7ms, a fresh connection 85ms, and 165ms once sudo asks for the password every task demands. The pass runs thousands of tasks. Two settings threw the multiplexer away. A persist window of 20s closes the master whenever a host waits longer than that for its next task, which in a linear play is most of them; and the named ControlPath points at a directory nothing creates, so a master that cannot open its socket reconnects per task without reporting it. Neither is retuned for the repository. The tool that moves a host onto the mesh now writes that host's own ssh_args, derived from the repository's value so every other option is kept and only the window and the socket differ. A host the mesh never touches keeps exactly what it had. Confirmed against the built command: a switched host gets ControlPersist=600s and a ControlPath under the directory Ansible creates, while a host beside it keeps the repository's own.