Skip to content

Platform and architecture

This page describes how the platform is built, in general terms. It doesn't name equipment models, addresses or other internal details.

Software

OpenNebula The cloud management platform: virtual machines, images, networks, quotas, multi-VM services (OneFlow) and the FireEdge web console. Claugine works with the current release of OpenNebula: it reads the version of each platform and shows it, and does not require, check or pin a particular one.
Host OS + KVM The hypervisor hosts run KVM on the host operating system Claugine installs; Claugine records each host and reads what it has.
VyOS All network functions are VyOS routers running as VMs, made from one VyOS image the provider supplies; Claugine works with the current VyOS release: project gateways, internet and corporate edges, route reflectors and L2 channel ends.
Claugine portal Self-service and operations: organizations, projects, approvals, deployment and changes, users and roles, and the record of resources and addresses.

Hardware

  • Compute: current-generation server CPUs with many cores and large memory. GPU servers have the GPUs passed through to the VM whole (PCI passthrough), never shared or overcommitted.
  • Storage: fast flash storage for VM disks and images, reached over NFS or iSCSI, plus local disks where that fits better. Backups are kept on separate storage.
  • Network: redundant switching with VLANs for the infrastructure and VXLAN/EVPN overlays for project networks. Routes are exchanged with BGP through route reflectors.

Structure

Site A data center: its hosts, storage systems, networks and IP subnets (the public and corporate address ranges projects get their addresses from).
Platform An OpenNebula installation at a site. A management platform runs the provider's own services and network functions. Shared platforms host the projects. A platform can span sites, with one front end and a zone per site.
Cluster A group of hosts of a platform with their datastores and networks. A project orders resources on a cluster. Kinds: management, shared (projects), dedicated (one organization or project), edge (network functions), ext-managed, and clusters managed by an external platform.
Datastore Storage of a platform on a storage volume: VM disks, images, files or backups.

Network design

Each project's traffic goes through two routers:

  • The project gateway (igw) is the project's own VM: advanced (VyOS, the default), native (the OpenNebula Service Virtual Router) or the project's own router. It routes the project's private networks, translates their addresses (SNAT) to the public address, and carries extra public networks. The project administers it.
  • The provider edge (egw) belongs to the provider. It limits bandwidth to what was ordered, lets only the project's own public addresses pass, and announces them to the internet through the exchange network.

Corporate projects connect to the corporate network through a corporate edge (cgw) in the same way; a project has the internet or the corporate network, never both. An L2 channel bridges a VLAN at the client's site into a project network over the provider's network. The portal assigns all addresses from the site's IP subnets; the customer chooses only the prefix sizes. Route reflectors spread routes inside each site. All provider routers are managed only from a separate management network.