<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Ansible on cloudplz</title><link>https://cloudplz.cc/tags/ansible/</link><description>Recent content in Ansible on cloudplz</description><generator>Hugo</generator><language>en-US</language><lastBuildDate>Thu, 10 Sep 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://cloudplz.cc/tags/ansible/index.xml" rel="self" type="application/rss+xml"/><item><title>Treating AI Agents Like Infrastructure: Provisioning Hermes Agent with Ansible</title><link>https://cloudplz.cc/writing/provisioning-ai-agents-with-ansible/</link><pubDate>Thu, 10 Sep 2026 00:00:00 +0000</pubDate><guid>https://cloudplz.cc/writing/provisioning-ai-agents-with-ansible/</guid><description>&lt;p&gt;I&amp;rsquo;ve spent 18 years making cloud infrastructure reproducible. Terraform modules for databases. Ansible roles for VM configuration. Packer templates for golden images. When I started running an AI agent on a Linux VM, I didn&amp;rsquo;t think about it — I reached for Ansible.&lt;/p&gt;&#10;&lt;p&gt;Three days and 15 commits later, I had a fully idempotent playbook that provisions &lt;a href="https://hermes-agent.nousresearch.com/"&gt;Hermes Agent&lt;/a&gt; from bare Ubuntu to production-ready. And the patterns I used? They&amp;rsquo;re the same ones I use for databases and caching clusters. That&amp;rsquo;s not a coincidence — it&amp;rsquo;s the point.&lt;/p&gt;</description></item></channel></rss>