Virtualization
The separation of hardware, operating system, and application is now at the core of every modern infrastructure. I plan, implement, and operate virtualization and container platforms that use resources efficiently, isolate services, and enable automation of operations and scaling. I combine classic virtualization with KVM/Proxmox and container-based orchestration with Docker and Kubernetes—entirely on an open-source basis and without proprietary licensing models.
With KubeVirt, I connect both worlds: virtual machines run directly in Kubernetes clusters and can be managed, orchestrated, and monitored there together with containers. This creates a unified platform for virtual and containerized workloads that can be consistently controlled via Ansible, GitOps, and CI/CD.
My approach: Virtualization creates stability and compatibility, while containerization brings flexibility and speed. Together, they form the basis for automated, reproducible, and scalable IT landscapes.
Virtual machines
(KVM, Proxmox VE)
I rely on Linux-based virtualization with KVM (QEMU), both via Proxmox VE and directly via libvirt and virsh—with container-based orchestration via Docker and Kubernetes.
This results in high-performance, highly available systems that can be managed granularly and fully automated.
- KVM hosts with CPU pinning, NUMA tuning, and multipath storage
- Proxmox clusters with Ceph or ZFS backends
- Ansible provisioning and templated VM deployments
- Snapshot, backup, and live migration concepts
- Integration into monitoring and access control (SSSD, LDAP)
Containerization (Docker)
I develop and operate container-based environments for applications, databases, and microservices.
Containers enable reproducible builds and easy maintenance across development, test, and production systems.
- Docker-based service stacks (PostgreSQL, NGINX, Jenkins, etc.)
- Versioned Compose files and automated build pipelines
- Resource optimization (CPU limits, cgroups, volumes)
- Network and security isolation within container networks
Kubernetes & Orchestration
For scalable, fault-tolerant systems, I rely on Kubernetes—from cluster provisioning to Helm and Kustomize deployments to GitOps workflows.
- Cluster setup with Kubespray (Ansible-based)
- Deployment with Helm, Kustomize, Argo CD
- Security with OPA/Gatekeeper, RBAC, and network policies
- Integration of persistent volumes (Longhorn, Ceph CSI)
- Monitoring and logging with Prometheus and Grafana
Trainings
You can find specific trainings and current topics in the Comelio GmbH training catalog.
Available in-house at your company, as a webinar, or as an open training—designed to meet different requirements.
Self-hosting & Platform operation
I also operate complex infrastructures entirely on my own—from physical hardware to virtualization and container orchestration to productive applications. Self-hosting enables maximum control, transparency, and independence from external cloud providers. I combine KVM clusters, Kubernetes environments, and Docker stacks to create modular, maintainable system landscapes that serve both training and production purposes.
- Setup and operation of own data center and lab infrastructures (KVM, Proxmox, Kubernetes)
- Provision of isolated training and test environments via Apache Guacamole
- Operation of productive container stacks: Mailcow, Bookstack, OpenProject, OpenCloud, OpenTalk, etc.
- Integration into central services: DNS, VPN, backup, authentication (LDAP/SSSD)
- Monitoring, documentation, and automation with Prometheus, Grafana, and Bookstack
- Use of ChatGPT/Gemini for documentation and process support
OpenStack Integration
I use OpenStack as an orchestration layer when virtualization and containerization need to be combined in large infrastructures.
- Nova (compute), Neutron (network), Cinder (block storage) with Ceph backends
- Heat and Magnum for orchestration (Kubernetes-on-OpenStack)
- Automation and provisioning via Ansible and Python scripts
Automation & CI/CD
I transform virtualization and container management into fully automated workflows.
This creates infrastructure-wide CI/CD pipelines with clear roles and version control.
- GitLab CI/CD and Jenkins integration
- Automated builds, tests, and rollouts
- Automatic validation of templates and playbooks
- Documentation in Markdown and Bookstack
Frequently asked questions about Virtualization
In this FAQ, you will find the topics that come up most frequently in consultations and training sessions. Each answer is kept brief and refers to further content where necessary. Can’t find your question? Feel free to contact me.
Why is the separation of hardware, operating system, and applications so important today?
Decoupling these layers creates flexibility, reliability, and better resource utilization. Systems can be operated, maintained, and scaled independently of each other without being tied to specific hardware or individual platforms.
What role do containers play in modern platform architectures?
Containers enable applications to be deployed in a standardized, reproducible manner, independent of the environment. They accelerate development and deployment processes and are a central building block for microservices, automation, and continuous delivery.
Do companies have to choose between virtualization and containerization?
No. In practice, both approaches complement each other. Virtual machines provide stability, compatibility, and clear demarcation, while containers deliver flexibility and speed. Modern platforms combine both technologies in a common architecture.
What are the advantages of a unified platform for infrastructure and applications?
A consolidated platform reduces complexity, simplifies operations, and enables end-to-end automation. Workflows, security mechanisms, and monitoring can be implemented centrally, which increases transparency, stability, and scalability.