Automatic VPS bandwidth limits are now enforced
Every automatically provisioned VPS now receives its purchased speed as a converted and verified Proxmox NIC rate limit before the service can be marked ready.
Plan speed now follows the VPS into production
SCComp automatic provisioning now carries the bandwidth published on each VPS plan into the Proxmox virtual network-interface configuration. Catalog plans are expressed in megabits per second, while Proxmox QEMU NIC rate limits are megabytes per second, so provisioning performs the required divide-by-eight conversion. A 100 Mbps plan is configured as 12.5 MB/s, a 250 Mbps plan as 31.25 MB/s, and a 1 Gbps plan as 125 MB/s.
Delivery is fail-closed
The provisioning worker now rejects automatic deployment when a catalog plan has no positive bandwidth value. It also reads the live Proxmox configuration back after applying the converted value. If the rate is missing, malformed, or different from the expected MB/s value, the VPS remains non-ready instead of being delivered without its intended limit.
Existing production automation brought into compliance
The current automatically provisioned VPS instances on the approved vmbr20 customer network were checked against their database-bound orders and updated to the converted rates. The legacy broken-template test systems remain isolated for their separate reprovision workflow, and protected VM 915 was excluded.
Validation
• Added regression tests for 100, 250, and 1,000 Mbps conversions, idempotent updates, stale-rate replacement, and missing-limit rejection.
• Passed the complete application test suite.
• Verified live Proxmox readback: the 250 Mbps service reports 31.25 MB/s and the 100 Mbps service reports 12.5 MB/s.
• Restarted the provisioning worker and gracefully reloaded the customer site.
The public VPS plan page now also states that published bandwidth is enforced during automatic provisioning.