Admin Guide

Admin dashboard

The admin dashboard is the operational overview for VMNexor. It should be used to quickly check platform health, node state, licensing, recent activity, and whether any customer or provisioning issues need attention.

Infrastructure management

• Add and manage Proxmox nodes
• Review node connection health
• Confirm storage availability
• Manage IP pools
• Prepare nodes before assigning customer services

Plans

Plans define the resource packages customers can receive. A plan should include CPU, memory, disk, allowed templates, and reinstall rules. Billing providers such as WHMCS should map products to these VMNexor plans.

Plan checklist

• Set CPU core count
• Set memory allocation
• Set disk allocation
• Choose allowed templates
• Choose reinstall policy
• Confirm whether Windows and Linux templates should be mixed on the same plan
• Test the plan with a disposable service

Templates

Templates should be registered only after they have been tested directly in Proxmox and through VMNexor provisioning. Avoid making new templates public until networking, password behaviour, console access, and guest-agent actions have been verified.

Services

• View provisioned customer VMs
• Check current service status
• Run lifecycle actions
• Investigate failed provisioning
• Assist with customer reinstall issues
• Compare VMNexor state against Proxmox state when needed

Customer support workflow

• Find the customer service in VMNexor
• Check service status and recent actions
• Confirm the VM exists in Proxmox
• Check node and template state
• Review whether the issue came from billing, VMNexor, or Proxmox
• Avoid destructive actions until the customer confirms data loss is acceptable

Billing provider workflow

Billing providers should create and control services through VMNexor rather than directly managing Proxmox. This keeps infrastructure automation consistent and allows VMNexor to enforce plans, templates, reinstall policies, and lifecycle rules.

Safe operating rules

• Test every new plan before public sales
• Do not delete customer VMs manually unless VMNexor state is also reconciled
• Keep admin access limited
• Monitor failed lifecycle actions
• Keep backups of database and shared configuration
• Document any manual recovery actions

Recommended launch checklist

• At least one node connected and healthy
• At least one Linux template tested
• At least one Windows template tested if Windows is being sold
• Plans configured and tested
• Billing adapter tested with create, suspend, unsuspend, terminate, and reinstall
• Customer portal reviewed
• Support process documented