Add hosts to QvDC

Adding a QHCI host to QvDC lets you manage its VMs, storage and networks from the dashboard, and lets clusters move VMs between hosts. The host proves it is yours with a one-time registration token generated on the host.

Prerequisites

• A QHCI host installed and reachable (see Install a QHCI host).
• QvDC installed (see Install QvDC).
• QvDC can reach the host on TCP 8443 (web and API) and 9443.
• The host's clock and QvDC's clock agree to within two minutes. Configure the same NTP servers on both.
• At least one cluster in QvDC — hosts are added into a cluster.

Step 1: create a cluster

1. In the dashboard go to Clusters and click New Cluster.
2. Basic information — enter a Cluster Name, an optional Description, and keep Cluster Zone on Standard Zone.
3. Select hosts — skip this for now if no hosts are registered yet.
4. High Availability settings — you can enable High Availability and DRS (automatic load balancing, with an Automation Level of Manual, Partially Automated or Fully Automated) now or later. High availability needs shared storage to restart VMs on another host.
5. Click Create Cluster.

Step 2: generate a registration token on the host

Use either:

• the host's Direct Console: Join / Manage Cluster → Generate Registration Token; or
• the host's Host UI: Admin Panel → Cluster → Generate Registration Token.

The token looks like QUANTIX-XXXX-XXXX-XXXX-XXXX. It can be used once and expires after a short time, so generate it just before the next step.

Step 3: trust the host's certificate in your browser

The host starts with a self-signed certificate. Your browser talks to the host directly while it is added, so it must accept that certificate first: open https://<host-address>:8443/ in the same browser and accept the warning. (Replacing the host's certificate with one your organization trusts avoids this step.)

Step 4: add the host

1. In the dashboard go to Hosts and click Add Host.
2. Enter the Host IP Address or URL. Port 8443 is added automatically.
3. Click Test connection. Every check should pass:
   • Host answers on its management port
   • Certificate is valid for this address
   • Host clock agrees with QvDC
   • Node daemon supports token registration
   • Certificate is trusted by this browser
4. Paste the Registration Token and choose the Target Cluster.
5. Click Connect & Discover Resources. QvDC shows the host's CPU, memory, storage, network interfaces and GPUs under Discovery Complete — Review & Confirm.
6. Click Add Host to Cluster.

Expected result

The dialog shows Host Enrollment Started. Within a minute the host appears on the Hosts page as ready, its VMs appear in the inventory, and its Host UI shows it as managed by QvDC.

Reading the Hosts page

Two columns describe each host's CPU, and they answer different questions:

• CPU Usage is the load the host measures right now. This is the figure to watch: a host that stays near 100 % is short of CPU.
• vCPU Committed is how many vCPUs the host's VMs have been given, against what QvDC will place on it. Giving VMs more vCPUs than the host has threads is normal: by default QvDC places up to 3 vCPUs per host thread (one thread is kept for the host itself). 100 % means that limit is reached, not that the host is busy. QvDC does not place a new VM on a host that it would take past the limit, and load balancing and high availability use the same limit.

If a check fails

Check	What to do
Host answers on its management port	Check the address, that the host is powered on, and that no firewall blocks TCP 8443 between QvDC and the host.
Certificate is valid for this address	The host's certificate does not name the address you typed. Use the address shown on the host's Direct Console.
Host clock agrees with QvDC	Point both at the same NTP servers and wait for the clocks to converge. A difference over two minutes warns; over an hour blocks.
Certificate is trusted by this browser	Do Step 3 again in this browser, then click Test connection.
Token rejected	The token was already used or has expired. Generate a new one.

Re-adding a host

If a host was previously added (for example after reinstalling it), QvDC recognizes its hardware and offers Recover Existing Host or Replace Existing Host. Only choose Replace after confirming the old host is powered off or isolated and cannot reconnect.

Removing a host from QvDC

On the host, Join / Manage Cluster → Leave Cluster in the Direct Console returns it to standalone management. Move or shut down its VMs first.