A physical location, an availability zone, with its networks, IP subnets, storage and servers.
IP subnet
A public or corporate address range of a site, carried by one exchange network. Projects get their addresses
from it, in blocks no larger than its max. Its type (internet or corporate) is detected from the address.
Exchange network (ix)
A transit VLAN with routers only, connecting the projects' edges to the internet (cloud-ix) or to the
corporate network (corpnet-ix) over BGP through route reflectors.
Core service
A service the site itself runs (not a project's): name servers, jump hosts, front ends, route reflectors,
gateways, backup storage and the like; deployed on existing hosts or from scratch as VMs.
Platform
An OpenNebula front end with a predefined type (mgmt, shared or ext-managed), belonging to a site.
Platforms on different sites can be federated.
Cluster
A group of a platform's hosts with their VMs and images datastores. A host belongs to one cluster.
Resource pool
A cluster from which projects order resources: an IaaS cluster (vCPU, RAM) or a GPU cluster (GPU bundles: a
whole GPU with a fixed share of vCPU and RAM).
Portal
The only interface to the platforms: underlay management (deploy and maintain platforms) and service
management (IaaS for projects).
Underlay
The physical network between servers that carries all platform traffic.
Host OS
The operating system installed on each hypervisor host.
OpenNebula
The open-source cloud management platform that runs virtual machines and manages compute, storage and network resources.
VyOS
The open-source network operating system used for routing in the platform and for project networks.
Inventory
The portal's record of the provider's infrastructure: sites, hardware, networks, platforms and core services,
entered in the portal after it is installed. Deployment is driven from it. See Inventory.
Platform admin
Someone who builds and maintains the platform: day-1 deployment and day-2/3 operations.
Platform user
A member of the provider's staff with the roles needed to sell and control the resource pools provided to
end customers.
Organization
An end customer, identified by its country and tax ID (in Kazakhstan the IIN or BIN of a legal entity, an
individual or an individual entrepreneur), of type cloud or corporate. It can have several projects.
Project
What an organization orders: its own resources, network and users; one OpenNebula group, whose name is the
project ID (_<org>_<project>). Earlier versions of the portal called it a tenant, and the code still does.
Project admin
The user of the organization responsible for a project; gets its credentials.
Stage
The commercial state of a project: POC (proof of concept; every project starts here) or client (production).
Status
Where a project is in its lifecycle: ok, paused, suspended, saved, archived. The review date is the day the
current status (or the POC) ends and is reviewed.
egw
The provider edge: the provider's router between a project and the internet exchange network. It controls
bandwidth and passes only the project's own addresses.
cgw
The corporate edge: the provider's router between a project and the corporate exchange network.
igw
The project gateway: the project's own router — advanced (VyOS), native (OpenNebula Service Virtual
Router) or custom (the project's own VM) — inside the project's resource pool.
L2 channel
A VLAN of the client's site brought into a project network over the provider's L3 network, by two VyOS VMs
(or one on an edge cluster).
Day 1
Deployment — creating the cloud platform from scratch, based on the inventory.
Day 2 / day 3
Ongoing operations — maintaining, updating and scaling the platform, automated through the portal.
How much of the portal a licence allows: Standard or Enterprise. Both run the same product. See
Licensing.
Standard
The free edition, with no time limit on use, its source public under the Business Source License 1.1 (each version AGPL 3.0 four years after it is published): one portal node, backups and updates on fixed settings, public code, installed and updated as a bundle from my.claugine.com.
Enterprise
The commercial edition, with full support, its code private under the PolyForm Internal Use License 1.0.0 (no end date): two portal nodes on one or two sites, backups and updates chosen, private code delivered by
my.claugine.com.
Licence
Issued on my.claugine.com for one installation; every installation needs one. For its
term its key gives the installer, automatic updates and restore from a backup. A Standard licence is free and
issued to anyone who registers, once the account is approved; an Enterprise licence is paid, requested and
approved, and can be tried for a limited time (a short licence). A licence is an edition and its validity; a
Standard one runs a year and is extended on request by 1 to 12 months. When it has expired, the portal keeps
working, without them.
Licence key
What identifies a licence to the installation script and to the portal (CLG-…).
Installation
One portal: one node under Standard, two nodes under Enterprise. One licence covers one installation.
Installation id
The installation's FQDN, the host of its site URL (for example portal.example.com), which binds it to its
licence. Installing again or restoring under the same name keeps it; a portal under another name is a new
installation (release the old one first).
Check-in
The portal asking my.claugine.com, every few minutes, for its licence and edition and for the version to install.
my.claugine.com being unreachable never stops a portal.
Grace period
The 60 days after a licence ends, the same for every licence, in which updates continue. After it the licence has
expired: the installer, updates and restore stop until it is extended; running projects, VMs and networks are
never stopped or limited.
Released installation
An installation released from its licence, which frees the key for a new installation. It keeps running and
keeps the limits of its edition, but receives no further updates. Installing again under its name with a free
licence of the same customer brings it back.