I would start by using AI to port the tangled mess into as much a tidy IaC as possible, with git backed declarative config tools, to prepare the safe ground where agents have context, can get loose and easily review, lint/check or test in throwaway VM before applying it.
A fleet of Openclaws (or equivalent) with control of machines for 100% hands off management seems like a russian roulette to me as of today, but a 90% handoff to AI for reviewing current config of X in our system, reading docs and configuring a deterministic tool is achievable and somewhat safe as you can easily review and trace what has been done.
frangonf
I think the most important work will be preparing the context for an agent (eg OpenClaw). Then add some skills (eg use ssh to visit specific machine). And finally the prompt. Maybe you should check what agent has the best tools for DevOps?
gitowiec
> I have dozens of Linux machines scattered throughout my property that need regular updates, migrations and general maintenance.
One idea is to move from "dozens of Linux machines scattered throughout my property" to just one.
comments (3)
A fleet of Openclaws (or equivalent) with control of machines for 100% hands off management seems like a russian roulette to me as of today, but a 90% handoff to AI for reviewing current config of X in our system, reading docs and configuring a deterministic tool is achievable and somewhat safe as you can easily review and trace what has been done.
frangonf
gitowiec
One idea is to move from "dozens of Linux machines scattered throughout my property" to just one.
andsoitis