Bare metal as a service
Offer your tenants dedicated bare metal servers on demand. A tenant requests a server, and vMetal provisions it from your hardware with the tenant's SSH keys on it. Nothing installs Kubernetes unless the tenant wants it.
This page shows how the pieces fit together and the order to build them in. Each step links to the guide that owns the procedure.
What the service provides
- A dedicated physical server. No other tenant's workloads share its hardware or kernel.
- Self-service requests. Tenants request a server from the Instances view in their project, or through the management API as a
NodeClaim. - Their own access. The server boots your chosen OS image with the tenant's SSH keys and user data, and nothing else.
- Reuse on release. Releasing the server returns it to the pool for the next request.
The same servers can also join clusters as dedicated nodes. A server provisioned as bare metal today can back a cluster tomorrow, from the same pool and the same API.
How it works
vMetal exposes one stable Machine API upward and uses pluggable provisioning drivers underneath. Your tenants request capacity the same way whichever driver supplies it.
| Layer | What it does | Where it's documented |
|---|---|---|
| Provisioning driver | Provisions your servers. Metal3 provisions bare metal directly. NVIDIA Infra Controller (NICo) provisions servers it already manages at a NICo site. Both support servers that don't join a cluster. | Provisioning drivers |
| Node provider and node type | A node provider connects the platform to a driver. Node types describe the hardware classes you offer. | Node providers and node types |
| Instance | A tenant's claim on one server, represented by a NodeClaim. | Instance and server concepts |
| Project | Decides who can request instances, which node types they can use, and how many instances they can hold. | Allowed node types, Instance quotas |
Build the service
- Install vCluster Platform on the cluster that will run the management plane. Instances require the Machine Management feature in your license. See Install.
- Connect your hardware through a provisioning driver. For Metal3, start with the requirements and overview. For NICo, connect your NICo site as described in the NVIDIA Infra Controller driver guide.
- Define what you offer. Create node types for each hardware class, and the OS images and SSH keys they use. See Node providers and node types. Your OS image carries anything the server needs after first boot, such as GPU drivers, so plan images with where the service ends in mind.
- Give tenants access. Give each tenant one or more projects. Restrict each project to the node types it may use, and cap how many instances it can hold. See Allowed node types and Instance quotas.
- Let tenants request servers. Tenants request, connect to, and release servers as described in Independently provisioned instances. For the tenant-facing overview, see Instances. To test the service, request one server from a tenant project and connect to it over SSH.
Operate the service
- Track capacity. The machine inventory mirrors every server your providers report, separately from the claims on them.
- Add and remove servers as your fleet changes. For Metal3, see Metal3 operations.
- Keep tenants apart. Project boundaries control which servers each tenant can claim. For Metal3, see Prevent cross-project server access.
- Troubleshoot provisioning. For Metal3, see Metal3 troubleshooting.
Know where the service ends
vMetal owns everything up to and including first boot. That covers the server, its OS installation and network configuration, and the claim on it. Your OS image and the tenant own everything after that, including GPU drivers, in-guest monitoring, patching, and any software the tenant installs. Plan your OS images and support boundary around that line. See What vMetal manages, and what it doesn't.
Related
- AI cloud provider and Compute aggregator show how bare metal combines with clusters in a complete platform.
- GPU presentation modes explains how vMetal exposes GPUs on servers it provisions.
- vMetal overview covers the full machine layer.