Page Comparison

Introduction to concurrent VM 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.

• 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. This limits  These properties limit the number of concurrent operations for the same connection (hypervisor IP or endpoint), device, or backup manager.

...

Code Block
java java
abiquo.virtualfactory.openSession=2

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.

abiquo.virtualfactory.{pluginTypeInLowerCase}.openSession
abiquo.virtualfactory.{backupManagerLowerCase}.backup.openSession
abiquo.virtualfactory.{deviceLowerCase}.device.openSession

If you do not specify a value, then the default is the platform level property.

For example, to allow two connections to AWS.only one operation at any time on each AWS region.

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 by the type of 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. 

abiquo.virtualfactory.openSession.byvdc=false
abiquo.virtualfactory.device.openSession.byvdc=false
abiquo.virtualfactory.backup.openSession.byvdc=false

To prevent compute concurrency in the same virtual datacenter, which means all the operations to the same VDC will be executed one after another, set the "byvdc" property to true and restrict the total number of sessions as the platform or provider/hypervisor level.

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.

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 same ConnectionData (provider endpoint or hypervisor IP)hypervisor/PCR endpoint, device, or backup manager. 

For example, if you have set openSession=2 for a vCloud1, when openSession.byvdc is set to true, the platform will allow two concurrent operations per VDC in vCloud1, with a total of up to "Number of VDCs x 2".In contrast, if openSession.byvdc is false, for the following configuration, in AWS you could have a total number of concurrent operations equal to the number of virtual datacenters x 2.

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

...

abiquo.virtualfactory.openSession.faststatechanges=true

When you use this fast state changes functionality, the platform will always execute VM state changes when you request them, without waiting for an ''available worker in the pool''.

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.

abiquo.virtualfactory.openSession.faststatechanges=true
abiquo.virtualfactory.openSession=1

Limitations
—
* the properties only apply to the virtualfactory (vm centric ops) so don't expect other operations with entities related to virtualdatacenter are also executed in the same pool (eg: create private network doesn't follow this concurrency limitations)

* byvdc requires a Vpc interface implementation, which can be:
** compute plugin also implements Vpc. eg: PCR vcloud 
** compute plugin + networking device. eg: vcenter + nsx device 

...