A license is required to use VMmanager. You can buy it in your client area at eu.ispsystem.com or reseller company. The license has an expiry date and a limited number of used physical CPU cores on cluster nodes.
If you are using the VMmanager Infrastructure version, you can purchase an additional package to increase the available CPU cores.
Licenses purchased before the release of version 6.9.0 have restrictions on:
- number of virtual machines (VM);
- the number of cluster nodes;
- number of LXD containers.
When purchasing a license, you can choose a free trial period of 14 days to learn about the features and test VMmanager.
Three days before the license expiry, VMmanager interface displays a message prompting to renew it. After renewing the license, you need to update the license information in VMmanager.
Versions of VMmanager
The VMmanager platform has two versions: VMmanager Hosting and VMmanager Infrastructure. The differences between the versions are shown in the table below:
focus on the needs of hosting providers
focus on the needs of IT infrastructure owners
In the current implementation of the platform, the VMmanager Infrastructure version includes the following additional functionality:
- platform installation on the server with Astra Linux SE 1.6 "Smolensk", Astra Linux CE 2.12 "Orel", Astra Linux 1.7 (tested on version 1.7.1), RED OS 7.2;
- support of cluster nodes with RED OS 7.2;
- configuring a high availability cluster.
To switch from one version of VMmanager to another, purchase a license for the required version and update the license information in the platform interface.
How to update the license information
Before expiry date
To update the license information, go to → System information → Update the license.
After expiry date
After expiry of the license, VMmanager will be blocked. Cluster nodes and VMs operation will not be affected, but management via VMmanager will no longer be available. To reactivate VMmanager, renew your license and click Update license information in the pop-up message about the blocking.
If the license token has changed
If you change the company purchasing the license, the license token value will change. For example, if you ordered a trial period in your client area at eu.ispsystem.com, and then purchased a license from an ISPsystem license reseller company.
To update information about such a license:
- Connect to VMmanager via SSH protocol with superuser permission (the default level is root).
In the configuration file /opt/ispsystem/vm/config.json specify the new license token value in LicenseToken.
Enter commands to re-create vm_auth_back_1 container:
To check license installation status, enter:
In case of successful license change, the response will be in the form: LICENSE_AUTH_TOKEN=aaaaaaaaaaaaaaaa:bbbbbbbbbbbbbbbbWhere
aaaaaaaaaaaaaaaa:bbbbbbbbbbbbbbbb — new value of the license token.
- In VMmanager interface, go to → Update the license → System information.
Limited number of devices
VMmanager license has a limit on the number of used physical CPU cores on cluster nodes. When this limit is reached, the ability to add VMs will be blocked. To enable adding new VMs, delete the unused ones or purchase a license with the ability to use more CPU cores. VMmanager Infrastructure users can purchase an additional package to increase the available CPU cores.
Licenses purchased before the release of version 6.9.0 have a similar limitation on the number of VMs, cluster nodes, LXD containers.
After you purchase a resource package, you need to activate it:
- Go to → System information → Activate package.
Enter the code from your resource package certificate.
- Press Activate.
The resource package has an expiration date and is purchased for a specific license. It cannot be activated in another instance of the platform.