All projects
Done · DPDK · VFIO · Ansible · Networking

DPDK / DPI - stable in production.

Production operation of a DPI/DPDK stack - NIC↔PCI mapping, VFIO binding, port/link diagnostics, and Ansible-driven server configs. Boring deploys = uptime.

Case study
01 · Problem

The DPDK stack crashed unpredictably.

NIC ↔ PCI ↔ VFIO bindings drifted between hosts. Manual config edits caused outages. Service startup was a 50/50 lottery on a fresh box.

02 · Approach

Deterministic bindings + Ansible.

Built a discipline: deterministic NIC↔PCI mapping per host, clean VFIO binding, port/link sanity checks before service start. Wrapped server config in Ansible - idempotent playbooks, no SSH-and-vim.

03 · Outcome

Uptime 99.92% → 99.97%.

Repeatable, reproducible deploys. Service startup time and false-fail rate dropped. Triage was compressed into a checklist any on-call can run at 3 AM.

Tech stack
DPDK VFIO-PCI Linux kernel networking Ansible Bash systemd
What I learned

DPDK ops is 80% hardware/PCI hygiene and 20% application. Make it boring with automation - boring is uptime.