Platform services¶
What the platform provides to its end customers, the projects.
Projects¶
A project has its own resources, network and users. It belongs to an organization, which can have several projects. (Earlier versions of the portal called it a tenant; the code still does.)
- In OpenNebula a project is one group. The group name is the project ID,
_<org>_<project>(letters and digits: the organization's short name, 3–15 characters, and the project's, 4–15 characters, without "-"). It never changes once the group exists. - Each project has one OpenNebula admin account,
<org>-<project>-adm, for the console. The project admin, a user of the organization, gets its credentials. - Projects are separated in the console (own group, quotas and permissions) and on the network (own networks and gateways).
- A project's type is cloud or corporate; only corporate organizations order corporate projects.
- Its stage is POC (proof of concept) or client (production). Every project starts as a POC; a POC is reviewed a month after it is created.
- Its status is ok, paused, suspended, saved or archived, with a review date when the current status (or the POC) ends; see Data model.
Resource pools¶
A project orders resources from a pool: a cluster of a shared platform. Its resources are recorded per cluster and site, and every change is a new version of that record.
| Pool | What the project orders |
|---|---|
| IaaS cluster | vCPU and RAM. VMs run within these limits. |
| GPU cluster | GPU bundles: one bundle is one GPU with a fixed share of vCPU and RAM. Each GPU is passed through to a VM as an entire PCI card (PCI passthrough), never shared or overcommitted. |
Storage and backups come with every project; see Storage. The network is described in Network.
Read on¶
- Storage: one storage number, its split, backups.
- Network: connection types, gateways, L2 channels.
- Services for projects: the customer-facing summary, also in Russian and Kazakh.