<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Meetups &amp; Conferences on dominic.dev</title>
    <link>https://www.dominic.dev/talks/</link>
    <description>Recent content in Meetups &amp; Conferences on dominic.dev</description>
    <generator>Hugo -- 0.154.5</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 11 Mar 2026 16:58:04 +0200</lastBuildDate>
    <atom:link href="https://www.dominic.dev/talks/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Integrating Ansible &amp; Terraform</title>
      <link>https://www.dominic.dev/talks/2023-09-12-integrate-ansible-terraform/</link>
      <pubDate>Tue, 12 Sep 2023 18:00:00 +0200</pubDate>
      <guid>https://www.dominic.dev/talks/2023-09-12-integrate-ansible-terraform/</guid>
      <description>&lt;p&gt;At the 14th Ansible Meetup in Zurich, I gave a talk on integrating Ansible and Terraform. The session focused on the challenges of provisioning infrastructure, the strengths of each tool, and how to effectively make them work together.&lt;/p&gt;
&lt;h2 id=&#34;the-core-challenge&#34;&gt;The Core Challenge&lt;/h2&gt;
&lt;p&gt;While Ansible is a powerful configuration managment solution, using it for pure cloud infrastructure provisioning comes with hurdles. It lacks resource dependencies, doesn&amp;rsquo;t maintain an infrastructure state, and its declarative nature means running a &amp;ldquo;check mode&amp;rdquo; on infrastructure that doesn&amp;rsquo;t exist yet will simply fail. (There is an upcoming talk about a &lt;code&gt;terraform plan&lt;/code&gt; implementation for Ansible - stay tuned)&lt;/p&gt;</description>
    </item>
    <item>
      <title>WIP: Ansible and Netbox</title>
      <link>https://www.dominic.dev/talks/2021-09-28-wip-ansible-netbox/</link>
      <pubDate>Tue, 28 Sep 2021 18:00:00 +0200</pubDate>
      <guid>https://www.dominic.dev/talks/2021-09-28-wip-ansible-netbox/</guid>
      <description>&lt;p&gt;Tracking IPs, networks, servers, and virtual machines manually in Excel and Confluence creates an airgap that prevents seamless automation. I shared our journey to bridge this gap during my talk at the 10th Ansible Meetup in Zurich. As we pushed for wider adoption of configuration management, we realized we needed a robust source of truth inventory, leading us to migrate to Netbox for IPAM and device management. Here is a breakdown of how Netbox and Ansible integrate, how context data is structured, and why we sometimes have to bypass modules to interact directly with the API.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Automated Infrastructure Testing with Molecule</title>
      <link>https://www.dominic.dev/talks/2021-09-14-automated-infrastructure-testing/</link>
      <pubDate>Tue, 14 Sep 2021 18:00:00 +0200</pubDate>
      <guid>https://www.dominic.dev/talks/2021-09-14-automated-infrastructure-testing/</guid>
      <description>&lt;p&gt;Interaction between hardened loadbalancers, reverse proxies and web applications are difficult to test in early stages and therefore often only detected late in pre-prod / integration environments under high load and/or edge cases. Molecule allows complex test scenarios with mixed environments (Container, VM, Cloud) in a fully automated way.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
