Documentation / Getting Started
Architecture
VirtlixCP runs on one server of your own, called the panel server. Everything below is installed there by the installer, with no Docker.
| Part | What it does |
|---|---|
| Web application | The admin area, client area and API, served by nginx and PHP |
| Database | MariaDB, holding your inventory, clients, IPs and settings |
| Queue workers | Run long jobs in the background: OS reloads, switch changes, VPS actions |
| Scheduler | Runs recurring work such as bandwidth polling and license checks |
| PXE services | DHCP, TFTP, HTTP and Samba, used to reinstall dedicated servers over the network |
| Console proxy | Opens VPS consoles in the browser |
| Hypervisor | The panel server can also run KVM VPSes, and you can add more hypervisors |
Three addresses
The panel answers on three names that all point at the panel server:
| Name | Used by |
|---|---|
panel.example.com |
Your clients |
admin.panel.example.com |
Your staff |
api.panel.example.com |
Both areas, and your own integrations |
How it reaches your hardware
- IPMI and PDUs: the panel connects to each server's BMC (or an APC PDU outlet) to power it on, off and reset, choose the boot device and open the KVM console.
- Switches: the panel logs in to your switches over SSH to set VLANs and port speeds, and polls them over SNMP for bandwidth.
- PXE: a server being reinstalled boots from the network, gets its address from the panel's DHCP server and downloads its installer from the panel.
- Hypervisors: the panel manages KVM on each hypervisor over SSH.