...
You can also allow concurrent operations that change the state of a VM (e.g. power on), while limiting concurrent configure operations.
List of VM operations for which the platform controls concurrency
The platform controls concurrency for VMs, which means the following operations that are managed through the provider/hypervisor, device, or backup manager.
...
The concurrency limits do not apply to non-VM entities related to virtual datacenters because the platform does not use the same pool for these, for example, the platform does not restrict the number of concurrent operations to create a private network.
Set default concurrency limits for the platform
The top level of concurrency configuration is the platform. These properties limit the number of concurrent operations for the same connection (hypervisor IP or endpoint), device, or backup manager.
...
This means that if you have two vCenters and some public cloud regions, you can perform two concurrent operations on vCenter1, and two on vCenter2, and two on each of the public cloud regions.
Set concurrency limits for a type of hypervisor or public cloud provider, device, or backup manager
To limit concurrency for specific plugins, devices, or backup managers, set the specific properties for this purpose.
...
| Code Block |
|---|
abiquo.virtualfactory.amazon.openSession=1 |
Control concurrency at the virtual datacenter level
Concurrency control at the VDC level means that the platform will apply the concurrency limits (for hypervisor/PCR endpoint, device, and backup manager) PER VDC.
...
In contrast, if the "byvdc" properties are false (or not present) the platform will only allow two concurrent operations for each hypervisor/provider endpoint, device, or backup manager.
Allow fast VM state changes
The VM state change operations are as follows:
...