AWS today closed out its first re:Invent keynote with a focus on edge computing. The company launched two smaller appliances for its Outposts service, which originally brought AWS as a managed service and appliance right into its customers’ existing data centers in the form of a large rack. Now, the company is launching these smaller versions so that its users can also deploy them in their stores or office locations. These appliances are fully managed by AWS and offer 64 cores of compute, 128GB of memory and 4TB of local NVMe storage.

In addition, the company expanded its set of Local Zones, which are basically small extensions of existing AWS regions that are more expensive to use but offer low-latency access in metro areas. This service launched in Los Angeles in 2019; starting today it’s also available in preview in Boston, Houston and Miami. Soon, it’ll expand to Atlanta, Chicago, Dallas, Denver, Kansas City, Las Vegas, Minneapolis, New York, Philadelphia, Phoenix, Portland and Seattle. Google, it’s worth noting, is doing something similar with its Mobile Edge Cloud.

The general idea here — and that’s not dissimilar from what Google, Microsoft and others are now doing — is to bring AWS to the edge and to do so in a variety of form factors.

As AWS CEO Andy Jassy rightly noted, AWS always believed that the vast majority of companies, “in the fullness of time” (Jassy’s favorite phrase from this keynote), would move to the cloud. Because of this, AWS focused on cloud services over hybrid capabilities early on. He argues that AWS watched others try and fail in building their hybrid offerings, in large part because what customers really wanted was to use the same control plane on all edge nodes and in the cloud. None of the existing solutions from other vendors, Jassy argues, got any traction (though AWS competitors would surely deny this) because of this.

The first result of that was VMware Cloud on AWS, which allowed customers to use the same VMware software and tools on AWS they were already familiar with. But at the end of the day, that was really about moving on-premises services to the cloud.

With Outposts, AWS launched a fully managed edge solution that can run AWS infrastructure in its customers’ data centers. It’s been an interesting journey for AWS, but the fact that the company closed out its keynote with this focus on hybrid — no matter how it wants to define it — shows that it now understands that there is clearly a need for this kind of service. The AWS way is to extend AWS into the edge — and I think most of its competitors will agree with that. Microsoft tried this early on with Azure Stack and really didn’t get a lot of traction, as far as I’m aware, but it has since retooled its efforts around Azure Arc. Google, meanwhile, is betting big on Anthos.

Western Digital’s composable OpenFlex flash storage system now supports Kubernetes storage, courtesy of Linbit’s LINSTOR software.

OpenFlex is a physical chassis, containing SSDs or disk drives, which is addressed as an NVMe target device. It’s basically an NVMe-oF JBOD (Just a bunch of drives) and needs additional software to link it to containerised environments.

Manfred Berger, WD’s senior manager for business development, platforms, said in a statement: “With Linbit’s LINSTOR software added to our OpenFlex offering, the software-defined-storage solution combines the advantages of SDS systems, Linux OS features and composable hardware so that organisations have the confidence they need in their Kubernetes environments.”

Philipp Reisner, Linbit CEO, said: “With the open-source LINSTOR we bridge the gap between the workload orchestrator (Kubernetes) and the efficient OpenFlex storage devices from Western Digital. In combination delivering high-performance block storage at a very attractive price point.”

LINSTOR is configuration management system for storage on Linux systems. The software use the Linux LVM tool to manage logical volumes and/or ZFS ZVOLs on a cluster of nodes. Linbit has developed a Distributed Replicated Block Device (DRBD) storage construct for Linux and LINSTOR uses this to provide block storage devices to users and applications.

LINSTOR sees WD’s OpenFlex Composable Infrastructure as an NVMe-accessed storage pool from which it can allocate space to DRBD. OpenFlex has a REST Open Composable API which is used by LINSTOR to do this.

That’s the downstream aspect sorted. On the upstream side there is a LINSTOR Operator to deliver DRBD capacity to Kubernetes. It installs DRBD in Kubernetes environments, thus linking OpenFlex and Kubernetes, and manages Kubernetes satellite and controller pods.