High Availability
Last updated
Last updated
High availability for Lapdev controllers can be achieved by simply adding more Lapdev Controller nodes, as described in .
The following has not been done yet.
In case a workspace host is down, we'll need to recover the data under /workspaces, where all the workspace data should be stored.
For simplicity of the cluster administrator, it's on the roadmap that Lapdev will deal with the data replication between workspace hosts, and actively re-provision workspaces to a new workspace host using the replicated /workspaces data should a workspace host be down.