The technology behind the platform
THE COMPONENTS
What the platform is built from
Five components, all open source, all replaceable. Click through them.
OpenStack with a standard API in every environment
OpenStack provides the API, scheduler and orchestration, with state and metadata in MariaDB. The standard API means anything that speaks OpenStack works without modification: Terraform, Ansible and your existing tooling.
Stateless nodes, reinstalled on reboot
The compute nodes run a read-only OS and are provisioned over PXE. A reboot is a reinstallation: no configuration drift, no local state to lose, and a minimal attack surface on the individual node. Faults are handled by replacement, not troubleshooting.
Distributed Ceph storage
VM disks and data sit in distributed Ceph storage, with three copies spread across separate nodes by default. A disk or node can fail without data loss.
Distributed routing on a closed optical network
EVPN/BGP distributes routing without central points of failure, and transport runs over dark fibre between locations, bypassing the internet. The full network architecture is described on the Cloud Connect page.
Two independent ways into the platform
The Edora Cloud Console is the primary entry point – Edora’s own console, with visibility across locations and local autonomy at each one. Alongside it sits full programmatic access via API, CLI and Terraform. There is always a way in, even if the console is unavailable.
PRINCIPLES
Four choices that explain the rest
No closed layers
Every component is open source. An exit is always technically real, and that also disciplines Edora as a supplier: the platform has to be good enough that you stay by choice.
Stateless by design
Compute nodes carry no state. Replacement instead of troubleshooting, no maintenance windows at node level, and a read-only OS as a security property.
API-first
The portal uses the same APIs as your automation. There is no function that can only be reached by clicking, and therefore no manual process that cannot be automated away.
A separate network per datacentre
Each datacentre has its own network fabric, and no Layer 2 network is stretched between locations. A fault in one place does not spread to the others.
WHERE TO NEXT
The technology in context
The network beneath the platform
Cloud Connect: the closed N×100G fibre network that ties the locations together, bypassing the internet.
The same stack behind your own walls
EU Cloud in a Box: the entire platform delivered and operated in your own datacentre.