System requirements
Prepare compute, storage, and network access before you deploy.
Native appliance target
The native installer checks for Debian 13 amd64. Cenovel runs in the customer’s own infrastructure; these instructions do not describe a cloud-hosted service. Use the console from a desktop browser.
Plan appliance resources
Size the VM for your device count, polling cadence, stored files, and retention needs. No measured production capacity or devices-per-VM guarantee is published here.
Separate your data
- Operating system and releases:
/and/opt/cenovel. - Database:
/var/lib/mysql. - Application data:
/var/lib/cenovel. - Native backup staging:
/var/backups/cenovel. Keep a recovery copy off the appliance.
With the supplied native configuration, first boot requires separate mounts for the database and application data.
Network access
Staff use HTTPS to reach the console. Device reads use SSH with Device CLI profiles, or SNMPv3 authPriv where configured. Allow the ports configured for those devices and only the external services you choose to connect.
Read the operator reference
1. Platform and resources Cenovel keeps inventory, topology, device observations, work records, and E-Rate records on the customer's own appliance or VM. The console is intended for desktop browsers. The responsive marketing website is not the console. The native installer checks for Debian 13 amd64. Its supplied configuration uses /var/lib/mysql for the database, /var/lib/cenovel for application data, and /var/backups/cenovel for local backup staging. With the supplied native configuration, first boot requires separate mounts for the database and application data. Releases are stored under /opt/cenovel. Plan compute, storage, and retention around the actual workload. No measured production device-capacity guarantee is published here. The recorded vSphere acceptance programme has not been executed against real hardware. Staff reach the console over HTTPS. Device reads use SSH with Device CLI profiles, or SNMPv3 authPriv where configured. Permit the ports configured for those devices and the optional external services the district chooses to use.
Reviewed against the current source code. Native appliance administration commands require the appropriate host privileges; validate deployment procedures on your own release before production use.