With eLxr, Wind River Brings Debian Linux to the Edge
Long-time embedded systems provider Wind River Software has launched an enterprise-grade Linux distribution aimed for a new generation of edge deployments.
Rather than upgrade the company’s Wind River Linux distribution, which has been for the past 20 years tailored for traditional embedded systems (notably telecommunications), Wind River engineers built a new distro to match emerging cloud native environments with heterogenous, computationally limited edge computing devices running in remotely placed devices.
The distro, called eLxr, will be based on Debian but will also include advanced features as over-the-air (OTA) updates, software bills of materials (SBOMs), edge processing, predictive maintenance and data aggregation. The distro is released under the MIT open source license.
And rather than overseeing the project itself, Wind River’s plan is to have eLxr be community driven.
“Edge-to-cloud” is how Wind River principal technologist Mark Asselstine described the goals of the project to The New Stack (TNS).
The distribution aims to cut down on the fragmentation of the edge computing market, where large organizations have collected countless software and hardware variants that all must be managed independently, and, as a result, not that efficiently. A single unified stack for both edge devices and the cloud servers that support them could simplify management considerably.
The idea behind eLxr was “how can we approach it differently so that you could have one supplier and one operating system that could cover both cases, from from the edge all the way into your servers,” Asselstine said.
Asselstine introduced the distribution last week at the DebConf in Busan, South Korea, in a technical presentation.
Origins of eLxr
eLxr sprang from another Wind River Linux Project, StarlingX, a cloud native Linux-based distribution. An OpenInfra Foundation Project, StarlingX has found a home in many large telecommunications providers, which use it to manage thousands of nodes on their 5G networks.
StarlingX was originally based on Red Hat‘s CentOS. But Red Hat changed that distribution to a streaming model, where updates are installed as soon as they are available.
StarlingX was not prepared to move to a streaming model, given the instability of rapid updates, so the decision was made to move the base to Debian.
The development team found that Debian would be a suitable base for running edge devices. Debian has been issuing stable releases for 30 years and was not controlled by a corporate entity with its own agenda.
After migrating StarlingX to Debian, Wind River’s dev team wanted a Linux distro for “edge-to-cloud” operations.
For Wind River, edge devices are not only switches, routers, multiplexors and other networking gear, but the whole expanse of industrial and retail embedded devices. This would include everything from point-of-sale machines to medical devices: Anything with internet connectivity and a bit more computational power than a bare-bones programmable logic circuit (PLC).
These edge systems have more constraints than a cloud server. They may be run in low-power environments, or be limited in CPU power or memory. Connectivity and bandwidth may be limited, which could truncate any window for applying security updates.
“Most binary Linux distributions aren’t necessarily solving for the problems with edge devices,” Asselstine said in his talk.
Another differentiator for eLxr is it will rely heavily on modern build and runtime tools, such as Docker and GitLab.
Asselstine hopes that such cloud native tooling may also bring in a set of younger set contributors. As TNS freelance reporter
Steven J. Vaughan-Nichols has pointed out elsewhere, open source has a graying issue with maintainers.
“We want to get young people involved in operating systems again,” Asselstine told TNS.
How eLxr Works
With a standard distribution like Debian, an image is installed on a device then configured for that particular environment by removing and adding the needed packages.
Because the package manager software must be installed locally, this approach does not work well for edge devices.
“When you’re deploying to an edge device, you’re not always going to have access to a package manager. Nor do you want to use a package manager to do updates,” Asselstine told TNS.
So eLxr takes the opposite approach: Developers create a manifest for building a preconfigured image, which then can be downloaded and installed.
eLxr uses OSTree to update packages as atomic commits. So, in your build system, you can commit a single package, such as systemd or libc, to be updated. “The manifest will let you include only what you need,” Asselstine said.
In the future, eLxr will have some sort of support for SBOMs although the team is still working out what this will entail. They are reviewing what work Debian has done. Their goal is to have a SBOM delivered when the user’s final image is created.
Building eLxr From Source
Wind River engineers were able to use the Yocto Project and Buildroot to assemble the distribution and to generate a software development kit (SDK) for a cross-platform toolchain.
The Yocto project, started by Wind River and Intel in 2011, can be thought of as a distribution builder, providing a way to users to build a custom image from source. It can even produce an SDK for the distro it generates.
Yocto was perfect for building operating systems for customized environments. The downside was that it requires a lot of work to build a distribution. eLxr can streamline that process significantly.
eLxr will have a “upstream first” release policy. It follows the Debian release cycle, with its releases expected to appear a few months after Debian’s.
Currently, eLxr is built on the most recent Debian “Bookworm” release, and when Debian releases the next version, “Trixie,” eLxr will follow with its own release within three to four months.
Core engineers will do their preparation work on the test releases of Debian, allowing them to contribute back to the Debian community with their features and fixes.
eLxr for the Community
Discussion is still underway for how to establish long-term and commercial support for eLxr.
Wind River is still working out how to build rLxr as a true community-led project, sorting out the details on things like governance and contributor models.
But overall, the idea is “Wind River doesn’t have to control the project in order for us to benefit from it,” Asselstine said.
