Intel TDX confidential VMs run on OpenMetal dedicated bare metal hardware today, available on on XL v5, with OpenStack Nova orchestration slated for after Hibiscus.
Tag: Hardware Editorial
A first-party FP4 checkpoint moves GPU selection from memory capacity to native tensor-core format support, and inverts the usual verdict. Based on the Inkling-Small.
On OpenMetal v5, one memory decision buys Intel TDX eligibility, full DDR5-6400 bandwidth, and SGX enclave headroom. XL v5 ships ready.
Prefill is compute-bound, decode is memory-bandwidth-bound. Why splitting inference into two purpose-fit GPU pools beats one uniform fleet.
After weights load, the HBM left over is your KV-cache budget. Why the H200’s 141GB buys more context and concurrency than a 94GB H100.
Map MongoDB, Redis, Kafka, ClickHouse, and Kubernetes workers to OpenMetal SKUs by the resource each role saturates, then size the failure domain.
An ordered Day-2 playbook for a single-tenant H200: full root and IPMI, owning the CUDA stack, boot-data isolation, and a node-bounded blast radius.
The v5 generation can be told as a cores-and-clocks story, but a significant change is bandwidth: the private fabric doubled to 40 Gbps, memory moved to DDR5-6400, and the lane budget grew to 88 PCIe 5.0 lanes.
All-NVMe OSDs, an isolated boot pool, a clean lane budget, and identical nodes: how OpenMetal’s v5 hardware makes Ceph behave predictably instead of needing tuning.