| 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 when the application of 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 it 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. This limits 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.
...
If you do not specify a value, then the default is the platform level property.
For example, to allow only one concurrent operation at any time on each AWS region.
| 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 properties for concurrency values (including plugin typelimits (for hypervisor/PCR endpoint, device, and backup manager) to an individual PER VDC.
This means that you must The platform supports "byvdc" properties when you have either a public cloud region with native support for VDCs (e.g. AWS VPC, Azure Virtual Network, vCloud vApp) or a hypervisor with a network device, (e.g. vCenter + NSX device).
If you do not specify these properties, the default values are false, which means that concurrent operations are limited at the level of the the platform will apply the concurrency limits PER hypervisor/public cloud providerendpoint, device, or backup manager. Or by the values set at the platform level.
| Code Block | ||||
|---|---|---|---|---|
| ||||
abiquo.virtualfactory.openSession.byvdc=false abiquo.virtualfactory.device.openSession.byvdc=false abiquo.virtualfactory.backup.openSession.byvdc=false |
...
For example, with the the following properties, it will only be possible to execute multiple concurrent operations (for the same hypervisor/PCR endpoint (connection data)) but only if they affect different virtual datacenters.
| Code Block | ||||
|---|---|---|---|---|
| ||||
abiquo.virtualfactory.openSession.byvdc=true abiquo.virtualfactory.openSession=1 |
When using you use ''openSession.byvdc'' properties, the platform does not limit the maximum number of concurrent connections to the provider endpoint or hypervisor IP (i.e. same set of connection data)hypervisor/PCR endpoint, device, or backup manager.
In contrast, if openSession.byvdc is false, the platform will only allow two concurrent operations for each provider endpoint or hypervisor IP, device, or backup manager.
For example, for the following configuration, in AWS you could have a total number of concurrent operations equal to the number of virtual datacenters x 2.
| Code Block | ||||
|---|---|---|---|---|
| ||||
abiquo.virtualfactory.openSession.byvdc=true abiquo.virtualfactory.amazon.openSession=2 |
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 changes change operations are as follows:
- powerOn
- powerOff
- shutdown
- reset
- pause
- resume
...
| 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.
...