The import from another panel reads a SolusVM 1 or SolusVM 2 installation through its admin API and brings over what you choose: accounts, plans, IP blocks and KVM servers. Server disks are copied by a VMStack node that logs into the SolusVM hypervisor over SSH. A server whose hypervisor the nodes cannot reach is kept as records only (its account, plan and addresses held in VMStack) and can be moved later.
The other panel is only read. A server is shut down there only when you ask for a clean copy, and started again if that copy fails. OpenVZ and Xen servers are listed but not imported.
Before you start#
- API access. SolusVM 1: create an API user under Configuration › API Access on the master, allowing the panel's address; you get an API ID and an API key. SolusVM 2: create an admin API token.
- Network. The panel reaches the SolusVM master's API (SolusVM 1 on TCP 5656, SolusVM 2 on its HTTPS port). Each VMStack node that receives servers reaches the hypervisors over SSH (TCP 22).
- SSH on the hypervisors. A user that can run
virshand read the disks (LVM volumes or image files);rootis the simple case. - VMStack side. The nodes that receive servers, with IP blocks for the addresses (or let the import create them), and a current agent on those nodes.
Connect the panel#
- Go to Infrastructure › Import from another panel › Connect a panel.
- Under The panel, choose SolusVM 1 or SolusVM 2, and give a Name and the Address:
- SolusVM 1: the master, for example
https://master.example.net:5656(the API path/api/admin/command.phpis added for you). - SolusVM 2: the management node, for example
https://solus.example.net(the API is/api/v1).
- SolusVM 1: the master, for example
- Under API credentials: SolusVM 1 API ID and API key; SolusVM 2 API token. They are stored encrypted, never shown again and never logged.
- Optionally paste the Certificate fingerprint (optional) (SHA-256).
- Under Copies, set Servers copied at once (1 to 8).
- Press Save and check.
The check reads the panel's TLS certificate first and sends no credentials until it is trusted. SolusVM's certificates are usually self-signed; compare the fingerprint the page shows with the certificate on the master:
openssl x509 -noout -fingerprint -sha256 -in /path/to/certificate.pem
Then press Trust this certificate…. The panel pins the certificate's key, so later calls work without turning verification off. Once trusted, the source reads the inventory: hypervisors, users, plans, IP blocks and servers. Check and read again refreshes it.
SolusVM 1 does not list IP blocks through its API: each hypervisor's addresses are shown as one block "
Map the hypervisors and their SSH login#
The source page lists the hypervisors (Hosts). For each one whose servers you want to copy:
- Press Map and SSH….
- Choose the VMStack node its servers go to, and the SSH host, Port and User the nodes log in with.
- Add the lines under The nodes' keys to add to the host's /root/.ssh/authorized_keys to that file on the hypervisor. Each node has its own key; its private half never leaves the node.
- Press Save and check the login.
- Back on the source page, compare the offered SSH host key with
ssh-keygen -lfon the hypervisor (the page names the file) and press Trust host key…. Check SSH runs the login again; its line says whethervirshandqemu-imgrun and how many domains were found.
The import wizard#
On the source page press Import…. The wizard has four steps; step 1 was connecting the panel. Nothing changes until you press Run the import.
2. What it has#
The inventory as read, with a box for each item: Accounts, Plans, IP blocks and Servers (owner, plan, host, system and disk, addresses). Tick what to bring over.
3. How it maps#
| Section | Choices |
|---|---|
| Accounts | Matched by e-mail to an existing VMStack account, else created as users with no known password. Mail each new account a link to set its password (only when mail works; otherwise they use Forgot password later). Optionally set each new account's external ID to the other panel's client ID (leave it off when a billing system such as WHMCS sets external IDs) |
| Plans | Each plan to a VMStack plan of the same size (chosen by default when one exists), Create a VMStack plan of the same size, or None: its servers keep their own size |
| IP blocks | Each block to the VMStack block holding most of its addresses, Create it on node … (IPv4 with gateway and netmask known; IPv6 blocks of SolusVM 2 are created on the node's link), or None |
| Other network cards | For servers with more than one card: each network to a private network (the card's MAC kept) or Not carried |
| Servers | Per server: Copy its disks now, Records only, move later, or Skip |
| Copies | Shut each server down on the other panel before its copy, Start the server on VMStack after the copy, Addresses (keep them where the node's blocks have them free, else new ones; or new addresses), Network card and Disk bus (VirtIO by default; e1000 and SATA for systems without VirtIO drivers), Plan of the servers without a mapped plan, and the owner of servers whose account is not imported |
4. What will happen#
The dry run: one row per item with what the run will do (create, match, map, records only, copy, done before, refused) and conflicts, for example an address VMStack already gives to another server. Download as CSV saves it. Press Run the import to start.
The run creates or links accounts, plans and IP blocks, holds the addresses of records-only servers, and queues the copies. Its page shows the report with each item's outcome, Download the report (CSV), and Follow the copies (Infrastructure › Imports in progress). Running the wizard again is safe: items already brought over show "Done before" and are not made twice.
How a server is copied#
At its turn, the server is made on its hypervisor's mapped node like any new server (limits, capacity, addresses). The node reads the libvirt domain on the hypervisor over SSH and streams each disk (files, LVM and ZFS volumes, qcow2 backing chains flattened, compressed with zstd when the host has it).
- Hardware kept: vCPUs, memory, disk sizes, BIOS or UEFI (with the UEFI variables when they fit), machine type, the first card's model and MAC address. The MAC must not belong to another VMStack server.
- Addresses: kept when every IPv4 address of the server is free in the node's blocks or held for it by a records-only import; otherwise new ones, with a note to set them inside the server.
- Shut down first (recommended): the server is shut down on the other panel, copied, and started again there if the copy fails. Without it, the disks are read while the server runs and may need a file system check; a server that still runs there is made but not started on VMStack, since both would have the same MAC address.
Progress, Cancel and Retry are on Infrastructure › Imports in progress, as for Proxmox imports. A retry starts over (shutting the server down again).
Records only, and moving later#
A records-only server's account and plan are imported and its addresses are reserved in VMStack with a note naming the source, so nobody else gets them. To copy it later, tick it on the source page (servers listed as "Records only") and press Move N servers now… (or Move now on one); its held addresses become the server's.
Not imported#
OS templates, node groups and locations (VMStack's own are used), SolusVM 2 locations and projects, billing links (WHMCS service IDs), snapshots and backups, network disks (RBD, iSCSI) and VMs that are not x86_64 KVM. Accounts get no password from the old panel.
The API offers the same for administrators: GET /panel-sources, its inventory, the dry run (POST /panel-sources/{id}/plan) and the run. Sources are added only on the page. See the API reference.