Operating systems available for order. Hyper-V

The article contains information about how BILLmanager loads and updates the list of operating systems from Hyper-V. It describes:

• the mechanism for loading the OS list;
• template parameter management;
• the process of automatic and manual synchronization of the OS list.

How the OS list is loaded

After the integration is configured, BILLmanager gets a list of available operating system templates (OS) from Hyper-V. The received templates are available by default for selection when ordering a VM on a tariff with the Hyper-V module.

The list of loaded OS templates is stored in BILLmanager and can be edited in Products → Product types → choose VPS → click Parameters → element Operating systems → click Values.

Operating system parameters:

• Name — the OS template name. It matches the template name in Hyper-V;
• Internal name — the unique identifier of the OS template;
• Tags — OS template tags. In general, they are used to link a template to recipes. For Hyper-V, tags are used to determine the OS family (Linux or Windows). Manual tag addition for Hyper-V is not supported: they will be overwritten during the next synchronization;
• Sorting — the order in which OS templates are sorted when ordering a service. Sorting from lowest to highest is used;
• Status — the OS template status:
  • — available for order on all tariff plans;
  • — available for order on some tariff plans;
  • — unavailable on any tariff plan.

Minimum resource requirements

Minimum virtual server resource values can be set for the OS according to the system requirements:

• hard drive size;
• RAM size;
• number of CPU cores.

These values cannot be changed from the billing platform side.

To check them, go to Products → Product types → element VPS → click Parameters → element Operating systems → click Values → select an OS → click Edit → fields Number of CPUs, RAM and Hard drive.

Managing OS templates

To make an OS template available for order, connect it to a tariff and to one of that tariff’s modules. To change template availability:

1. Go to Products → Product types → select VPS → click Parameters → select Operating systems → click Values.
2. Select an operating system and click the buttons:

• • Modules — opens the list of processing modules for the product type "VPS". Status shows template availability on the module:
    • — the template is connected to the module;
    • — the template is not connected to the module;
  • Tariff plans — opens the list of tariff plans with the product type "VPS". Status shows template availability for order:
    • — the template is available for selection when ordering a VM on this tariff;
    • — the template is unavailable for selection when ordering a VM on this tariff.

If several modules with different OS templates are connected to one tariff, all of these OS templates will be shown in one tariff. To make sure extra OS templates are not shown in one tariff:

1. Go to Products → Tariff plans.
2. Select a tariff plan → click Clone. Create as many tariff clones as you need to separate modules from each other.
3. Select the tariff plan clone → click Modules → enable the module for the tariff. Connect a separate module for each tariff clone.

How the OS list is updated

Once an hour, BILLmanager contacts Hyper-V and updates information about available OS templates. For this purpose, there is a cron job:

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

To start synchronization manually through the interface, go to Integration → Processing modules, select the required module, and click Config.

If differences are found during synchronization, the OS list in BILLmanager changes:

• the template exists in Hyper-V and not in BILLmanager — the OS template will be connected to the service module and tariffs;
• the template exists in Hyper-V and was disabled manually in BILLmanager — after synchronization, the OS template remains disabled in BILLmanager;
• the template does not exist in Hyper-V and exists in BILLmanager — the OS template will be deleted.