The settings of your IncrediBuild Cloud solution are configured in the Settings page. Theses settings consist of the following sections:
...
Parameter | Description |
Cloud Region | AWS region where the VMs will run. In this region, the pool and additional Helper VMs will be created. It is recommended to select the same region for the Initiating VMs and the pool and Helper VMs, in order to avoid network latency. |
Tags | [Optional] AWS custom tags that will be added automatically to the following resources, which that are created by IncrediBuild on AWS:
You can add up to 5 custom tags, by defining for each tag a name:value pair. For more information on resource tagging in AWS, see: To find Your Machine cost by using the Tags, you must enable the "cost allocation tags," and after the machine usage, navigate to the Cost Explorer, see: https://docs.aws.amazon.com/awsaccountbilling/latest/aboutv2/cost-alloc-tags.html |
Use Private Network |  [Optional] This option enables you to use a Virtual Private Network on the cloud for launching and running Helper VMs, thus adding another layer of security for your transferred data. Important! To use this option, you must already have a private network on AWS. Your Coordinator host should be connected to the private network as follows:
Once you enable the Use Private Network option, in addition to the other parameters described above, you need to set the following:
|
...
Parameter | Description |
Tenant ID | Your Azure tenant ID. |
Subscription | Your Azure subscription name. |
Cloud Region | Azure region where the VMs will run. In this region, the pool and additional Helper VMs will be created. It is recommended to select the same region for the Initiating VMs and the pool and Helper VMs, in order to avoid network latency. |
Resource Group Name | [Optional] Customization of the name of the default resource group. All the resources that are created by IncrediBuild Cloud for build acceleration, belong to one resource group. You can change the default name of this resource group before activating the solution. If you do not add a customized name for the resource group and leaves this field empty, IncrediBuild Cloud will use a default value, which includes your Coordinator ID. |
Tags | [Optional] Azure custom tags that will be added automatically to the following resources that are created by IncrediBuild on Azure:
You can add up to 5 custom tags, by defining for each tag a name:value pair. For more information on resource tagging in Azure, see: Note: All Azure cloud resources that are created by IncrediBuild include "cloud" in their name. |
Use Private Network |  [Optional] This option enables you to use a Virtual Private Network on the cloud for launching and running Helper VMs, thus adding another layer of security for your transferred data. Important! To use this option, you must already have a private network on Azure. Your Coordinator host should be connected to the private network as follows:
Once you enable the Use Private Network option, in addition to the other parameters described above, you need to set the following:
|
...
VM Type – for machines that will function solely as Helpers, use VMs with a high number of CPU cores, such as 32 or 64 cores.
Note: Machines that will function solely as Initiators, can have a small number of cores.VMs with a high number of CPU cores improve performance, since their cache reduces the required number of file sync iterations.
[For IncrediBuild Cloud solution only] VMs with a high number of CPU cores save storage costs when these machines are in a Sleep mode in the pool, in comparison to many VMs with a smaller number of cores that together provide the same number of cores.
Number of VMs in the pool - all VMs that function solely as Helpers should be in the pool to avoid cache loss.
To apply this recommendation, in the Settings page of your IncrediBuild Cloud solution, verify the following:
Total Cores Limit value = No. of VMs in Pool value X the number of cores of your selected VM Type.
This will ensure that every VM that will be launched for your tasks will be included in the pool allocation.
For example, if you selected a VM Type that has 32 cores, and you want to use at the most 160 cores, specify 5 VMs for the No. of VMs in Pool:
If you set a higher value in the Total Cores Limit field, it means that if your tasks will require more Helper cores than the ones that are in the pool, additional VMs will be launched for these tasks. However, once the tasks will be completed, these additional VMs will be terminated and their cache will be lost.
...