OpenKeel: the sovereign French Cloud solution of the inherent group, with a European reach Discover inherent
Components · Compute and capacity
Instances run as KubeVirt VirtualMachines; conductor with the scheduler in process, one agent per node.
OpenKeel implementation in Go of OpenStack nova (the compute API, its conductor with the scheduler in process, and a per-node compute agent), with KubeVirt as hypervisor and Ironic for bare-metal flavors, generated from the reverse-specification of branch stable/2026.2 by the generate-go-from-spec skill. It replaces the Python service without its clients noticing: same routes, status codes, error bodies, microversions and policies. What is reproduced and what differs is in docs/CONFORMANCE.md; the security checklist is in docs/SECURITY.md.
github.com/openkeel/openkeel-novanova-api (API on port 8774, health and metrics on 9090), nova-conductor (consumes the conductor queue on RabbitMQ, schedules through Placement, drives KubeVirt and Ironic), nova-compute-agent (DaemonSet on compute nodes: service record, heartbeat, hypervisor row, Placement inventory), nova-ironic-agent (Deployment, one replica active behind a Lease: the same for each Ironic node, rendered when peers.ironic_endpoint is set), nova-console-proxy (Deployment, consoleProxy.enabled: noVNC and console websockets on port 6080, see Consoles below)nova-kubevirt.md (flavor → instancetype/preference, VirtualMachine per server in os-<project>), bare-metal flavors (resources:CUSTOM_BAREMETAL_*=1) to openkeel-ironic, node placement per openkeel-docs/NODE-PLACEMENT.md of the workspaceExcerpt from openkeel-nova/README.md (in English).
273 operations of the original REST API (routes and body actions), and their state in OpenKeel.
The API-sample exchanges of Python Nova are replayed against the Go service, concurrency is tested on Galera, and real KubeVirt guests are booted and drained on the lab.
Each recorded API-sample exchange of Python Nova gives the same status and body from the Go service, on a fresh database per file.
make e2e (1233 files), on go-mysql-server and on MariaDB 11.4 with E2E_MYSQL_DSN; report in test/e2e/report.json.
Latest result 1957 / 2590 identical on both engines; remaining differences are mainly unimplemented APIs (501) and tests that stub the database.
Source: openkeel-nova/docs/CONFORMANCE.md
Router pipeline, validation messages, the 214 policy rules, state map, scheduler resources and flavor-to-KubeVirt conversion behave as specified.
make test; flavor vectors in internal/driver/kubevirt/flavor_test.go.
Latest result Pass; flavor to KubeVirt vectors 6 / 6.
Source: openkeel-nova/docs/CONFORMANCE.md
Quotas, unique names and concurrent actions hold when requests arrive through three Galera nodes at once.
test/galera on a 3-node cluster: concurrent boots, key pairs, server groups, same-name creations and stops.
Latest result Pass, 3 runs out of 3: exactly 10 servers for a quota of 10 out of 30 boots, no 5xx.
Source: openkeel-nova/docs/CONFORMANCE.md
POST /servers with Neutron ports boots real guests that get their Neutron addresses, are isolated between projects and survive live migration.
Disposable kind cluster, openkeel-lab profile dataplane: real OVN, KubeVirt v1.9.1, cirros guests, real Glance, Placement and Neutron.
Latest result Pass (2026-10-31); live migration through the conductor on a local-path disk is refused by KubeVirt and covered by unit tests only.
Source: openkeel-nova/docs/CONFORMANCE.md
A drain live-migrates the guest, and Nova adopts the migration: host, port binding, OVN chassis and Placement allocation follow.
openkeel-lab/scripts/drain-test.sh on the dataplane lab, with two servers created by POST /servers.
Latest result Pass (2026-10-31); a peer lost 1 ping out of 55. No shared disk migrated, no node fully emptied.
Source: openkeel-nova/docs/CONFORMANCE.md
The upstream Tempest compute API tests against a deployed Nova.
Needs a kind cluster with KubeVirt, CDI, Longhorn and the OpenKeel peers.
Latest result Not run.
Source: openkeel-nova/docs/CONFORMANCE.md
Nova keeps its API and scheduling model but hands the hypervisor to KubeVirt, which removes cells, per-host nova-compute services and the deprecated proxy APIs.
A Kubernetes-native deployment runs one cell: one schema holds the tables of nova_api and the cell database, and the instance row is written at once.
API-visible concepts (instance mappings, request specs, BUILD and ERROR states with faults) are kept, so clients see the same server lifecycle.
Source: openkeel-nova/docs/CONFORMANCE.md
Taken over by KubeVirt
KubeVirt runs the guests cluster-wide; the conductor drives it through one RabbitMQ quorum queue and the scheduler is a library of the conductor. A per-node agent only reports resources.
Boot, stop, resize, live migration and drain work through KubeVirt; the libvirt, VMware and Hyper-V option groups disappear with the drivers.
Source: openkeel-nova/docs/CONFORMANCE.md
The proxies to Glance, Cinder and Neutron (images, os-volumes, os-snapshots, os-networks, os-floating-ips, os-security-groups, os-hosts, os-baremetal-nodes) are deprecated upstream.
These routes answer 501. Current clients, including ok and Skyline, call Glance, Cinder and Neutron directly, which OpenKeel provides.
Source: openkeel-nova/docs/PLAN.md
Taken over by KubeVirt
KubeVirt has no save of guest memory to disk.
suspend is accepted but stops the VM: the guest's memory state is lost and it boots again on resume. Disks and data are kept.
Source: openkeel-nova/docs/CONFORMANCE.md
Taken over by OVN CNI
KubeVirt starts the guest once the CNI plugin has seen OVN program its ports; Nova no longer holds a paused guest waiting for the event.
The server stays BUILD until Neutron reports its ports ACTIVE. The event is still accepted, so Neutron is unchanged and a lost event costs nothing.
Source: openkeel-nova/docs/CONFORMANCE.md
Only what was left out by design is listed here; the work not done yet is in the Known gaps of the module's docs/CONFORMANCE.md. Every module
Service view generated by the diagram skill from the OpenKeel model.
Full screen| From | To | Protocol | What |
|---|---|---|---|
| Skyline | Nova API | REST API | aggregated lists |
| Nova API | Placement | REST API | usages, quotas |
| Nova API | Glance | REST API | image metadata |
| Nova API | Neutron server | REST API | ports |
| Nova API | Cinder API | REST API | volume attach |
| Nova API | Barbican | REST API | encryption keys |
| Neutron server | Nova API | REST API | network-vif-plugged |
| Cinder API | Nova API | REST API | volume events |
| Masakari engine + monitors | Nova API | REST API | server state, host disable |
| Nova API | Nova conductor + scheduler | RabbitMQ | RPC build/resize |
| Nova conductor + scheduler | Nova compute agent | RabbitMQ | RPC |
| Nova conductor + scheduler | Placement | REST API | allocation candidates, claims |
| Nova compute agent | Placement | REST API | inventory, traits |
| Nova conductor + scheduler | KubeVirt | Kubernetes API | VirtualMachine, Instancetype, Preference |
| Nova console proxy | KubeVirt | Kubernetes API | VNC and serial websockets, console log |
| Nova API | Nova console proxy | REST API | console log, with a token |
| Nova compute agent | Kubernetes API server | Kubernetes API | watch node allocatable |
| Nova conductor + scheduler | Ironic API | REST API | bare metal flavors: provision nodes |
| Nova compute agent | Ironic API | REST API | nodes → Placement inventory (planned) |
| Heat engine | Nova API | REST API | OS::Nova::* |
| EC2 API | Nova API | REST API | instances |
| Nova conductor + scheduler | CDI | Kubernetes API | root DataVolume: clone of the image PVC |
Branch stable-2026.2 · 17 files
Read the reverse-specResource inventories and allocations; the first component rewritten in Go.
Containers as a Service: one Pod per container, isolated in its own Kata microVM, with its Neutron port as its only network.
Instance high availability; node health from Node Healthcheck and Self Node Remediation.
Bare metal: stays upstream Python, packaged in an OpenKeel chart; too many hardware configurations to test.