We are excited to announce the release of Operos v0.2. Even though the change from 0.1 to 0.2 may seem numerically insignificant, it represents several huge milestones for Operos.

Open source

The first and most exciting change is that all of Operos is now open source under the Apache 2.0 license. In developing Operos, we have made extensive use of open source technology - integrating Arch Linux, Kuberentes, Ceph, iPXE, and a host of other components. So it only made sense to us to release our last year’s work as free (as in “free speech”) software.

We encourage anyone looking for a complete, open-source infrastructure and application management stack for commodity hardware to download and try Operos, or check out the source on GitHub.

Preparation for system updates

Another important change in this release is the significant amount of progress we’ve made towards our vision of atomic and stateless system upgrades. From the ground up, we have redesigned how the OS is installed and delivered on the controller and worker machines. Rather than trying to automate a complex process through OS-native packaging or configuration management systems like Puppet or Ansible, the Operos OS images for all nodes are pre-created at build- time. At boot time, these static images are simply mounted as the root filesystem. Any local machine state is kept on top via OverlayFS or through additional volume mounts.

This approach has numerous benefits:

  • Smaller installer ISO (2.6 GB before vs 1.7 GB now);
  • Atomic OS images that can be quickly swapped out during upgrades - or rolled back, in case something goes wrong;
  • Data and configuration is kept entirely separate from the OS state;
  • Shorter build time.

Component upgrades

Among the other changes that made it into this release are upgrades to major components: