Standardizing and Automating Infrastructure with Ansible

Configuration management

Automate recurring tasks, ensure consistency, and avoid manual errors. Where servers are currently set up manually and inconsistently, NETWAYS works with you to define reusable Ansible playbooks and roles—configurations become reproducible, documented, and rolled out consistently across all systems.

Reproducible Instead of Handmade

Every configuration is available as code and runs identically on all systems—no more manual updates.

New Servers in Minutes

Playbooks deploy standard setups in minutes—a process that would take hours to do manually.

Agent-free

Ansible works via SSH—no additional agent on the target systems, less maintenance, and a smaller attack surface.

Documented & Traceable

The code is the documentation; every change is versioned in Git and can be reviewed.

Consistency Enforced

The target state is defined—configuration drift is detected and corrected before it accumulates.

All in one place

Consulting, playbook development, operations, and training from NETWAYS—your open-source specialists.

The Problem

As long as servers are set up manually and inconsistently, nothing is reproducible—and over time, no one knows exactly what is configured where.

Server set up manually

Every admin does it a little differently. Setups are not reproducible and take time to reconfigure with every new system.

Configuration Drift

Over time, the systems drift apart. No one knows the actual state of affairs—errors are difficult to reproduce.

Knowledge is in people’s minds

Only one person knows how to set up the system. If it fails, the knowledge is lost—instead of being stored in shared, versioned code.

How we work with you

Four steps, identical for every NETWAYS solution—from standards to an automated, reproducible operational infrastructure.

Step 1

Analysis & Concept

We assess systems, recurring tasks, and standards, and determine what is worth automating.

→ We automate the tasks that truly save time and effort—not everything at any cost.

"

Step 2

Setup & Integration

We develop reusable playbooks and roles, version them in Git, and integrate them into a CI pipeline.

→ Infrastructure as Code instead of one-off scripts that no one understands anymore.

"

Step 3

Commissioning & rollout

Go-live: Configurations are rolled out consistently across all systems—in a controlled and traceable manner.

→ Deploy changes in a controlled manner instead of manually, system by system.

"

Step 4

Support & Operations

We maintain and expand the playbooks and, upon request, can take over operations (MyEngineer)—or train your team.

→ Automation remains relevant and evolves along with your environment.

What We Automate

From configuration as code to consistent rollout—the building blocks are interconnected and can be implemented step by step.

Ansible Playbooks

Configuration as Code

Server configuration is encapsulated in reusable playbooks and roles rather than in manual steps.

Result: identical , reproducible systems.

Infrastructure as Code

Versioned & Traceable

The playbooks are stored in Git: Changes are versioned, can be reviewed, and can be rolled back at any time.

Result: Every change is documented and traceable.

IT Automation

Rollouts & Routine

Recurring tasks—packages, services, updates—run automatically across all hosts.

Result: Hours of manual labor are reduced to minutes.

Infrastructure Automation

Ensure Consistency

The defined target state is enforced; deviations (drift) are detected and corrected.

Result: The systems no longer drift apart.

What You’ll Achieve

Faster and error-free, fully consistent, knowledge embedded in the code.

Faster & error-free

Standard setups are completed in minutes—without typos, missed steps, or manual rework.

Full consistency

All systems are in their defined target state—no drift, no unpleasant surprises during operation.

Knowledge in Code

Setups are documented and shared within the team, rather than being tied to individual people.

What is your solution built with?

Tried-and-true open-source components—run in-house or via NWS. You decide what you’ll do yourself and what NETWAYS will handle.

Ansible

The agentless automation engine: Playbooks and roles deploy configurations reproducibly to all systems via SSH.

Foreman

Expands configuration management to include provisioning and lifecycle management—from initial installation to the current patch status.

GitLab

Version controls the playbooks as Infrastructure as Code and executes them via CI pipelines in a tested and traceable manner.

Icinga

Monitors the standardized systems—to ensure that the target state is maintained during operation.

We’ll integrate what you’re already using with

The pipeline integrates code, security, and the target environment. A selection of the building blocks we use to build DevSecOps setups.

Operating Systems

RHEL / CentOS
Debian / Ubuntu
SUSE
Windows

Code & CI

GitLab
Git
CI Pipelines
Molecule (Tests)

Operations & Quality

Icinga
Idempotence
Drift Checks
Reporting

Automation

Ansible
Playbooks & Roles
AWX / AAP
Ansible Galaxy

Provisioning & Cloud

Foreman
VMware
Proxmox
Cloud APIs

Questions & Answers

Frequently Asked Questions About This Solution

What is configuration management?

2

3

Configuration management involves centrally defining the desired state of systems and enforcing it automatically—rather than setting up each server manually. Tools like Ansible describe the configuration as code, ensuring that all systems are set up in a reproducible, consistent, and documented manner.

What is Ansible?

2

3

Ansible is an open-source tool for automation and configuration management. It operates agentlessly via SSH and describes the desired state in human-readable playbooks. This allows you to install software, configure services, and automate recurring tasks across many systems.

What is Infrastructure as Code?

2

3

Infrastructure as Code (IaC) means describing infrastructure and configuration as versioned code rather than setting them up manually. The code is stored in Git, is reviewable and reproducible—every change is traceable and can be rolled out automatically and identically.

Ansible vs. Puppet – What's the Difference?

2

3

Ansible is agentless (push via SSH) and can be deployed quickly using easy-to-read playbooks. Puppet typically operates on an agent-based (pull) model and excels at managing very large, permanently enforced states. For most environments, Ansible is the more accessible and flexible option—we provide unbiased advice based on your specific use case.

Is Ansible really agentless?

2

3

Yes. Ansible connects via SSH (or WinRM on Windows) and requires only Python on the target systems—no permanently running agent. This reduces maintenance and the attack surface, and makes getting started much easier.

How are Ansible and Foreman related?

2

3

Foreman handles provisioning and lifecycle management—that is, the deployment and management of servers—while Ansible handles the fine-tuning of configurations. Together, they cover the entire process, from initial installation to ongoing configuration. Learn more about this in our solution for server provisioning and lifecycle management with Foreman.

Book a personal consultation with AlinaIndividual open source solutions tailored to you and your business.Get in touch