# Ansible Ansible is open-source automation technology that uses playbooks to automate tasks and manage system configuration. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Self-Hosted Platform Build Order: Dependencies from Bare Metal to Model Serving DevFeed: [Self-Hosted Platform Build Order: Dependencies from Bare Metal to Model Serving]() Original publisher: [Read original article]() Author: Philipp Lehmann (philipp.lehmann@gruppe.ai) Published: 2026-09-04T07:00:00Z Content type: article Language: en Sources: [Philipp Lehmann]() Topics: [Self-hosted](), [Ansible](), [Kubernetes](), [ceph](), [observability](), [model-serving](), [Compose]() Tags: [ansible](), [architecture](), [article](), [ceph](), [compose](), [infrastructure-as-code](), [kubernetes](), [model-serving](), [observability](), [self-hosted]() ### AI overview This article explains the dependency order for building a self-hosted platform. It covers consistent bare-metal inventory, Ansible configuration convergence, networking, Kubernetes, Ceph storage, identity, observability, and model serving. ### Source excerpt Self-hosted platform build order: why mesh, cluster, Ceph storage, identity and observability must precede model serving, shown with Compose depends_on. ## 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. ## Using netlab in Software Testing with Dinesh Dutt DevFeed: [Using netlab in Software Testing with Dinesh Dutt]() Original publisher: [Read original article]() Published: 2026-08-28T06:26:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Software Testing](), [networking](), [software-development](), [Ansible](), [Vagrant]() Tags: [ansible](), [development](), [netlab](), [network](), [networking](), [podcast](), [software](), [software-development](), [software-gone-wild](), [software-testing](), [testing]() ### AI overview This article introduces Episode 208 of Software Gone Wild, a conversation about using netlab to test network management software. It discusses how netlab helps Stardust Systems test new SuzieQ features, along with related history involving Vagrant and Ansible. ### Source excerpt I know a few software development companies use netlab to test their network management software (and contribute back to netlab - thanks a million!), and I always wanted to chat about that. As I have known Dinesh Dutt for ages, it wasn't hard to decide who to invite to have that chat with ;) As it turns out, it's dangerous to put Dinesh1 and me in the same (virtual) room - we were all over the place, from the ancient history of Vagrant in networking labs to the recent Ansible woes, but we did manage to cover how netlab helps Stardust Systems test new SuzieQ features. Read more ... ## Infrastructure Control Plane | Day 2 Operations & Drift DevFeed: [Infrastructure Control Plane | Day 2 Operations & Drift]() Original publisher: [Read original article]() Author: Nicole Morgan Published: 2026-08-06T00:00:00Z Content type: article Language: en Sources: [Harness Blog]() Topics: [Infrastructure as code](), [Software-defined networking](), [Provisioning](), [Ansible](), [CI/CD](), [configuration](), [Amazon EC2](), [AWS CloudFormation](), [Amazon Web Services]() Tags: [ansible](), [aws](), [ci-cd](), [cloudformation](), [configuration](), [deployment](), [ec2](), [incident](), [infrastructure](), [infrastructure-as-code](), [provisioning](), [systems](), [tools]() ### AI overview This article explains that infrastructure problems often emerge during day 2 operations, after initial deployment. It describes how console changes, incidents, and isolated Terraform, Ansible, and CI/CD workflows create infrastructure drift, and argues that control planes can enforce governance, detect divergence, and automate remediation. ### Source excerpt Learn why infrastructure breaks after deployment and how control planes enforce governance, detect drift, and automate remediation across Terraform, Ansible, an | Blog ## What are the best platforms for network automation? DevFeed: [What are the best platforms for network automation?]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-07-24T08:25:02Z Content type: article Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [Network](), [Automation](), [Ansible](), [Orchestration](), [awx](), [Low code]() Tags: [ansible](), [automation](), [awx](), [faq](), [low-code](), [nautobot](), [network](), [network-automation](), [orchestration](), [red-hat](), [source-of-truth]() ### AI overview The article lists Nautobot, Itential, Ansible, AWX, and Red Hat Ansible Automation Platform as network automation platforms. It states that they serve different purposes, including configuration, orchestration, source of truth and inventory, and enterprise low-code use cases. ### Source excerpt The best platforms for network automation include Nautobot, Itential, Ansible, AWX, Red Hat Ansible Automation Platform to name a few. Each one serves a different purpose including configuration and orchestration, source of truth and inventory and enterprise low code. Check out my dedicated post on network automation platforms ## What is Ansible? DevFeed: [What is Ansible?]() Original publisher: [Read original article]() Author: Roger Perkin Published: 2026-07-23T18:25:09Z Content type: tutorial Language: en Sources: [Roger Perkin Network Automation Consultant]() Topics: [Ansible](), [Automation](), [configuration](), [Network](), [Open Source](), [ssh](), [YAML](), [Server]() Tags: [ansible](), [applications](), [automation](), [configuration](), [faq](), [network](), [open-source](), [servers](), [ssh](), [tasks](), [yaml]() ### AI overview Ansible is an open-source, agentless IT automation tool for configuring systems, deploying applications, and managing network devices. It uses human-readable YAML playbooks and connects through SSH to automate repetitive changes across routers, switches, and servers. ### Source excerpt Ansible is an open-source IT automation tool that configures systems, deploys applications, and manages network devices using simple, human-readable YAML files called playbooks. It's agentless, connecting via SSH, and widely used by network engineers to automate repetitive tasks like configuration changes across routers, switches, and servers at scale. ## On the Futility of Opening Ansible Issues DevFeed: [On the Futility of Opening Ansible Issues]() Original publisher: [Read original article]() Published: 2026-07-22T06:03:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Ansible](), [bug](), [Open Source](), [configuration](), [networking]() Tags: [ansible](), [bug](), [cli](), [github](), [network](), [open-source]() ### AI overview The author describes opening an Ansible issue after discovering that the cisco.ios.ios_config module did not report rejected Cisco IOS configuration commands. The issue was initially closed without the proposed error-message fix, but an update says it was later reopened and fixed shortly after publication. ### Source excerpt Remember the anonymous troll who chided me for writing a rant instead of opening a GitHub issue in the relevant Ansible repository? Well, I decided to be an open-source poster boy when I stumbled upon the next Ansible bug, and ended up feeling like a sweet summer child :( Read more ... ## Orchestration powered by Temporal at Zscaler: Wrap, don't rewrite DevFeed: [Orchestration powered by Temporal at Zscaler: Wrap, don't rewrite]() Original publisher: [Read original article]() Author: Abhishek Mitra Published: 2026-07-22T00:00:00Z Content type: opinion Language: en Sources: [Temporal Blog]() Topics: [Orchestration](), [Automation](), [Ansible](), [opentofu](), [Terraform](), [argocd](), [GitOps](), [Provisioning]() Tags: [ansible](), [automation](), [aws-cloudformation](), [bash](), [ci](), [cli](), [gitops](), [infrastructure-as-code](), [orchestration](), [provisioning](), [temporal-voices]() ### AI overview The article describes how Zscaler designed a durable orchestration contract above eight heterogeneous automation engines, including Ansible, Terraform, OpenTofu, Helm, ArgoCD, Crossplane, Kubernetes Cluster API, AWS CloudFormation, and Jenkins. The approach aims to coordinate existing tools without rewriting them. ### Source excerpt How one durable contract above eight automation engines changed Zscaler's architecture without changing the engines ## Content: New Parameter in Multiple something\_config Ansible Modules DevFeed: [Content: New Parameter in Multiple something\_config Ansible Modules]() Original publisher: [Read original article]() Published: 2026-07-15T05:22:00Z Content type: opinion Language: en Sources: [ipSpace.net blog]() Topics: [Ansible](), [configuration](), [Network](), [issue tracker]() Tags: [ansible](), [network]() ### AI overview The article discusses new parameters added to several Ansible network device configuration modules after concerns about templating behavior and a change introduced in Ansible 12. It describes the author's issue report and notes that the issue's closure was due to poor issue management rather than rejection of the proposed solution. ### Source excerpt Last December, I wrote a pretty ranty post explaining how Ansible release 12 broke (some?) network device configuration playbooks. The inevitable anonymous troll (why are they always anonymous?) couldn't resist asking whether I opened an issue on GitHub. I didn't (more about that later), but when the solution to that rant was "we're deprecating using templates in src" parameter, I opened an issue arguing why that's not a good idea. Read more ... ## How to Troubleshoot and Debug Ansible Playbooks DevFeed: [How to Troubleshoot and Debug Ansible Playbooks]() Original publisher: [Read original article]() Author: Mrinalini Sugosh Published: 2026-07-15T00:00:00Z Content type: tutorial Language: en Sources: [Harness Blog]() Topics: [Ansible](), [debugging](), [Infrastructure as code](), [YAML]() Tags: [ansible](), [debugging](), [how-to](), [iac](), [infrastructure-as-code](), [troubleshooting](), [yaml]() ### AI overview This tutorial explains how to troubleshoot and debug Ansible playbooks. It covers structured and conditional debugging, verbosity controls, targeted variable inspection, reusable debugging roles, failure taxonomies, and CI/CD-friendly logging. It also describes common problems such as syntax errors, variable conflicts, connection errors, and inconsistent execution across hosts. ### Source excerpt Master how to debug Ansible with expert tips for troubleshooting playbooks. Learn structured debugging, reduce errors, and streamline Infrastructure Deployments | Blog ## Ubuntu Server on the NVIDIA DGX Spark (Without the Desktop) DevFeed: [Ubuntu Server on the NVIDIA DGX Spark (Without the Desktop)]() Original publisher: [Read original article]() Author: Techno Tim Published: 2026-06-22T13:00:00Z Content type: tutorial Language: en Sources: [Techno Tim]() Topics: [DGX Spark](), [Ubuntu](), [NVIDIA DGX](), [GPU](), [NVLink](), [CUDA](), [Docker](), [Ansible](), [vllm](), [Blackwell](), [networking](), [GitHub]() Tags: [ai](), [ansible](), [blackwell](), [cuda](), [dell](), [dgx-spark](), [docker](), [github](), [gpu](), [homelab](), [networking](), [nvidia-dgx](), [nvlink](), [ubuntu](), [vllm]() ### AI overview A guide to replacing DGX OS with a minimized Ubuntu 24.04 Server installation on GB10 systems such as the NVIDIA DGX Spark and ASUS Ascent GX10. It explains the memory and power benefits of removing GNOME while retaining the NVIDIA drivers, CUDA, Docker, and NVIDIA Container Toolkit, and covers ConnectX-7 networking, dual-node setup, and Ansible automation. ### Source excerpt When you buy an NVIDIA DGX Spark or an ASUS Ascent GX10, it ships with DGX OS. DGX OS is NVIDIA's managed Ubuntu image, and it is fine - if you want a full GNOME desktop on an AI box. I did not want that. The GB10 has 128 GB of unified memory shared between the CPU and GPU over NVLink-C2C. Every gigabyte the OS and desktop environment consume is a gigabyte not available to your model. On the ... ## Technology Short Take 196 DevFeed: [Technology Short Take 196]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2026-05-22T14:00:00Z Content type: article Language: en Sources: [Scott's Weblog]() Topics: [datacenter](), [networking](), [Cybersecurity](), [Linux](), [Terraform](), [Artificial Intelligence](), [Ansible](), [Large Language Model](), [Cloud](), [cURL](), [npm]() Tags: [ai](), [ansible](), [article](), [aws](), [cilium](), [cli](), [cloud](), [cni](), [containers](), [cri-o](), [curl](), [cybersecurity](), [data-center](), [devops](), [docker](), [go](), [iac](), [k8s](), [kubernetes](), [linux](), [llms](), [networking](), [npm](), [oci](), [security](), [technologies](), [terraform]() ### AI overview Technology Short Take 196 is a curated list of articles about data center technologies, covering networking, servers and hardware, security, cloud management, operating systems, and applications. Topics include Ansible and IPSet, WireGuard and Headscale, a compromised Bitwarden CLI package on NPM, curl vulnerabilities, Terraform, AWS MCP Server, AI-assisted infrastructure as code, llama.cpp on Apple Silicon, Chrome's local AI model installation, Linux 7.0 and PostgreSQL, and Linux desktop voice typing. ### Source excerpt Welcome to Technology Short Take 196! Just in time for the US Memorial Day holiday, I am back with another list of articles related to various data center technologies like networking, security, operating systems, and applications. You will find articles on VPNs, Linux local privilege escalation (LPE) vulnerabilities, browser quirks and workarounds, the death of Terraform (again), and so much more. Enjoy your weekend reading! Networking Andrew Ward shares an Ansible role to block abusive subnets using IPSet. From this article on switching to WireGuard from Tailscale, I learned about Headscale (an open source implementation of the Tailscale control plane). Servers/Hardware Doug Dawson looks at some innovations that continue to improve computing power. Doug's article includes a few items I hadn't yet heard of. Security Bitwarden confirmed a compromise of its CLI package on NPM. First, we had CopyFail. Now we have Dirty Frag and Fragnesia. Daniel Stenberg talks about how Mythos found a single vulnerability--yes, just one--in curl. I don't really have words for this...security incident? That doesn't seem like the correct way to describe such a massive oversight, especially when you realize it happened to a cybersecurity agency. "Oops" doesn't even begin to describe it. Cloud Computing/Cloud Management Graham Gilbert insists Terraform is dead. I wonder what sorts of things the AWS MCP Server will make possible? William Collins argues in favor of AI through IaC rather than instead of it. I enjoyed this article. Collins indicates that while authoring IaC using LLMs is working rather well, managing infrastructure using LLMs is another story entirely. If you're at all interested in the intersection of LLMs and IaC, I'd add this to your reading list. Operating Systems/Applications Eric Sloof looks at using llama.cpp to run your own local, private AI stack on Apple Silicon. Mat Duggan examines his descent from artist to mercenary as a result of finding LLMs more useful than he exp ## Speeding Up Ansible NetBox Inventory with Caching and Fewer API Lookups DevFeed: [Speeding Up Ansible NetBox Inventory with Caching and Fewer API Lookups]() Original publisher: [Read original article]() Author: Rick Donato Published: 2026-05-05T09:00:12Z Content type: tutorial Language: en Sources: [Packet Coders - Learn Network Automation]() Topics: [Ansible](), [NetBox](), [API](), [Caching]() Tags: [ansible](), [api](), [caching](), [netbox](), [tips]() ### AI overview This tip explains how to improve Ansible NetBox inventory load times by enabling caching and disabling unused extra lookups in the netbox.netbox.nb_inventory plugin. These changes reduce calls to NetBox API endpoints. ### Source excerpt NetBox/Ansible Tip: The netbox.netbox.nb_inventory plugin pulls data from multiple NetBox API endpoints. Enable caching and disable unused extra lookups to reduce API calls and improve inventory load times. Here's what you need to add to your NetBox inventory plugin file: # Cache inventory data cache: ## 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. ## How Claude Helped Build a Proxmox Environment (and What I Learned Along the Way) DevFeed: [How Claude Helped Build a Proxmox Environment (and What I Learned Along the Way)]() Original publisher: [Read original article]() Author: info@goteleport.com (Steven Oakley) Published: 2026-04-24T00:00:00Z Content type: article Language: en Sources: [Teleport]() Topics: [Claude](), [Homelab](), [Proxmox](), [Ansible](), [Terraform](), [rhel 10](), [Zero Trust](), [Windows](), [ssh]() Tags: [ansible](), [claude](), [homelab](), [proxmox](), [rhel-10](), [ssh](), [terraform](), [windows](), [zero-trust]() ### AI overview Steven Oakley describes using Claude with Terraform and Ansible to build and migrate a Proxmox homelab. The project includes RHEL 10 and Windows infrastructure, automated domain deployment, and Teleport agent connections to self-hosted and cloud environments. ### Source excerpt Enterprise Solutions Engineer Steven Oakley walks through building a Proxmox homelab using Claude as an engineering assistant and the lessons learned along the way. ## Wix Migrated Its MySQL EC2 Fleet from Intel CPUs to Graviton DevFeed: [Wix Migrated Its MySQL EC2 Fleet from Intel CPUs to Graviton]() Original publisher: [Read original article]() Author: Wix Engineering Published: 2026-03-23T11:27:39Z Content type: article Language: en Sources: [Wix Engineering]() Topics: [Graviton](), [MySQL](), [Ansible](), [awx](), [Amazon EC2](), [intel](), [Databases](), [DevOps](), [Replication](), [Server](), [Linux]() Tags: [amazon](), [ansible](), [awx](), [devops](), [ec2](), [graviton](), [infra](), [intel](), [linux](), [mysql](), [rdbms](), [replication]() ### AI overview Wix's DB Infra team migrated more than 1,000 MySQL EC2 servers across over 160 clusters from Intel-based CPUs to Graviton in one month, ahead of the original three-month timeline. The project also enabled a move to Amazon Linux 2023 and away from CentOS 7.0, using AWX workflows and Wix's Dev Portal to automate the process while accounting for replication and cluster reliability concerns. ### Source excerpt Last January, the DB Infra team at Wix embarked on a strategic and very important mission: Migrating all of our MySQL EC2 servers from Intel based CPUs to the new shiny Graviton ones. Not only will this allow us to work on better CPUs, saving us money and improving our databases, we'll be able to move to Amazon Linux 2023 OS and move from the EOL CentOS 7.0. That sounds simple enough, until you realize that we're dealing with over 1K servers spread over 160+ MySQL clusters. The initial... ## Как мы управляем арсеналом из 500 тестовых стендов: инфраструктурный опыт hh.ru DevFeed: [Как мы управляем арсеналом из 500 тестовых стендов: инфраструктурный опыт hh.ru]() Original publisher: [Read original article]() Author: wlpnnn (hh.ru) Published: 2026-03-13T05:10:00Z Content type: article Language: ru Sources: [HeadHunter RU]() Topics: [Testing](), [Kubernetes](), [Docker](), [nginx](), [PostgreSQL](), [Redis](), [Ubuntu](), [Ansible]() Tags: [ansible](), [docker](), [e2e](), [iac](), [jira](), [kubernetes](), [nginx](), [postgresql](), [qa](), [redis](), [tag-7b800b2da0b8](), [tag-9653a3ac62a2](), [tag-b3a2b40e0fa4](), [testing](), [ubuntu]() ### AI overview A QA engineer at hh.ru describes the company's infrastructure for managing 500 test stands. The article explains personal and specialized environments, deployment profiles, isolated Ubuntu-based virtual machines, Docker containers, Kubernetes namespaces, and automated testing workflows linked to Jira. ### Source excerpt Привет! Меня зовут Карина, я QA-инженер в hh.ru. Наша компания растёт, а вместе с ней -- число команд, вовлечённых в разработку и функционал. Появляются новые сервисы, базы данных, очереди. Каждый компонент требует слаженной работы и надёжной поддержки на тестовых стендах. Сегодня мы работаем с гибкой тестовой средой, которую можно настроить под любую задачу. В статье расскажу, как вся эта сложная система выглядит изнутри. Читать далее ## Technology Short Take 191 DevFeed: [Technology Short Take 191]() Original publisher: [Read original article]() Author: Scott Lowe Published: 2026-02-27T14:00:00Z Content type: article Language: en Sources: [Scott's Weblog]() Topics: [networking](), [Ansible](), [Security](), [Infrastructure as code](), [Artificial Intelligence](), [Large Language Model](), [Containers](), [VXLAN]() Tags: [ai](), [ansible](), [aws](), [blog](), [cilium](), [cli](), [cloud](), [cni](), [containers](), [cri-o](), [devops](), [docker](), [go](), [gre](), [iac](), [k8s](), [kubernetes](), [linux](), [llm](), [network-automation](), [networking](), [oci](), [security](), [vxlan]() ### AI overview Technology Short Take 191 is a curated collection of commentary and links covering networking, network automation, security, cloud management, containers, operating systems, applications, AI adoption, and software vulnerabilities. ### Source excerpt Welcome to Technology Short Take #191! This is my semi-regular collection of links related to technology disciplines, including networking, security, cloud computing, storage, and programming/development. I hope that I've managed to curate an interesting and useful set of links for readers. Enjoy! Networking I learned a new acronym from Ivan Pepelnjak in his article on "not so passive" OPSFv2 interfaces in Cisco IOS/XR: QDS (Quick and Dirty Solution). I am totally using that from now on. Via Ivan (hat tip to my colleague Russ for pointing me in this direction), I also learned that all is not well in network automation land with Ansible. Although some parts of it are apparently now resolved, this does raise questions about the viability of Ansible for network automation. Doug Dawson talks about the new Amazon Eero Signal, a cellular backup to a primary broadband connection for users using their Eero mesh systems. I agree with Doug--the pricing seems high to me. I generally like the Eero devices, although there have been times when I really could use a bit more control over the settings. Security The APNIC blog features a guest article discussing the use of tunneling protocols to infiltrate networks. The article specifically discusses Generic Routing Encapsulation (GRE) and Virtual Extensible LAN (VXLAN). It's worth a read if your network uses either of these technologies. Cloud Computing/Cloud Management Somewhere along the way I missed the CDK deprecation announcement. If I am not mistaken, this leaves Pulumi as the only cloud-independent IaC tool that lets you use a general purpose programming language. Managing dependencies between containers can be difficult at times; this blog post by Nicolas Fränkel introduced me to wait4x, a tool one can use to help simplify these types of situations. Operating Systems/Applications I appreciated reading Mitchell Hashimoto's AI adoption journey. I feel it does provide a more realistic approach to how someone in a role like his m ## My 2026 Homelab Tour (Rack + Servers + Network + Storage) DevFeed: [My 2026 Homelab Tour (Rack + Servers + Network + Storage)]() Original publisher: [Read original article]() Author: Techno Tim Published: 2026-02-26T13:00:00Z Content type: article Language: en Sources: [Techno Tim]() Topics: [Homelab](), [Network](), [Server](), [5G](), [Ansible](), [Pi-hole](), [USB](), [ssh]() Tags: [2026](), [5g](), [ansible](), [backup](), [dns](), [homelab](), [hosting](), [house](), [hub](), [internet](), [network](), [poe](), [raspberry-pi](), [self-hosting](), [server](), [servers](), [ssh](), [storage](), [testing](), [ups]() ### AI overview A 2026 tour of a homelab covering network connectivity, backup 5G internet, whole-home wiring, PoE equipment, Raspberry Pi systems, UPS coordination, NUT Server, Pi-hole, and Ansible-based SSH key rotation. ### Source excerpt My homelab has changed again... 2026. This year turned into a full evolution: network upgrades, compute refreshes, storage testing, and a bunch of power/UPS changes that change how I run (and recover) everything. Self-hosting guide next - subscribe for the follow up. Watch the video The wall of tech (everything that doesn't fit the rack) Before we even touch the rack, let's start with th... ## Configuring 6PE Route Reflector on Cisco IOS DevFeed: [Configuring 6PE Route Reflector on Cisco IOS]() Original publisher: [Read original article]() Published: 2026-02-26T07:19:00Z Content type: tutorial Language: en Sources: [ipSpace.net blog]() Topics: [Cisco](), [BGP](), [configuration](), [networking](), [Ansible](), [NETCONF](), [REST API]() Tags: [ansible](), [bgp](), [cisco](), [configuration](), [logging](), [mpls](), [netconf](), [netlab](), [rest-api]() ### AI overview The article explains a Cisco IOS configuration issue affecting BGP route reflectors for MPLS 6PE and L3VPN. IPv6 labeled-unicast and VPNv6 address-family commands may appear to apply through Ansible's ios_config module but not persist in the BGP configuration unless IPv6 routing is enabled with ipv6 unicast-routing. The article also argues that NETCONF or REST API mechanisms could report configuration failures more consistently than CLI-based automation. ### Source excerpt Imagine you want to deploy a BGP route reflector for MPLS 6PE or L3VPN service. Both services run over MPLS LSPs, use IPv4 BGP sessions, and use IPv4 next hops for BGP routes. There's absolutely no reason to need IPv6 routing on a node that handles solely the control-plane activity (it never appears as a BGP next hop anywhere), right? Cisco IOS disagrees, as I discovered when running route reflector integration tests for netlab 6PE and (MPLS) L3VPN functionality. Most platforms failed those tests because we forgot to configure route-reflector-clients in labeled IPv6 and VPNv4/VPNv6 address families1. That was easy to fix, but the IOS-based devices were still failing the tests, with nothing in the toolchain ever complaining about configuration problems. Read more ... ## Git para sysadmins: control de versiones DevFeed: [Git para sysadmins: control de versiones]() Original publisher: [Read original article]() Author: Antonio Pérez Published: 2026-02-16T00:00:00Z Content type: tutorial Language: es Sources: [tengoping.com]() Topics: [Git](), [Linux](), [Ansible](), [nginx](), [Firewall](), [Terraform](), [Command-line interface](), [Script](), [Terminal](), [Gitea](), [GitHub](), [GitLab]() Tags: [ansible](), [env-file-security](), [firewall](), [git](), [github](), [gitlab](), [linux](), [scripts](), [sysadmin](), [sysadmins](), [terminal](), [terraform]() ### AI overview A practical Spanish-language guide explains how sysadmins can use Git to version server configurations, infrastructure-as-code files, and maintenance scripts. It covers repository setup, commits, branches, remotes, collaboration, and avoiding secrets in version control. ### Source excerpt Guía práctica de Git para sysadmins: versiona configuraciones, gestiona infraestructura como código y colabora en equipo sin miedo a romper nada. ## Fast Arista cEOS Container Configuration DevFeed: [Fast Arista cEOS Container Configuration]() Original publisher: [Read original article]() Published: 2026-02-09T06:23:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Containers](), [Command-line interface](), [Ansible]() Tags: [ansible](), [cli](), [container](), [containers](), [net-11](), [netlab]() ### AI overview The article explains how to configure Arista cEOS containers by executing netlab-generated EOS configuration snippets through FastCli. It describes wrapper requirements, Ansible template and error-handling issues, and a startup timing problem addressed in netlab release 26.02 by waiting for SSH availability and enabling shell configuration mode. ### Source excerpt After the enormous speedup I achieved with the FRR containers, I tried to do something similar with the Arista cEOS ones. After all, Arista's pretty open about running its software on standard Linux, so it should be possible to map host-side configuration files into container-side scripts and execute them, right? There was just one tiny gotcha: all netlab-generated EOS configuration files are device configuration snippets that are intended to be submitted via EOS CLI, and I didn't feel like cracking open the netmiko documentation (that's another backburner project). However, Arista cEOS includes this magic command called FastCli ;) Read more ... ## Interface MAC Address in IOS Layer-2 Images DevFeed: [Interface MAC Address in IOS Layer-2 Images]() Original publisher: [Read original article]() Published: 2026-02-03T07:08:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Cisco](), [bug](), [configuration](), [Ansible](), [Code]() Tags: [ansible](), [bug](), [cisco](), [code](), [configuration](), [netlab]() ### AI overview The article explains that Cisco IOS layer-2 images change an interface's MAC address when its switchport status changes. It also describes how a bug in a netlab Jinja template and Ansible's configuration comparison can leave the resulting device configuration inconsistent. ### Source excerpt Here's another "You can't make this up, but it sounds too crazy to be true" story: Cisco IOS layer-2 images change the interface MAC address when you change the interface switchport status. Let me start with a bit of background: IOL Layer 2 image starts with interfaces enabled and in bridged (switchport) mode (details) netlab has to run a normalize script (applicable to IOLL2, IOSv L2, and Arista EOS) before configuring anything else to ensure all interfaces are shut down. The IOLL2 normalize Jinja template had a bug - when setting the interface MAC address, it checked l.mac_address instead of intf.mac_address. Nevertheless, everything worked because the MAC addresses were also set during the initial device configuration. Read more ... ## Fast FRR Container Configuration DevFeed: [Fast FRR Container Configuration]() Original publisher: [Read original article]() Published: 2026-02-02T06:47:00Z Content type: article Language: en Sources: [ipSpace.net blog]() Topics: [Docker](), [Containers](), [Ansible](), [Bash](), [configuration](), [race-condition]() Tags: [ansible](), [bash](), [configuration](), [container](), [docker](), [infrastructure](), [netlab](), [race-condition]() ### AI overview This article describes netlab's effort to configure FRR containers by executing generated Linux scripts through docker exec. It explains using shebangs to select vtysh or another interpreter, and reports integration-test issues including timing problems and a race condition involving parallel VLAN configuration. ### Source excerpt After creating the infrastructure that generates the device configuration files within netlab (not in an Ansible playbook), it was time to try to apply it to something else, not just Linux containers. FRR containers were the obvious next target. netlab uses two different mechanisms to configure FRR containers: Data-plane features are configured with bash scripts using ip commands and friends. Control-plane features are configured with FRR's vtysh I wanted to replace both with Linux scripts that could be started with the docker exec command. Read more ... [Next page]()