Centrally Manage the Server Lifecycle—From Provisioning to Patching

Provisioning

Provisioning, patching, and lifecycle management from a system’s first day to its last. NETWAYS is setting up Foreman as a central hub—from initial installation through patch statuses to decommissioning. Ansible handles the fine-tuning. You have a single interface for monitoring the status of each server.

One interface for everything

Provisioning, configuration, patches, and status are all managed centrally in Foreman—rather than in separate tools.

Servers in Minutes

Automated provisioning of bare-metal servers and VMs based on a template—instead of installing each machine manually.

Patch Management

Get a centralized view of patch statuses and roll them out in waves—no more flying blind when it comes to keeping your systems up to date.

Entire Life Cycle

From initial installation through operation to controlled decommissioning—all in one place.

Foreman + Ansible

Foreman handles provisioning and the lifecycle, while Ansible handles the fine-tuning—two tools, one seamless process.

All in one place

Consulting, setup, operation (MyEngineer), and training for NETWAYS—as open-source specialists.

The Problem

Without centralized management, every server installation is a manual process, the patch status remains unclear, and the lifecycle is fragmented across separate tools.

Server installation takes days

Setting up each machine manually is slow and inconsistent—and with every new system, the process starts all over again.

No one knows the condition

Which server has which patch status and which version? Without a centralized view, it remains a mere estimate—a risk to safety.

A Lifecycle Without a Common Thread

Provisioning, patching, and decommissioning are performed using separate tools and scripts—without a comprehensive overview.

How we work with you

Four steps, identical for every NETWAYS solution—from inventory to centrally managed server lifecycle during operation.

Step 1

Analysis & Concept

We assess the inventory, provisioning needs, and patch and compliance requirements, and define the lifecycle model.

→ A life cycle that fits your environment—from the first day to the last.

"
Step 2

Setup & Integration

We are setting up Foreman as a central hub—with provisioning templates, Ansible integration, and patch workflows.

→ A user interface covering everything from installation to patching.

"
Step 3

Commissioning & Provisioning

Go-live: New servers are automatically created based on a template, and patches are rolled out centrally and in a controlled manner.

→ Provisioning at the push of a button instead of days of manual work.

"
Step 4

Support & Operations

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

→ The server lifecycle remains under centralized control at all times.

The Life Cycle Under Control

From deployment to configuration to decommissioning—the four stages are interlinked.

Bare-Metal Provisioning

Deploy

Foreman automatically installs bare-metal servers and VMs based on templates—via PXE, images, and provisioning templates.

Result: New systems in minutes instead of hours.

Configuration

Configure

Immediately after provisioning, Ansible handles the fine-tuning—packages, services, and settings.

Result: Servers ready for use without any manual follow-up work.

Patch Management

Patching & Updating

Patch statuses are clearly visible, and updates can be managed and rolled out in waves.

Result: up-to-date, secure systems that operate without flying blind.

Server Lifecycle Management

Manage & Dismantle

From inventory to day-to-day operations to controlled decommissioning—everything is traceable.

Result: Every server remains in a known state until the very end.

What You’ll Achieve

Faster deployment, a complete overview, and controlled updates.

Deploy Faster

New servers are automatically provisioned in minutes rather than hours—based on a template and configured to be ready for use immediately.

A Complete Overview

An interface shows which server is in which state—including the version and patch status.

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.

Foreman

The central hub for provisioning and lifecycle management: initial installation, inventory, content views, and patch management—all in one place.

Ansible

Performs fine-tuning immediately after provisioning—agentless via SSH, reproducible using a playbook.

GitLab

Version controls templates and playbooks and executes them via CI—provisioning and configuration as code.

Icinga

Monitor the deployed systems from the very beginning—so that every server is under surveillance from day one.

We’ll integrate what you’re already using with

Foreman manages the lifecycle across many platforms and operating systems. A selection of what we typically connect.

Provisioning

  • PXE / Boot
  • Images
  • Bare Metal
  • Virtual Machines

Operating Systems

  • RHEL / CentOS
  • Debian / Ubuntu
  • SUSE
  • Windows

Operations & Quality

  • Icinga
  • Reporting
  • Compliance
  • MyEngineer

Platforms & Hypervisors

  • VMware
  • Proxmox
  • libvirt / KVM
  • Cloud

Configuration & Lifecycle

  • Ansible
  • Foreman
  • Content Views
  • Patch Workflows

Questions & Answers

Frequently Asked Questions About This Solution

What is provisioning?

2
3
Provisioning refers to the automated deployment of servers—from the initial installation of the operating system through basic configuration to the point where the server is ready for use. Instead of setting up each machine manually, new systems are created in a reproducible manner based on a template, for example via PXE boot or images.

What is Foreman?

2
3
Foreman is an open-source tool for managing the lifecycle of physical and virtual servers. It handles provisioning, inventory, configuration management, and patch management, and provides a centralized interface that displays the status of each system—from installation to decommissioning.

How do I automate provisioning?

2
3
By defining templates for installation and basic configuration and rolling them out using a tool like Foreman—via PXE boot or images for bare-metal servers and VMs. Ansible then handles the fine-tuning. NETWAYS sets up this workflow so that new servers can be created at the push of a button and in a reproducible manner.

Foreman vs. Ansible – What's the Difference?

2
3
Foreman covers provisioning and the lifecycle—that is, deployment, inventory, and patch management throughout the entire lifecycle. Ansible specializes in configuration management—that is, setting up and maintaining software on systems. The two complement each other: Foreman provides the infrastructure, and Ansible configures it.

What is patch management with Foreman?

2
3
Foreman provides a centralized view of the patch statuses of all systems and allows for the controlled rollout of updates—for example, first to test systems, then to production systems. This keeps servers up to date and secure without anyone having to monitor each host individually.

Is this also available as a managed service?

2
3
Yes. Upon request, NETWAYS will manage the operation of the provisioning and lifecycle platform—including maintenance and patching workflows—via MyEngineer. You use the central interface; we keep the underlying infrastructure up to date and available.

We look forward to your message






    captcha