Configuration management with Ansible

Standardize IT Infrastructure

In many companies, servers are still set up inconsistently and manually. Configuration management with Ansible provides a solution: We work with you to define reusable playbooks and roles so that configurations can be rolled out in a reproducible, documented, and consistent manner.

Reproducible Instead of Manual

Each configuration is available as code and runs identically on all systems. Manual retightening is not necessary.

New Servers in Minutes

Ansible playbooks deploy standard setups in minutes. If done manually, it would take hours.

Agent-free

Ansible works via SSH. No additional agent on the target systems, which reduces maintenance and the attack surface.

Documented & Traceable

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

Enforced Consistency

The target state has been defined once. Configuration drift is detected and corrected before it can accumulate.

All in one place

As open-source experts, we offer you a one-stop solution: consulting, playbook development, operations, and training.

Common Problems with Manual Server Configuration

If servers are set up manually and inconsistently, nothing is reproducible. Without centralized configuration management, no one knows exactly what is configured on which server.

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 what the actual situation really is anymore, and it’s becoming difficult to trace errors.

Knowledge is in people’s minds

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

How we work with you

Four Steps to Successful Configuration Management. They guide you from the initial standards to an automated, reproducible infrastructure in a live environment.

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.

"
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, monitored, and traceable.

→ 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

Configuration as code is the starting point; a consistent rollout is the result. The building blocks are interconnected and can be introduced 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 such as packages, services, and updates run automatically on all hosts.

Result: Hours of manual work 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.

Here’s how you can do that

Consistency, Speed, and Traceability Through Configuration Management with Ansible

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?

For your configuration management, we rely on proven open-source components that run either in-house or via NETWAYS Web Services. You decide what you’ll do yourself and what we’ll take care of.

Ansible

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

Foreman

Extends configuration management to include provisioning and lifecycle management: initial installation, updates, and patch management.

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 deployed 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. Configuration management software such as Ansible describes 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 in Git, is available for review, and is 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 way to get started. We provide impartial advice based on the specific application.

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. Ansible handles the fine-tuning. 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.

What is the difference between Ansible and AWX, or the Ansible Automation Platform?

2
3
Ansible is the automation engine that executes playbooks. AWX (the open-source version) and the Ansible Automation Platform (AAP, the commercial version from Red Hat) provide a web interface and user management on top of it. This allows playbooks to be executed, scheduled, and released to the team in a controlled manner from a central location.

We look forward to your message






    captcha