| Table of Contents |
|---|
Introduction to concurrent VM operations
| Excerpt |
|---|
The platform uses configuration properties to control the number of concurrent operations |
...
to:
|
...
|
...
|
...
|
...
The platform can control concurrency for:
|
...
|
...
|
...
|
...
|
...
|
...
You can |
...
define |
...
concurrency limits at the level of:
|
...
|
...
|
...
You can also allow concurrent operations |
...
to change the state of a VM (e.g. power on), while limiting concurrent configure operations. See the "openSession" properties at Abiquo configuration properties#virtualfactory |
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.
- VM state changes (powerOn, powerOff, etc)
- Configure/Deconfigure/Reconfigure VM
- Register/Unregister/Update VM with Firewall Policy / Load Balancer / Nat Rule
- Perform Backup / Schedule Backup / Restore From Backup of a VM
An example of the application of when concurrency limits apply is when you are deploying a virtual appliance with multiple VMs.
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
When you use the fast state changes functionality, the platform will always execute VM state changes when you request them, without waiting for any concurrent operations to finish.
The VM state change operations are as follows:
...
| Code Block | ||||
|---|---|---|---|---|
| ||||
abiquo.virtualfactory.openSession.faststatechanges=true |
...
For example, with the following configuration, the platform will only allow one configure/deconfigure/reconfigure at a time, but several state changes can occur concurrently.
...