Operation principles of VMmanager 6 module

Service activation algorithm

After a client has ordered and paid for the service, BILLmanager starts the VM creation process:

1. Logs in to VMmanager 6 with admin permissions. BILLmanager uses the credentials from the processing module settings. 
2. Checks that the client exists in VMmanager 6.
3. Creates a new user account if needed. 
4. Sends a request to create a new virtual machine. VMmanager 6 performs the following operations: 
   
   1. Checks the data from BILLmanager and selects a cluster node.
   2. Assigns the IP address to the server. If the cluster has several IP pools, it selected the one with the smallest ID. If the pool is not available, it selects the next one with the larger ID. 
   3. Uploads the required operating system if it is not created on the node. 
   4. Creates and runs the VM. 
5. Waits when the VM creation task is completed. 
6. Automatically terminates the IP creation tasks. IP management operations are performed in VMmanager 6. 
7. Receives and saves information about the VM: its IP address, domain, and password. 

Changing VM resources

Changing main VM parameters (vCPU, RAM, disk) can be performed without rebooting. For changing other parameters, the VM will be rebooted.

Hot changes (without rebooting) are supported for the following resources:

• Number of CPUs — only increasing is supported. Maximum — 128 cores (Windows OS), 240 cores (other OS);
• RAM — only increasing is supported, in steps of 1024 MiB. The maximum number of increases allowed per VM is 16;
• Disk space — only increasing is supported. When attempting to specify a smaller size, the value is ignored.

Hot changes are supported if the following conditions are met:

1. The cluster uses KVM (Kernel-based Virtual Machine) virtualization.
2. In the service card, the following options are enabled:
   • for CPU and RAM — Increase CPU and RAM values without VM reboot;
   • for disk space — Increase disk size without VM reboot.

If resources supporting hot updates are changed simultaneously with other parameters, the VM will be rebooted.

Logging

Logs of interaction between the billing system and VMmanager 6 are located in /usr/local/mgr5/var/pmvmmgr6.log.