Google brings futuristic Linux software CoreOS onto its cloud

A container-based operating system on a virtualized cloud on a container-based distributed system = M.C. Escher's cloud


Fans of new Linux operating system "CoreOS" can now run the lightweight tech on Google's main cloud service.

This means developers who want a Linux OS that takes up just 168MB of RAM, runs all of its applications within containers, and is designed for marshaling mammoth clusters of computers, can now do so on top of Google's cloud.

"In the next few days, CoreOS will become available as a default image type in the GCE control panel, making running your first CoreOS cluster on GCE an easy, browser-based experience," wrote CoreOS's chief technology officer Brandon Philips in a blog post. "CoreOS is an ideal host for distributed systems and Google Compute Engine is a perfect base for CoreOS clusters."

CoreOS is built around three key technologies: etcd, a distributed key-value store that helps tie clusters of CoreOS machines together; Docker, which is used to package up apps and run them as containers while automatically configuring the network; and Linux mainstay systemd, which helps developers command a cluster of CoreOS machines as though they are one system.

The CoreOS team has done some work to integrate the OS with the capabilities of Google's cloud platform, making it easier for developers to pair apps on the lightweight OS with some of the advanced services provided by Google's cloud.

"CoreOS integrates easily with Google load balancers and replica pools to easily scale your applications across regions and zones," Philips explains in a guest Google blog post. "Using replica groups with CoreOS is easy; configure the project-level metadata to include a discovery URL and add as many machines as you need. CoreOS will automatically cluster new machines and fleet will begin utilizing them. If a single machine requires more specific configuration, additional cloud-config parameters can be specified during boot."

"Running on Compute Engine allows you to connect your front-end and back-end services running on CoreOS to a fully managed Cloud Datastore or Cloud SQL database," he explaines. "Applications that store user-generated content on Google Cloud Storage can easily start worker instances on the CoreOS cluster to process items as they are uploaded."

Since Google's (virtualized) cloud is itself built on top of Linux containerization, this means developers will enter into the paradoxical situation of running a container-based OS on a hypervisor on top of a container. However, Google product manager Navneet Joneja assures El Reg that "virtualization has gotten really good, the performance overhead tends to be minimal. Everything we've heard is [CoreOS] performance is really good on Compute Engine."

Most of the work for this support was done by the CoreOS team, Joneja said, before noting that there's "a good overlap" between CoreOS and the Google Cloud's capabilities and methods of doing things.

From our perspective, it's an intriguing partnership, and highlights that though CoreOS is a young technology it seems to be squinting at a software future that the rest of us can't quite see, yet. ®

Similar topics


Other stories you might like

  • Google Pixel 6, 6 Pro Android 12 smartphone launch marred by shopping cart crashes

    Chocolate Factory talks up Tensor mobile SoC, Titan M2 security chip ... for those who can get them

    Google held a virtual event on Tuesday to introduce its latest Android phones, the Pixel 6 and 6 Pro, which are based on a Google-designed Tensor system-on-a-chip (SoC).

    "We're getting the most out of leading edge hardware and software, and AI," said Rick Osterloh, SVP of devices and services at Google. "The brains of our new Pixel lineup is Google Tensor, a mobile system on a chip that we designed specifically around our ambient computing vision and Google's work in AI."

    This latest Tensor SoC has dual Arm Cortex-X1 CPU cores running at 2.8GHz to handle application threads that need a lot of oomph, two Cortex-A76 cores at 2.25GHz for more modest workloads, and four 1.8GHz workhorse Cortex-A55 cores for lighter, less-energy-intensive tasks.

    Continue reading
  • BlackMatter ransomware gang will target agriculture for its next harvest – Uncle Sam

    What was that about hackable tractors?

    The US CISA cybersecurity agency has warned that the Darkside ransomware gang, aka BlackMatter, has been targeting American food and agriculture businesses – and urges security pros to be on the lookout for indicators of compromise.

    Well known in Western infosec circles for causing the shutdown of the US Colonial Pipeline, Darkside's apparent rebranding as BlackMatter after promising to go away for good in the wake of the pipeline hack hasn't slowed their criminal extortion down at all.

    "Ransomware attacks against critical infrastructure entities could directly affect consumer access to critical infrastructure services; therefore, CISA, the FBI, and NSA urge all organizations, including critical infrastructure organizations, to implement the recommendations listed in the Mitigations section of this joint advisory," said the agencies in an alert published on the CISA website.

    Continue reading
  • It's heeere: Node.js 17 is out – but not for production use, says dev team

    EcmaScript 6 modules will not stop growing use of Node, claims chair of Technical Steering Committee

    Node.js 17 is out, loaded with OpenSSL 3 and other new features, but it is not intended for use in production – and the promotion for Node.js 16 to an LTS release, expected soon, may be more important to most developers.

    The release cycle is based on six-monthly major versions, with only the even numbers becoming LTS (long term support) editions. The rule is that a new even-numbered release becomes LTS six months later. All releases get six months of support. This means that Node.js 17 is primarily for testing and experimentation, but also that Node.js 16 (released in April) is about to become LTS. New features in 16 included version 9.0 of the V8 JavaScript engine and prebuilt Apple silicon binaries.

    "We put together the LTS release process almost five years ago, it works quite well in that we're balancing [the fact] that some people want the latest, others prefer to have things be stable… when we go LTS," Red Hat's Michael Dawson, chair of the Node.js Technical Steering Committee, told The Register.

    Continue reading

Biting the hand that feeds IT © 1998–2021