BILLmanager 6 Startup, Advanced

Operating systems available for order. VMmanager 6

The minimum hard disk size can be set for the OS according to the system requirements. This value cannot be changed by the billing platform. To check it, go to ProductsProduct typesVPS item → Parameters button → Operating system item → Values button → select OS → Edit button → Hard drive field.

List of operating systems

After the integration is configured, BILLmanager receives a list of available operating system (OS) templates from VMmanager 6. The received default values are available for selection when ordering a VM on a tariff with VMmanager 6 processing module.

The OS list is saved in BILLmanager → ProductsProduct typesVPS item → Parameters button → Operating system item → Values button.

Operating system parameters: 

  • Name — the name of the operating system template. It corresponds to the template name in VMmanager.
  • Internal name — the unique identification for the OS template. It is created automatically per the template "<OS repository>__<OS template>". 
    • The value of the parameter is case-sensitive. For example, if you change the repository name from ISPsystem to ISPSYSTEM in VMmanager settings, templates from this repository will not be available.
    • If the repository name contains a hyphen character, this character will be replaced by a space in the internal name. This will cause an error when creating the VM. To solve the issue, replace all hyphens with spaces in the VMmanager repository name.  
  • Tags — the OS template tags. They are used to connect the template with recipes. In the current version, tags are not supported for VMmanager 6;
  • Sort — allows you sort out (in direct order) templates during order. Direct order is used;
  • Status – the status of the OS template:
    • — the template is available for order on all tariffs;
    • — the template is available for order on certain tariffs;
    • — the template is not available on any tariffs.

OS template management 

To make an OS template available for order you should connect it to a tariff and one of its processing modules:

  1. Go to ProductsProduct typesVPS item → Parameters button → Operating system item → Values button.
  2. Select the operating system and use the buttons:
    • Modules — a list of all modules for the Virtual server product type. Status shows if a template is available on the processing module:
      •  — the template is connected to the processing module;
      •   — the template is not connected to the processing module;
    • Tariff plans — a list of all tariffs for the Virtual server product type. Status shows if a template is available on the processing module:
      • — the template is available for order for the given tariff;
      • — the template is not available for order for the given tariff.

If several processing modules with different OS templates are connected to one tariff, all these OS templates will be displayed in one tariff. To prevent "extra" templates from being displayed in one tariff:

  1. Go to ProductsTariff Plans.
  2. Select a tariff → Clone button. Create as many tariff clones as the number of processing modules you need to separate from each other.
  3. Select a clone of the tariff → button Modules → enable a processing module for the tariff. Enable a separate processing module for each tariff clone.

Updates of the OS list

Once an hour, BILLmanager connects to VMmanager to update the information about available OS templates. The billing platform uses the following cron job: 

Cron job
## BILLmanager sync processing module configurations
54 * * * *	/usr/local/mgr5/sbin/mgrctl -m billmgr processing.getconfig >/dev/null 2>&1

To start the synchronization manually through the web interface go to IntegrationsProcessing modules → select a processing module → Config button. 

If the information differs, the list of operating systems in BILLmanager will be changed: 

  • A template exists in VMmanager but it is missing in BILLmanager — the OS template will be connected to the processing module and tariffs; 
  • A template exists in VMmanager but it has been disabled in BILLmanager manually — after synchronization, the OS template will still be disabled in BILLmanager; 
  • A template doesn't exist in VMmanager but it exists in BILLmanager — the OS template will be disabled from the processing module and tariffs.