Project cloud synchronization

To ensure that data in BILLmanager matches the actual resources in the external system, the platform synchronizes their state. This article describes the synchronization mechanism using the integration with VMmanager 6 as an example.

Project cloud infrastructure features

When creating a project cloud, private networks are created automatically. Virtual machines (VM) are isolated within their private network and receive a private IP address. This feature is available only for cloud categories.

Synchronization types

Synchronization works differently for non-billable and billable resources:

• non-billable resources (for example, virtual networks) are synchronized automatically. If an external system administrator deletes a network directly, the information is reflected in BILLmanager during the next synchronization;
• billable resources (for example, virtual servers) require manual involvement of a platform employee. Automatic assignment of such resources is impossible, as the operation is associated with the client's financial obligations. The detection mechanism is used for such resources.

Synchronization of untariffed resources

To synchronize the state of the project's untariffed resources, go to the Goods/Services → Project clouds→ select the cloud service → click the Synchronize button.

After the operation is completed, the project service list will be updated. The update will reflect the actual state of the tenant in the external virtualization system.

Synchronization of billable resources

Billable resources detection

The detection mechanism allows you to identify VMs in an external virtualization system that do not have a corresponding service in BILLmanager, and assign them to a client within a specific project.

To start detection:

1. Go to the Integration → Processing modules section.
2. Select the required VMmanager 6 processing module from the list.
3. click the Autodiscovering button.
4. On the page that opens, click the Start button to generate an up-to-date list of VMs.

The detection table displays VMs with the following statuses:

• A VM exists in the external virtualization system, but there is no corresponding service in BILLmanager;
• a service exists in BILLmanager, but the corresponding VM is missing in the external virtualization system;
• A VM is marked as system and is not intended for assignment to clients.

Assigning a detected VM to a project

The procedure for assigning a VM to a project is similar to the standard assignment, but includes an additional step to select a project. For more information on standard assignment, see the VM autodiscovering article.

To assign a VM to a client within a project:

1. On the detection page, select the required VM from the list.
2. Click the Assign button.
3. On the first step select the Client and click Next.
4. On the second step, configure the tariff. Select:
   1. The Provider of the service.
   2. The Project to which the VM will be assigned.
   3. The Tariff according to which the service usage will be billed.
5. Click Next.
6. On the third step, configure the service parameters:
   1. Specify the Effective date, Period.
   2. Enable Auto-renewal if necessary.
   3. Configure VM resources:
      • disk space;
      • RAM;
      • number of processors;
      • public IP addresses;
      • operating system.
7. Click Finish.

After the operation is completed, a virtual server service is created in BILLmanager, linked to the selected project. The service card automatically populates fields with VM data: name, IP address, domain, configuration.

Creating a VM for an existing service

If BILLmanager has a virtual server service, but the corresponding VM is missing in the external virtualization system, the VM can be restored.

To create a VM for an existing service:

1. Go to the Integration → Processing modules section.
2. Select the VMmanager 6 processing module and click the Autodiscovering button.
3. Select the service for VM creation from the list.
4. Click the Start button.

The platform calls the processing module and initiates VM creation with parameters from the service. After successful completion, the service card populates fields with data for the created VM.