# Ansible Roles Ansible roles organize related automation content in a defined file structure so it can be reused and shared. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Autobase 2.11 released DevFeed: [Autobase 2.11 released]() Original publisher: [Read original article]() Published: 2026-09-09T00:00:00Z Content type: release Language: en Sources: [PostgreSQL news]() Topics: [postgresql clusters](), [Database](), [releases](), [Ansible Roles](), [cloud-infrastructure]() Tags: [ansible](), [cloud](), [operations](), [postgresql](), [postgresql-clusters](), [release]() ### AI overview Autobase 2.11 adds Platform UI management for PostgreSQL cluster scaling, minor and major upgrades, backups, and point-in-time recovery. It also introduces Ansible playbooks for backup and recovery operations. ### Source excerpt Autobase 2.11 is an important milestone in the evolution of the platform. Two years ago, we started working on a broader goal: evolve the Autobase Console from a PostgreSQL deployment UI into a platform for managing the complete cluster lifecycle. With this release, the remaining major pieces of that roadmap are now in place - scaling, upgrades, backups, and point-in-time recovery can all be managed directly from the Platform UI. See the full details in the release notes. Highlights Scaling (read replicas) Scale PostgreSQL read capacity directly from the UI. Simply specify the desired number of cluster nodes, and Autobase will provision the additional replicas automatically using the existing cloud configuration. For cloud deployments, the required servers and related infrastructure resources are created automatically. You can also scale clusters running on your own bare-metal or virtual machines. Start with a single-node PostgreSQL cluster and add replicas later as your workload grows. Upgrades Autobase Platform now supports minor upgrades within the current PostgreSQL major version as well as major-version upgrade workflows. For minor upgrades, replicas are updated one at a time, followed by a switchover and upgrade of the former primary. Read traffic remains available throughout the process, while expected write downtime is only ~5-10 seconds. For in-place major upgrades, the expected downtime is typically ~30-60 seconds. A blue-green major upgrade workflow with near-zero downtime is planned for a future release. Backup & Restore (PITR) Backup and recovery management is now available directly in the Platform UI. Configure the backup method, storage, retention, and schedule, or create backups on demand. Restore options include: Latest: recover to the latest available state Point in time: restore to a specific date and time Specific backup: restore from a selected backup New Ansible playbooks Autobase 2.11 adds new Ansible playbooks for backup and recovery operatio ## Testing Infrastructure Code by Executing Its Real Expressions DevFeed: [Testing Infrastructure Code by Executing Its Real Expressions]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-08-28T07:00:00Z Content type: tutorial Language: en Sources: [Philipp Lehmann]() Topics: [Ansible](), [Testing](), [Pytest](), [Ansible Roles]() Tags: [ansible](), [ci-cd](), [code](), [infrastructure](), [infrastructure-as-code](), [pytest](), [testing]() ### AI overview This article explains how to test Ansible infrastructure code by rendering the shipped Jinja expression through Ansible's actual templating machinery. It recommends extracting the expression from the role file, using realistic fixture variables, and asserting on the rendered result instead of duplicating the computation in Python. ### Source excerpt Ansible Templar in pytest: render the shipped combine(recursive=True) expression from defaults/main.yml instead of a shallow Python paraphrase. ## Ansible roles: proxy\_env, ssh, etc\_hosts, libvirt released DevFeed: [Ansible roles: proxy\_env, ssh, etc\_hosts, libvirt released]() Original publisher: [Read original article]() Author: Staf Wagemakers Published: 2026-05-03T06:03:00Z Content type: release Language: en Sources: [stafwag Blog]() Topics: [Ansible Roles](), [releases](), [Ansible](), [ssh]() Tags: [ansible](), [apt](), [archlinux](), [changelog](), [debug](), [documentation](), [freebsd](), [kvm](), [libvirt](), [linux](), [pacman](), [releases](), [service](), [ssh]() ### AI overview The article announces releases for four Ansible roles: proxy_env 2.1.0, ssh 1.1.1, libvirt 2.1.0, and etc_hosts 1.1.1. It lists updates including package-management changes, handler fixes, documentation updates, lint corrections, and virtual-machine SSH host-key support. ### Source excerpt Made some time to do some work for a few Ansible roles that I maintain. You'll find the new releases below. ## Automatizar servidores con Ansible: primeros pasos DevFeed: [Automatizar servidores con Ansible: primeros pasos]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-01-08T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Ansible](), [Ansible Roles](), [ssh](), [dry-run](), [Git](), [nginx]() Tags: [ansible](), [dry-run](), [git](), [nginx](), [ssh](), [sysadmins](), [variables](), [vault]() ### AI overview A step-by-step introduction to automating server configuration with Ansible. It covers ad-hoc commands, inventories, playbooks, dry runs, roles, group variables, loops, and secrets with ansible-vault. ### Source excerpt Ansible desde cero: comandos ad-hoc, playbooks, roles, variables por grupo, bucles y secretos con ansible-vault, paso a paso. ## Ansible on Vagrant - skipping: no hosts matched DevFeed: [Ansible on Vagrant - skipping: no hosts matched]() Original publisher: [Read original article]() Author: Tom Published: 2015-12-29T00:00:00Z Content type: tutorial Language: en Sources: [Tomasz Gągor]() Topics: [Ansible](), [Vagrant](), [Ansible Roles](), [Testing](), [Raspberry Pi]() Tags: [ansible](), [linux](), [raspberry-pi](), [test](), [testing](), [tools](), [vagrant]() ### AI overview This tutorial explains how to resolve Ansible's "no hosts matched" problem when testing playbooks with Vagrant. The issue occurs because the testing machine is not included in the host group defined by the playbook; adding the Vagrant machine to that group in the Vagrantfile resolves it. ### Source excerpt I have some Ansible roles to configure my vps, Raspberry Pi, etc. I like to test them before I broke something on my real, not clustered machines - I use Vagrant for that. But with it I had one problem - in playbooks I define hosts as groups of severs ex. web for my vps: Example Ansible playbook - hosts: web gather_facts: True sudo: True ... But testing machine wasn't in this group and when I run vagrant I could only see: