Tessera & NovaOS · Concept guide
Know the host
behind the state.
Clouds describe the estate you manage. Hosts are the execution targets within it.
Keep ownership visible
A host belongs to an authorized organization and project scope. Its display name is useful for people; its stable identity identifies the target.
Fleet and cloud views group the estate for navigation. A grouping does not grant access to its hosts or imply permission to run work across projects.
- Organization and project
- The ownership and access scope for records and operations.
- Host identity
- The specific execution target, separate from its display label.
- Release and capabilities
- The installed software and supported work reported for that host.
Read observed state carefully
A last observation is not proof of a current connection. Keep its time and source visible when deciding what to do next.
A disconnected host and a failed workload are different conditions. Retained logs and results may remain useful even when the host cannot be reached.
On your sites and beyond
Managed infrastructure can be on-premises, off-premises or mixed. The location of Nova Platform itself is a separate hosting decision.
General-purpose VM and container hosting are planned product capabilities. Creating and managing those workloads is not available in the console yet.