Data flows and structures¶
This section describes every object Claugine works with, the terms used for them, how the data is structured and how the components interact.
Where the data lives¶
| Data | Defined by | Lives in |
|---|---|---|
| Infrastructure: sites, IP subnets, server profiles, hosts, storage, networks, platforms, clusters, core services | resource managers and support engineers | portal records, edited only in the portal |
| Secrets | the same people | portal records, encrypted; other records refer to them by key |
| Organizations, projects, orders, resource records, addresses | customers and staff, through the portal | the portal database: the desired state |
| What OpenNebula holds | the platforms | read-only by the Platforms timer (every 30 minutes by default): the actual state |
How the components interact¶
flowchart LR
people["Customers and staff"] -->|requests, approvals| portal["Portal<br/>desired state"]
portal -->|deploys and changes| one["OpenNebula platforms<br/>actual state"]
portal -->|configures over ssh| nf["Network functions<br/>VyOS routers"]
one -->|read-only by the Platforms timer, every 30 min| portal
portal -->|emergency copy in group metadata| oneflowchart LR
people["Customers and staff"] -->|requests, approvals| portal["Portal<br/>desired state"]
portal -->|deploys and changes| one["OpenNebula platforms<br/>actual state"]
portal -->|configures over ssh| nf["Network functions<br/>VyOS routers"]
one -->|read-only by the Platforms timer, every 30 min| portal
portal -->|emergency copy in group metadata| one
- The database is the desired state and OpenNebula is the actual state. The portal compares them and shows every difference.
- Nothing is deleted from the database: rows are versioned or blocked.
- Each project's OpenNebula group carries an emergency copy of the project's current state.
Objects¶
flowchart TB
site[Site] --> host[Host]
profile[Server profile] --> host
site --> storage[Storage] --> volume[Volume]
site --> subnets[IP subnets] --> network
site --> network[Network] --> ranges[Ranges, BGP peer groups]
site --> core[Core services]
site --> platform[Platform]
platform --> ds[Datastores] --> volume
platform --> pnet[Platform networks] --> network
platform --> cluster[Clusters] --> host
org[Organization] --> project[Project]
project --> records[Resource records per cluster and site]
project --> conn[Connectivity per site: addresses from the IP subnets]
records --> clusterflowchart TB
site[Site] --> host[Host]
profile[Server profile] --> host
site --> storage[Storage] --> volume[Volume]
site --> subnets[IP subnets] --> network
site --> network[Network] --> ranges[Ranges, BGP peer groups]
site --> core[Core services]
site --> platform[Platform]
platform --> ds[Datastores] --> volume
platform --> pnet[Platform networks] --> network
platform --> cluster[Clusters] --> host
org[Organization] --> project[Project]
project --> records[Resource records per cluster and site]
project --> conn[Connectivity per site: addresses from the IP subnets]
records --> cluster
Read on:
- Data model: every record and field, IP subnets, project resource records, storage quotas, project status and the copy kept in OpenNebula.
- Network design: fabrics, segments, exchange networks, L2 channels, the EVPN fabric IP subnets and address allocation.
- Terms: the words used throughout these docs.