Integration with VMmanager KVM/OVZ

From ISPWiki

Jump to: navigation, search

You must have admin (not root) permissions to set up integration between BILLmanager and VMmanager.


Customizing add-ons

VMmanager KVM and VMmanager OVZ support the following service package add-ons:

  • Disk size (in VMmanager this parameter cannot be modified upon service activation. We recommend selecting the check box "Forbid clients to change the package"
  • Number of CPU (kernels)
  • CPU frequency
  • RAM (consider the minimum values allowed for order on a specific OS)
  • Number of IP addresses
  • Number of IPv6 addresses (at least one parameter must be not less than 1, otherwise it will be impossible to create a VPS)
  • Operating system. Should be specified if you use commercial operating system.

Vmmanager OVZ (VEmanager) also has the following parameters:

  • Processes - corresponds to "proc" in BILLmanager.
  • File discriptors - corresponds to "files" in BILLmanager.
  • Incoming traffic - by default is not present in BILLmanager. Internal name is chratein
  • Outgoing traffic - by default is not present in BILLmanager. Internal name is chrateout
  • swap to RAM ratio (ib %) - by default is not present in BILLmanager. Internal name is 'swapratio

You can bill clients for the following add-ons based on statistics:

  • traffic - VMmanager/VEmanager send information about both incomming (the in parameter) and outgoing (the out parameter) traffic.

Versions and later the following parameters can be collected:

  • io - the number of input/output operations. The data is collected in hundreds of input/output operations per 24 hours (the internal name of the unit of measure is hio), add-ons to service packages can be set up using "iops" that is 864 times as less as hio - the total number of input/output operations divided by the number of seconds in 24 hours.
  • cpu - cpu usage time. The data is collected in cpu seconds per 24 hours.

Processing orders

  1. Make sure there is a VMmanager/VEmanager user associated with the client who orders the service.
  2. If not, the account will be created in VMmanager/VEmanager, and all client's services will be associated with that account.
  3. VMmanager/VEmanager will send parameters of the selected OS template.
  4. If add-ons are configured in BILLmanager, default values will be changed into that values.
  5. IP addresses will be checked. If IPv4 is not present, IPv6 address will be assigned to the virtual machine.
  6. The VM creation command will be sent to VMmanager/VEmanager.
  7. After getting response from the server, the OS installation process will be checked every 30 seconds. Once installed, the service will be considered active and a corresponding notification will be sent to the client.

Additional information in XML of the welcome letter

You can add the following parameters into the welcome letter:

<itemparam.password>xxx</itemparam.password> - VMmanager/VEmanager user password 
<itemparam.account>test.recalc</itemparam.account> - VMmanager/VEmanager username 

For example:

Username in VMmanager/VEmanager: <xsl:value-of select="itemparam.account"/>
User password in VMmanager/VEmanager: <xsl:value-of select="itemparam.password"/>

We recommend that you add the root password change notification:

For security reasons we recommend that you change the root password.

Additional information

If BILLmanager is integrated with IPmanager, add the ExternalIpAllocation option into the VMmanager/VEmanager configuration parameter.

BILLmanager will get a list of containers and OS templates from VEmanager upon basic configuration of VEmanager, i.e. you must first add and set up IP addresses, add OS templates and create a container in VEmanager.

Transferring services from VDSmanager

Versions and later support automatic synchronization of data of virtual machines migrated from VDSmanager into VMmanager or VEmanager. Execute the following operation:

/usr/local/ispmgr/sbin/cpvmmgr fix

Complete the steps below for migrating virtual machines and containers:

  1. Set the VDSmanager server to manual setup
  2. Migrate virtual machines and containers to a new server with VMmanager or VEmanager
  3. Add connection to VMmanager or VEmanager, if needed
  4. Run the command
/usr/local/ispmgr/sbin/cpvmmgr fix

While executing the command, the module will search all the virtual servers registered in BILLmanager that are connected to the VMmanager/VEmanager server or to server with manual setup (search is performed by IP address). The following changes will be made:

  1. If the virtual server in BILLmanager does not have the id that can be used to identify it in VMmanager/VEmanager, it will be taken from the panel and saved in the database.
  2. If the username who owns VMmanager/VEmanager is not specified for a virtual server in BILLmanager, a new user corresponding to the BILLmanager user will be created in the panel or the name of the existing user will be received. That username will be saved in the database as the virtual server's owner.
  3. Th owner of the virtual machine or container will be changed into the user created above.
  4. If the previous owner of the virtual machine or container does not own anything else, it will be deleted.
  5. If needed, in BILLmanager the processing server will be changed into the VMmanager/VEmanager server.

Once completing the steps, all the operations with virtual servers in BILLmanager will be performed automatically.

Was this helpful? Yes | No
Personal tools