Platforms¶
Claugine starts here. A platform is an OpenNebula front end with a predefined type.
Types¶
| Type | What it is |
|---|---|
| mgmt | The site's management platform. It runs the provider's own services and network functions. |
| shared | Projects are created on it. |
| ext-managed | Claugine manages the platform itself (hosts, OpenNebula, networks), while its payload is managed by a third-party system. Formerly called portal. |
Platforms and sites¶
- A platform always belongs to a site.
- Platforms on different sites can be federated: a platform can span sites, with one front end and a zone per site. A secondary zone belongs to the front end of its primary.
Platform-wide resources¶
A platform has resources that, in OpenNebula terms, belong to the whole platform:
- networks: VLANs on the site's networks, or existing bridges;
- datastores. The platform-wide datastore types are file and backup, served by the front ends.
Clusters¶
A platform organizes its hosts into clusters.
- A host belongs to only one cluster.
- Every cluster must have datastores for VMs and images, served by the cluster's hosts.
- One VM datastore can be connected to several clusters, and so can an images datastore.
flowchart TB
site[Site] --> p["Platform<br/>OpenNebula front end"]
p --> fds["Platform datastores<br/>file, backup<br/>served by the front ends"]
p --> pn[Platform networks]
p --> c1[Cluster A]
p --> c2[Cluster B]
c1 --> h1[Hosts of A]
c2 --> h2[Hosts of B]
vms[("VMs datastore")] --- c1
vms --- c2
img[("Images datastore")] --- c1
img --- c2flowchart TB
site[Site] --> p["Platform<br/>OpenNebula front end"]
p --> fds["Platform datastores<br/>file, backup<br/>served by the front ends"]
p --> pn[Platform networks]
p --> c1[Cluster A]
p --> c2[Cluster B]
c1 --> h1[Hosts of A]
c2 --> h2[Hosts of B]
vms[("VMs datastore")] --- c1
vms --- c2
img[("Images datastore")] --- c1
img --- c2
Cluster kinds: mgmt (management), shared (projects are created on it), dedicated (one organization or project), edge (network functions), platform (managed by an external platform) and ext-managed. A project orders resources on a cluster; see Platform services.
How the portal works with a platform¶
- Mode: read-only (the portal reads the platform and writes only to its own test projects) or execution (the portal provisions projects on it).
- Network function image: the VyOS image the platform's VyOS VMs are made from, which the provider supplies (the shipped default name is VyOS Router 2026.03); see VyOS.
- State: planned (not installed), deployed or retired.
Read on: Platform and architecture, OpenNebula, VyOS.