2026-02-03, 14:50–15:40, B.1.017
LLMs can write Ansible roles and playbooks as well as plugins and modules to a relative degree of competency with commodity hardware that you can run offline, at home, with less privacy and security concerns.
They certainly understand what Ansible is, how it works and they can write YAML, Jinja or Python.
What about troubleshooting an issue with an Ansible playbook ?
You could provide it with a log file or copy & paste the results of your ansible-playbook command.
Maybe it could point you in the right direction... or hallucinate. Who knows ? ¯\(ツ)/¯
ARA Records Ansible playbook results to a database and provides an API to query the results.
What if we gave a LLM programmatic access to that API using Model Context Protocol (MCP) ?
It would allow the model to include context like host facts, playbook files and detailed task results, amongst other things.
The author experimented with it (for science) and the results are interesting.
Join us to learn about the experiment, how it works and how it might be useful in a number of ways.
David is an open source enthusiast and contributor to projects like OpenStack, Ansible, Fedora and CentOS.
iWeb, Ubisoft and RedHat alumni doing bare metal and clouds, Dev/Ops, SRE, CI/CD and everything in between at OVHcloud.
He likes simplicity and makes things work.