| 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
...
- 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.
...
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.
...