---
title: "Ansible"
description: "4 posts about Ansible, summarised, each linking to the original."
---

# Ansible
> 4 posts about Ansible, summarised, each linking to the original.

## Articles

### [Managing edge solutions with Red Hat: A layered approach](https://yomu.fyi/post/managing-edge-solutions-with-red-hat-a-layered-approach.md)
- Company: [Red Hat](https://yomu.fyi/company/red-hat.md)
- Author: Daniel Froehlich
- Published: Sep 25, 2026
- Type: Explainer

Managing edge infrastructure at scale across hundreds of locations demands consistent management rather than disparate tools. Red Hat’s layered approach organizes tools into three compartments: a universal foundation, OS-level fleet management for RHEL, and Kubernetes lifecycle management for OpenShift. The universal layer includes Ansible for agentless automation, Quay for container image registry with geo-replication, Lightspeed for proactive drift detection and compliance, and Trusted Software Supply Chain for end-to-end security. For RHEL-based edges, Edge Manager provides SaaS fleet management with OTA updates while Satellite offers on-premise content management for air-gapped environments. For OpenShift-based edges, Advanced Cluster Management handles cluster lifecycle and zero-touch provisioning while Advanced Cluster Security enforces container security across the fleet.


### [From incident to remediation: Building an AI-driven AIOps workflow with Red Hat Ansible Automation Platform](https://yomu.fyi/post/from-incident-to-remediation-building-an-ai-driven-aiops-workflow-with.md)
- Company: [Red Hat](https://yomu.fyi/company/red-hat.md)
- Author: Neha Chugh
- Published: Sep 5, 2026
- Type: Tutorial

This tutorial builds an AIOps workflow for diagnosing and remediating a deliberately induced CPU incident in a product catalog application running on an AWS EC2 instance with RHEL. An Ansible investigation playbook collects CPU utilization, top processes, application status, and HTTP health evidence, which Claude Code analyzes through MCP to identify the Python process as the likely contributor and recommend the approved “AIOps - Remediate High CPU” Job Template. AI does not access the host directly: Ansible Automation Platform retains responsibility for credentials, inventory, execution, and remediation. The remediation changes the application from HTTP 503 and degraded to HTTP 200 and healthy, while a final health check confirms recovery and completes the detect-investigate-analyze-recommend-execute-verify sequence.


### [Build AI-assisted firewall workflows with Ansible Automation Platform](https://yomu.fyi/post/build-ai-assisted-firewall-workflows-with-ansible-automation-platform.md)
- Company: [Red Hat](https://yomu.fyi/company/red-hat.md)
- Author: Michal Zdyb
- Published: Sep 4, 2026
- Type: Problem & solution

The workflow replaces a manual, fragmented process for turning a simple ServiceNow connectivity request into firewall changes. Event-Driven Ansible connects ServiceNow, GitHub, an LLM, and two Palo Alto Networks firewalls, checking drift, gathering topology data, and coordinating structured rule proposals, pull requests, and workflow records. Ansible Automation Platform keeps credentials away from the AI and deploys approved rules through a deterministic, idempotent path after engineer and CAB approvals. GitHub’s main branch records the last successful state, proposed changes are reviewed as Configuration as Code, and execution stops when live configuration differs from the intended state. The lab demonstrates partial coverage, no coverage, and an unresolvable request; failed deployments can roll back, while an undefined Palo Alto Networks App-ID stops the workflow for human intervention.


### [How Ansible® Automation Powers the Uber Corporate Network at a Global Scale](https://yomu.fyi/post/how-ansible-automation-powers-the-uber-corporate-network-at-a-global-s.md)
- Company: [Uber](https://yomu.fyi/company/uber.md)
- Published: Apr 30, 2026
- Type: Explainer

Uber’s corporate network spans offices across six continents and around 5,000 devices, creating a configuration-management problem involving continuous updates, regional variation, and hardware from multiple vendors. The post explains why Uber uses Ansible for on-premises network configuration while Terraform handles cloud provisioning and Puppet manages configuration on running machines. Its Daily Nightly Enforcement workflow backs up each region’s running configuration to a private GitHub repository, gathers device facts, renders vendor-specific golden configurations through inventory variables and Jinja templates, and pushes them overnight, with failures triggering alerts. Inventory groups encode desired state across regions, functions, and operating systems, while custom roles, formatters, cleanup jobs, and occasional Ansible or Python modules address scale and vendor-specific gaps. The conclusion says this automation makes the diverse network manageable, stable, updated, and ready for daily use, although some hardware still requires other portals.