...
To limit concurrency for specific plugin typesplugins, devices, or backup managers.
If not specified by type, then the defaults are the platform level properties.
...
Control concurrency at the virtual datacenter level
In Abiquo 4.5+ you can also limit concurrency for virtual datacenters. This will not apply to public cloud providers that do not support VDCs.
To prevent concurrent operations at the virtual datacenter level, use the "byvdc" property. This property can apply to VDCs, devices, and backup managersConcurrency control at the VDC level means that the platform will apply the properties for concurrency values (including plugin type, device, and backup manager) to an individual VDC.
The default values allow concurrent operations to the same VDC. provider type, device, and backup manager.
...
| Code Block |
|---|
|
abiquo.virtualfactory.openSession.byvdc=true
abiquo.virtualfactory.openSession=1
|
Note that when using ''openSession.byvdc'', the platform does not limit the maximum number of concurrent connections to the same ConnectionData (provider endpoint or hypervisor IP). 
Allow fast VM state changes
...
| Code Block |
|---|
|
abiquo.virtualfactory.openSession.faststatechanges=true
abiquo.virtualfactory.openSession=1
|
...
* changing the behavior of the pool when using a provider also capable of device ops (public clouds with lb,fw, net or nat features), previously using 2 pools (opensessions + device.opensessions), now a plugin capable of executin device ops only use the opensessions pool.
...
Examples
no concurrency in a virtualdatacenter (by type)
...
| Panel |
|---|
Given
abiquo.properties: |
...
- abiquo.virtualfactory.vcd.openSession=1
|
...
- abiquo.virtualfactory.vcd.openSession.byvdc=true
a vcloud public cloud region
2 virtualdatacenters (2 vapps in vcloud)
When
deploy a vapp with +1 vm in each vdc
Then
only one concurrent operation for each virtualdatacenter
concurrent operations can affect different virtualdatacenters |
...
...
no limitation if not specified by type
...
| Panel |
|---|
Given
abiquo.properties: |
...
- abiquo.virtualfactory.vcd.openSession=1
|
...
- abiquo.virtualfactory.vcd.openSession.byvdc=true
an amazon public cloud region
2 virtualdatacenters
When
deploy a vapp with +1 vm in each vdc
Then
the default is applied (abiquo.virtualfactory.openSession=2 / abiquo.virtualfactory.openSession.byvdc=false)
only 2 concurrent operations independent of the virtualdatacenter |
...
...
change the default concurrency context
...
| Panel |
|---|
Given
abiquo.properties: |
...
- abiquo.virtualfactory.openSession.byvdc=true
a vcloud public cloud region
2 virtualdatacenters (2 vapps in vcloud)
When
deploy a vapp with +1 vm in each vdc
Then
only one concurrent operation for each virtualdatacenter
concurrent operations can affect different virtualdatacenters |
...
...
compute plugin without vpc device
...
| Panel |
|---|
Given
abiquo.properties: |
...
- abiquo.virtualfactory.openSession.byvdc=true
a esx datacenter without any networking device (or using a device not implementing Vpc - nowadays all implements Vpc)
2 virtualdatacenters
When
deploy a vapp with +1 vm in each vdc
Then
vms doesnt have the sense of virtualdatacenter (any?=(no)? Vpc plugin capable of setting the vpc/vdcProviderId)
only 2 concurrent operations independent of the virtualdatacenter
this means the same result will apply with the same setup but using the default openSession.byvdc=false |
...
...
fast powerOn
...
| Panel |
|---|
Given
abiquo.properties: |
...
- abiquo.virtualfactory.vmx_04.openSession=1
|
...
- abiquo.virtualfactory.vmx_04.openSession.faststatechanges=true
a esx-vcenter private datacenter (with or without device)
2 virtualdatacenters
When
deploy a vapp with +1 vm in each vdc
Then
only one configure operation concurrently, but all powerOn after the configure of the vm (regardless if performing other powerOns or other vm configure) |
...
...
fast powerOn during configure
...
| Panel |
|---|
Given
abiquo.properties: |
...
- abiquo.virtualfactory.vmx_04.openSession=1
|
...
- abiquo.virtualfactory.vmx_04.openSession.faststatechanges=true
a esx-vcenter private datacenter (with or without device)
When
deploy a vapp with +1 vms
powerOn/powerOff/reset/pause or resume another vm (same vdc or not)
Then
only one configure operation concurrently, but the state change in the other vm is executed immediately |
...