Running macOS at Datacenter Scale
Namespace operates MacBook Pros in datacenter racks as Mac compute infrastructure for customers developing iOS apps, which requires macOS. The company chose laptops over Mac Minis due to supply chain disruptions and staggered hardware releases—Minis ordered in January weren’t delivered until July, and the Mini line lagged months behind receiving M5 processors. Each MacBook connects to an IP KVM for remote management, external 10G Ethernet, and power cabling, with custom-made holders designed to manage heat dissipation.
Operational challenges appeared in unexpected places. HDMI cables proved significantly more unreliable than MagSafe connections; the team deployed specialized flexible variants and exhausted available market supply. FileVault encryption complicates unplanned reboots: password prompts appear on closed laptop screens but disappear from external KVM displays after 5 minutes. Although macOS Tahoe enables SSH-based FileVault unlock, this capability expires after 5 minutes on laptops. The workaround is fdesetup authrestart, which allows rebooting while keeping the disk unlocked. External USB network interfaces occasionally fail but can be revived by recreating the network service in macOS settings.
Namespace virtualizes Macs using Apple’s Virtualization framework, constrained to two guest VMs per physical machine. The platform launches macOS instances in seconds and deploys updated Xcode versions hours after Apple releases them. Incoming M5 and M6 Mac Minis and Studios offer simpler management with built-in 10Gb networking, automatic restart after power loss, and MDM-based OS provisioning.
Read the full article
Continue reading at Hacker News →This is an AI-generated summary. Read the original for the full story.