Onur Baydaş

Technology, AI & Systems Radar: October 15, 2026

Thu, 15 Oct 2026 19:55:26 +0300

Daily intelligence briefing covering frontier AI architectures, global software ecosystem breakthroughs, critical CVE alerts, silicon innovations, and open-source systems.

Systems & Security Radar: October 14, 2026

Wed, 14 Oct 2026 15:34:11 +0300

Daily operational intelligence covering Linux kernel advancements, critical CVE advisories, enterprise storage, and infrastructure architecture.

One User, Two UIDs: NFSv4, Kerberos, and Docker on a Domain-Joined TrueNAS

Tue, 13 Oct 2026 00:00:00 +0000

SSSD and TrueNAS gave the same AD user different UIDs. How that showed up as nobody, Permission denied, root:root 755, and "I have no name!", and how we aligned them.

Docker Authorization with OPA: The Silent Fail-Open and Other Production Lessons

Mon, 12 Oct 2026 00:00:00 +0000

The plugin looks enabled, the policy is correct, yet Docker allows everything. A silent security gap I hit with opa-docker-authz in production, and its lessons.

About

Mon, 01 Jan 0001 00:00:00 +0000

I’m Onur Baydaş, a systems and infrastructure engineer based in Turkey. Since 2024 I’ve been designing, deploying, running, and troubleshooting on-premises infrastructure: the kind of environments where there is no managed cloud service to fall back on and every layer, from hardware and storage to identity and scheduling, is your responsibility.

Currently

Scheduling, partitioning, and isolation on multi-user GPU infrastructure
Operating virtualization and software-defined storage clusters
Backup, monitoring, and high availability
Technical writing in Turkish and English, drawn from production experience

What I work on

Virtualization and storage: Clustered virtualization, software-defined storage, hyperconverged infrastructure (HCI), enterprise NAS and ZFS-based storage.
GPU infrastructure: GPU servers and clusters for AI and research workloads, GPU partitioning and virtual GPUs, HPC job scheduling, stress testing, and driver/framework compatibility.
Multi-user platforms: Shared Linux workstations: user isolation, resource management, container access control, and day-to-day operations.
Container security: Restricting the container runtime on shared machines, policy-as-code authorization, and cross-user isolation gaps.
Identity and access: Directory services and identity management, Kerberos authentication, network home directories, PAM integration.
Backup and DR: Hyperconverged backup, deduplication backup appliances, backup monitoring and reporting.
High availability: Cluster resource management, block-level replication, active/passive service failover.
Observability: Metrics, centralized logging, alerting, and dashboards; centralized syslog collection.
Hardware and lifecycle: Rack server deployment, out-of-band management (BMC), RAID controller and disk failure analysis, vendor support processes.
Network and security: Next-generation firewall management, segmentation, management network design.

What I write about

I write about problems I actually hit in production: the silent failures, the misleading documentation, and what the source code says when the docs don’t. Every post is based on a real incident, tested on a live system, and backed by links to the source.

Systems & Security Radar

Mon, 01 Jan 0001 00:00:00 +0000

Live technical intelligence stream aggregating Linux kernel, CVE exploits, infrastructure architectures, and AI compute across 25+ authorities.