Reading a SolusVM 2 estate without touching it
KLYRN VM connects to a running SolusVM 2 panel, reads the whole estate into its own tables, and changes nothing on the source.
The hardest part of changing virtualisation panels is the first step, because the estate is in production. KLYRN VM's Migration Center is built around one rule: reading a panel must be safe to do on a live one.
What it promises
- It only reads. Every request to the source panel is a GET, and the build fails if any other method appears in the importer.
- It writes here, not there. What a scan finds goes into KLYRN's staging tables. Nothing changes on either system.
- It hands over nothing by itself. The source panel stays in charge until an operator adopts a host.
What a scan shows
Connect a panel with its address and an API token, press Read the estate, and KLYRN lists what it found: compute nodes, virtual servers, plans, IP blocks and customers, with a per-host readiness page that says what, if anything, stands between that host and KLYRN. On a real four-node estate a single scan staged 296 records.
Every request KLYRN made is listed under the panel, so the claim that it only read is something you can check rather than trust.
Read more on the migration page.