OpenKeel: the sovereign French Cloud solution of the inherent group, with a European reach Discover inherent

The project

Context: OpenStack

Fifteen years of history, a large community, a heavy code base.

OpenStack in a few dates

  1. 2010

    Launched by Rackspace and NASA: Swift and Nova

  2. 2012

    OpenStack Foundation created

  3. 2015-16

    Peak activity: contributors, companies, Summits

  4. 2020

    The foundation becomes the OpenInfra Foundation

  5. 2023

    End of alphabetical names: series 2023.1, 2023.2…

  6. 2025

    OpenInfra joins the Linux Foundation

  7. 2026.2

    Current series, OpenKeel's target

A release every six months since 2010; each service keeps its API compatible from one release to the next.

An open community that has narrowed

Governance

The “Four Opens”: open source, open design, open development, open community. A Technical Committee, a PTL per project.

Tooling

OpenDev: Gerrit review, Zuul CI, devstack and Tempest to test every change.

Users

Telecom operators, public and private clouds, research: very large fleets in production.

Trend

After the 2015-2016 peak, vendors withdrew; fewer contributors for as much code.

The weight of legacy code

OpenKeel's starting point: keep the contracts (API, database, messages) that give the ecosystem its value, and replace the implementation with Kubernetes-native Go.

Runtime

Python and eventlet

Monkey-patched green threads, the move away from eventlet still in progress; GIL and limited performance.

Dependencies

Stacked libraries

Dozens of oslo libraries, clients and drivers to keep in step.

Configuration

Sprawling configuration

Hundreds of options per service, many of them unused.

Deployment

Complex deployment

Kolla, OpenStack-Ansible, TripleO (discontinued): the tooling weighs as much as the cloud.

Life cycle

Painful upgrades

Schema migrations, versioned RPCs, a strict upgrade order.

Hosts

Agents on the hosts

libvirt, OVS agents, iSCSI: a data plane reinvented next to Kubernetes.