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

The project

Vision and principles

OpenKeel, the sovereign French Cloud solution of the inherent group, with a European reach: a Cloud built on Cloud Native, open source technologies, natively multi-tenant, designed to be SecNumCloud-ready, with REST APIs fully compatible with OpenStack's.

Sovereign, French, with a European reach

OpenKeel is developed by the inherent group, a French IT group expert in AI, cloud, cybersecurity and connectivity for businesses and public bodies.

Its sovereignty rests on open source code, distributed under the Apache License 2.0, on open APIs shared with the OpenStack ecosystem, and on a deployment on the customer's own Kubernetes clusters, in France and in Europe.

  • A solution of the inherent group
  • Open source software and open standards
  • Distributed under the Apache License 2.0
  • Data and operations under the customer's control

A Cloud Native solution

OpenKeel takes the OpenStack modules (Keystone, Nova, Neutron, Cinder, Glance, Manila…) and rewrites them in Go on top of Cloud Native technologies: Kubernetes, OVN, KubeVirt, CSI, Rook-Ceph, Medik8s, ExternalDNS.

The control plane (API, scheduling, database, bus) is rewritten; the data plane is handed to proven Kubernetes projects. OpenKeel deploys on Kubernetes clusters with the okadm CLI.

  • Static Go binaries, distroless images without a shell
  • One Helm chart per service, an umbrella chart
  • Lab (kind) or production (Talos) deployment

Natively multi-tenant

Tenant isolation comes from the OpenStack APIs (domains, projects, roles, quotas) and from the data plane: OVN networks per tenant, Neutron ports with port_security, NFS-Ganesha gateways inside the tenant network, one Kata microVM per container.

Tenants have no Kubernetes access: only the OpenKeel services create the objects (VirtualMachines, Pods, PVCs, NetworkAttachmentDefinitions).

Designed to be SecNumCloud-ready

SecNumCloud (ANSSI, framework 3.2) qualifies a Cloud service and the provider who runs it: organisation, people, premises and operations as much as technique. No software can be qualified on its own.

OpenKeel aims to be a SecNumCloud-ready foundation: encrypted flows, an audit trail on every API, tenant isolation, strong authentication and key management, with the documentation that lets the provider prove compliance during the audit.

  • Mechanisms built in, evidence in the code
  • What is compliant and what is left to do, published
  • A path to qualification: matrix, pre-audit, PASSI penetration test

Guiding principles

OpenStack API

100% compatible with the Python APIs

MariaDB

100% compatible with the data model

RabbitMQ

100% compatible with the messages

e2e tests

Replay the OpenStack test suites

Existing building blocks

CSI, NFS-Ganesha, OVN, KubeVirt

First step: specify, generate, test

  1. 01

    151 upstream projects

    OpenStack repositories fetched and analysed

  2. 02

    36 reverse-specs

    Precise specifications of the components

  3. 03

    27 Go projects

    Starting with Placement and Keystone

  4. 04

    Skill and e2e tests

    Specification enriched, e2e tests integrated

Figures from the presentation; the workspace currently holds 38 reverse-spec folders and 25 Go modules.

OpenKeel on one page

  • 24components presented on this site
  • 38reverse-specs of the upstream repositories
  • 3chained Claude skills: spec, diagram, code