Documentation

SkyVirtHCI is a hyperconverged virtualization platform. In practical terms: you install it on a few servers, and those servers together provide virtual machines, shared resilient storage, virtual networking, and the management console to run it all. There is no separate storage appliance, no separate network controller and no separate management server to maintain.

How the documentation is organised

Guide	Read it when…
Getting started	You're installing the platform for the first time, on one node or three.
Administration	You run VMs, networks and storage day to day.
Operations	You're responsible for backups, disaster recovery, upgrades and monitoring.
Security & access	You manage who can do what — accounts, roles, sign-on, audit.
Migrating to SkyVirtHCI	You're moving VMs in from another virtualization platform.

A few ideas worth knowing up front

The cluster is the unit

Hosts join a cluster; the cluster pools their CPU, memory and disks. You think in terms of "the cluster has room for this workload", not "which server do I put this on". When you do care about placement, affinity rules and manual pinning are there.

Storage is everywhere and nowhere

Data disks across the cluster form one replicated pool. A VM's disk isn't on a server — it's in the pool, with copies on more than one server. That's what makes live migration and host failure recovery routine instead of frightening.

Tenants keep things apart

Every resource belongs to a tenant. Users in one tenant can't see another tenant's VMs, networks or images. Within a tenant, projects and quotas give finer-grained boundaries. A single-team installation simply uses one tenant and never thinks about it again.

The console and the API are the same thing

Everything the web console does goes through the same documented REST API you can use yourself. Scoped API keys let automation do exactly what you allow and nothing more.