Chris Abel

Overview

Chris Abel is a storage engineer at Google who represents Google's requirements in the OCP data center storage specification effort. His contributions at the October 2025 OCP Global Summit focused on two interconnected themes: firmware convergence at hyperscale and the L.O.C.K. open-security initiative.

Google's core motivation for participating in the OCP spec is improving quality at scale while breaking down the siloing of per-vendor firmware requirements. Abel described the goal as coordinating each hyperscaler's requirements so the industry converges on a single firmware — or at minimum something approximating one — that all major customers can accept, rather than each operator maintaining bespoke qualification matrices.

Quality-of-service is central to Google's requirements. Abel identified the NVMe QoS Technical Proposal as critical for providing isolation between users when multiple tenants share storage devices. OCP latency monitoring has been part of the spec since version 2.0; spec 2.7 adds minor host-initiated telemetry updates on top of that foundation.

On security, Abel argued that opacity is the core problem: when an exploit is discovered in one SSD vendor, hyperscalers are compelled by the lack of visibility into firmware internals to assume all other vendors carry similar vulnerabilities. The implication is that an open, verifiable secure base layer is table stakes for trusting any storage device at cloud scale. He reported concrete progress on OCP L.O.C.K. as of October 2025: a L.O.C.K. 1.0 specification has been formally contributed, Caliptra 2.1 has been released, the TCG Opal MEK MP host interface feature set is ready for public dissemination, and SSD implementation is the designated next step.