ores.compute.platform
Table of Contents
A target a wrapper and engine can be built for, named by its triplet code
(for example x64-linux). A package belongs to an app version and a
platform, so the orchestrator matches incoming workunits against the host's
triplet through this row.
The platform registry is a global one: the platform rows ship under the
system tenant and every tenant reads them, which
:system_tenant_visible: true states on the repository.
is_active retires a triplet without deleting it, so a package that names
it still resolves. It is a plain column and not a declared filter, because
the generated read refuses a filter, and a filter the service rejects is
worse than no filter at all.
1. Flags
2. Columns
2.1. id
UUID primary key for the platform.
2.2. code
Triplet code, e.g. 'x64-linux'. This is the key callers address the row by.
2.3. display_name
Human-readable name, e.g. 'Linux x86-64'.
2.4. description
What the triplet targets.
2.5. os_family
Operating system family: linux, macos or windows.
2.6. cpu_arch
CPU architecture: x86_64 or aarch64.
2.7. abi
Application binary interface, where the triplet distinguishes one. Empty for a triplet that does not.
2.8. is_active
Whether the triplet is offered to hosts. A retired triplet keeps its row so packages that name it still resolve.
3. SQL
3.1. Flags
4. C++
4.1. Flags
4.2. Repository
The platform registry is shared: the platform's rows ship under the system
tenant and every tenant must see them, which :system_tenant_visible: true
states on the repository.
4.3. Domain includes
#include <string>
4.4. Conventions
4.5. Table display
| column | header |
|---|---|
| id | ID |
| code | Code |
| display_name | Display Name |
| os_family | OS Family |
| cpu_arch | CPU Arch |
| is_active | Active |
| modified_by | Modified By |
| recorded_at | Recorded At |
5. See also
- ores.compute — component group overview.