1785176717voxconf2026Europe/Berlinlecturevoxconf2026-110722-opening-openvoxpuppet2026-07-16T08:45:00+02:0008:4500:10VortragssaalvoxconfenPuppet Inventor Luke Kanies recalls the reasoning behind Puppet (now OpenVox), its early history, and goals.Prototype in Summer 2004 to proof intellectual property Full time Puppet 2005 Sysadmins building tools for sysadmins, transform the role of a sysadmin Fired from Puppet in 2016https://video-dl.homelab.ayanami.us/174aedfc-8209-11f1-a4ef-566f547c0006/LukeKanies.mp4falseLuke Kanieslecturevoxconf2026-110737-history-of-openvoxpup2026-07-16T08:50:00+02:0008:5000:10VortragssaalvoxconfenLuke is the original author of the 2006 OpenVox, then called Puppet. Luke recalls how he felt the need to develop OpenVox and the tradeoffs he acceptedfalseLuke Kanieslecturevoxconf2026-110723-migrating-to-openvox2026-07-16T08:55:00+02:0008:5500:25VortragssaalvoxconfenPuppet has been in use at INFN Naples for several years, together with Foreman for lifecycle management. It is currently used to manage several hundred machines, both bare metal and virtual, across a heterogeneous infrastructure that includes Ceph and dCache storage systems, HTCondor clusters, an OpenStack private cloud, and a number of self-hosted services such as Greenbone and NetBoxA change in Perforce licensing policy forced us to look for an alternative solution, leading to the migration to OpenVox and to an active involvement with its community. The migration process can be divided into several sub-tasks: Migration of an all-in-one Puppet Server (OSP Server, PuppetDB, and Puppetboard) and the managed clients Migration of the Foreman server and its managed clients Migration of the supporting toolchain (Bolt, IDE integrations, and related tools) Each of these areas presented distinct challenges and required different migration strategies, some of which are still ongoing. Contributions and roadmap The migration effort led us to contribute to upstream projects, most notably the puppet-openvoxdb module (now released) and a set of Foreman templates to provision clients with the OpenVox repository enabled (work in progress at the time of writing). Despite the strong community support and our efforts, some components of the infrastructure have not yet been migrated, most notably the Git-based workflow, which still relies on r10k.https://import.c3voc.de/videos/aca0b8e8-9b64-466d-88b4-0d145ed618d2.mp4falseFrancesco Di Nuccilecturevoxconf2026-110724-migrating-to-openvox2026-07-16T09:20:00+02:0009:2000:25VortragssaalvoxconfenAt CERN we are currently switching our whole infrastructure to Openvox all over the place and would like to contribute by giving a talk during the VoxConf 2026. This switch, although simple for some other organisations (not a simple repo and package switch for us), showed some non-negligible technical debt and challenges. We would like to present our journey, past, present and future on our Puppet to Openvox transitionFor many organizations, the migration from Puppet to OpenVox might be a matter of swapping repositories and running a package update. For CERN (home to the Large Hadron Collider and tens of thousands of heterogeneous nodes spanning data centers, accelerator controls, and physics analysis grids) it has been an archaeological dig through a decade and a half of institutional configuration history. This is a post-mortem (and mid-mortem) of a massive enterprise pivot for a system that supports +15000 machines and +400 administrators. In our pursuit of a fully OpenVox-driven infrastructure, we discovered that the technical debt was not in the software itself, but in the abstractions we had built on top of the software. This is a description of the challenges we surpassed and will have coming later on this year (and beyond) to align with CERN's long-term opensource strategy.https://import.c3voc.de/videos/6064049c-f98a-4636-a78d-73a62883928b.mp4falseDaniel Juárezlecturevoxconf2026-110725-whats-new-in-openvox2026-07-16T09:45:00+02:0009:4500:25VortragssaalvoxconfenThis session will cover the most important changes in OpenVox 9, including dependency updates, removal of previously deprecated features, new deprecations to be aware of, and notable new features or platform changes. It will provide a practical overview of the release and what users and module authors should review before upgrading.https://import.c3voc.de/videos/908f2555-50c9-4aa0-8e7c-d4aa2f34f4c3.mp4falseSteven Pritchardlecturevoxconf2026-110726-automated-observabili2026-07-16T10:20:00+02:0010:2000:25VortragssaalvoxconfenBuilding comprehensive infrastructure observability traditionally requires manual configuration of monitoring targets, brittle configuration management and endless YAML files. Every new server means updating Prometheus configs, managing certificates and hoping nothing breaks. What if your infrastructure could monitor itself automatically from the moment a server boots?This talk demonstrates a production-ready architecture that combines modern Puppet patterns with automated service discovery to create truly self-configuring observability. Using Puppet's exported resources, nodes automatically register themselves for monitoring without any manual intervention. New web servers are discovered and scraped within minutes of provisioning—no configuration updates required. You'll learn how to implement: * Modern Puppet classification using CSR attributes instead of site.pp node definitions. Nodes self-classify by embedding their role directly in their TLS certificate, eliminating centralized configuration bottlenecks. * Hiera-based roles defined as pure YAML data instead of Puppet manifests, making roles accessible to non-Puppet experts and enabling templated role generation. * Automated service discovery through Puppet's exported resources. Each node exports its monitoring endpoints to PuppetDB, which a lightweight Python script queries to generate Prometheus file-based service discovery targets. Zero manual configuration required. * Zero-trust security using Caddy as an mTLS reverse proxy. All metrics traffic is secured with mutual TLS using Puppet's existing CA infrastructure—no additional certificate management needed. * Universal observability with node_exporter on every server and application-specific exporters (apache_exporter, etc.) automatically configured based on the node's role. The architecture scales from a handful of servers to thousands, works seamlessly with cloud auto-scaling and provides complete visibility into both system and application metrics. Attendees will observe a demo with working code, container configurations and a deep understanding of how to build self-managing infrastructure that doesn't require operator intervention to stay observable. https://corporate-gadfly.github.io/zero-trust-observability/#/title-slidehttps://video-dl.homelab.ayanami.us/174aedfc-8209-11f1-a4ef-566f547c0006/AutomatedObservability.mp4falseHaroon Rafiquelecturevoxconf2026-110727-openvox-operator-pupp2026-07-16T10:45:00+02:0010:4500:25VortragssaalvoxconfenSetting up a production-ready OpenVox stack is complex: node classification, auto signing, load balancing, code deployment, OpenVox DB - everything has to be set up and wired up by hand. The OpenVox Operator takes care of that and describes the entire infrastructure declaratively as Kubernetes Custom Resources. After a short introduction to what a Kubernetes Operator is, the talk walks through the design and a live demo showing how quickly a fully working, scalable OpenVox server comes up.https://github.com/slauger/talk-voxconf-2026https://video-dl.homelab.ayanami.us/174aedfc-8209-11f1-a4ef-566f547c0006/KubernetesOpenVox.mp4falseSimon Laugerlecturevoxconf2026-110728-what-is-documentation2026-07-16T11:35:00+02:0011:3500:25VortragssaalvoxconfenIn this workshop, we will discuss how Vox Pupuli approaches documentation as well as how OpenVox documentation is (re-)created. The goal is to contribute to Vox Pupuli and OpenVox documentation strategy while addressing my research interest in non-knowledge. In this 50 minutes exchange with the audience, I will guide the conversation with a series a questions that give space for different opinions as well as feedback about my research.The workshop will cover a number of key considerations, including the narrative or story behind both, Vox Pupuli and OpenVox; the type(s) of documentation that is/are needed, wanted and expected, as well as its/their maintainability; and finally, the (best) practices that contribute to good documentation. In the process, I will share the preliminary results of my analysis of Slack exchanges, PRs and comments on the GitHub documentation repository, and interviews with the Vox Pupuli members most involved in the process of creating OpenVox documentation. I expect to conclude this exercise with actionable items for the community and more data for my dissertation.https://video-dl.homelab.ayanami.us/174aedfc-8209-11f1-a4ef-566f547c0006/Documentation.mp4falseSol Martinez Demarcolecturevoxconf2026-110729-realize-the-potential2026-07-16T12:00:00+02:0012:0000:25VortragssaalvoxconfenPuppet has been the hidden glue of system automation for decades but it never came turnkey. Every sysadmin built their own setup: roles, profiles, PuppetDB, eyaml, hiera, octocatalog-diff reinventing the same wheel, privately, forever. LinuxAid changes that. Built on OpenVox, it packages those decades of hard-won operational decisions the common module, monitoring module, typed DSL, change-preview with octocatalog-diff into a single collaborative platform anyone can fork, use, and improve. When you build your platform as open source instead of just on open source, the work you do for one customer compounds for everyone.https://video-dl.homelab.ayanami.us/174aedfc-8209-11f1-a4ef-566f547c0006/ForemanPuppetAndContainers.mp4falseKlavs Klavsenlecturevoxconf2026-110730-welcome-and-introduct2026-07-16T13:15:00+02:0013:1500:05VortragssaalforemanenfalseBernhard Suttnerlecturevoxconf2026-110731-foreman-puppet-and-co2026-07-16T13:20:00+02:0013:2000:50Vortragssaalenhttps://video-dl.homelab.ayanami.us/174aedfc-8209-11f1-a4ef-566f547c0006/ForemanPuppetAndContainers.mp4falseAdam Růžičkalecturevoxconf2026-110732-centralized-ansible-a2026-07-16T14:10:00+02:0014:1000:25Vortragssaalforemanenhttp://poller.in-ulm.de/voxconf/Centralized%20Ansible%20Automation%20with%20Foreman%20Ansible%20Director.mp4falseThorben Denzerlecturevoxconf2026-110733-foreman-in-the-age-of2026-07-16T14:35:00+02:0014:3500:25Vortragssaalforemanenhttp://poller.in-ulm.de/voxconf/Foreman%20in%20the%20age%20of%20digital%20sovereignty,%20NIS2%20and%20AI.mp4falseDirk Götzlecturevoxconf2026-110734-foreman-openbolt-a-32026-07-16T15:15:00+02:0015:1500:40VortragssaalforemanenEnd of 2024, we started a journey of <a href="https://community.theforeman.org/t/rfc-integrating-bolt-into-remote-execution/39901">integrating OpenBolt into Foreman</a>. This turned into a series of conference talks: <ul> <li>At the Foreman Birthday Party 2025 I gave a presentation about migrating from <a href="https://bastelfreak.de/foreman2025/index.html#1">Puppet Enterprise to Foreman + OpenVox<a>.</li> <li>At the Config Management Camp 2026 I spoke about <a href="https://bastelfreak.de/cfgmgmtcamp2026/openbolt.html#1">integrating OpenBolt tasks into Foreman</a>.</li> <li>This talk is part three of the series - integrating <a href="https://choria.io/">Choria</a> as a transport protocol for scaleable remote execution and orchestration with the <a href="https://github.com/overlookinfra/foreman_openbolt">OpenBolt Plugin</a>.</li>We will go into the details on: <ul> <li>What actually is Choria?</li> <li>How do I configure this?</li> <li>Why do I want to use this awesome OpenBolt integration for all of my daily sysops tasks and platform orchestration?</li> <li>Why is this the perfect combination to Foreman and OpenVox and the missing piece for orchestration (why is it cooler than Ansible or the existing remote execution in Foreman)?</li> </ul>https://video-dl.homelab.ayanami.us/174aedfc-8209-11f1-a4ef-566f547c0006/ForemanOpenBolt.mp4falseTim Meusellecturevoxconf2026-110735-opentofu-based-comput2026-07-16T15:55:00+02:0015:5500:25Vortragssaalenhttps://video-dl.homelab.ayanami.us/174aedfc-8209-11f1-a4ef-566f547c0006/opentofu.mp4falseManisha Singhallecturevoxconf2026-110736-bootc-provisioning2026-07-16T16:20:00+02:0016:2000:20Vortragssaalenhttp://poller.in-ulm.de/voxconf/bootc.mp4falseJonas Trüstedt