If the vSphere virtual machine environment you manage services a large number of concurrent requests, such as multiple (for example, more than 30) concurrent Business Service Requests for workloads from Novell Cloud Manager, you should tune the vsphere provisioning adapter in PlateSpin Orchestrate 2.5 to accommodate the load.
We recommend that you adjust these policies for large scale concurrent VM provisioning operations.
Use the following steps to adjust critical performance facts in the policy.
In the Explorer view of the Orchestrate Development Client, select the vsphere policy to open the policy editor.
On line 77, change the default value for the actionTimeout fact from 2400 to 7200.
<fact name="actionTimeout"
type="Integer"
value="2400"
description="Timeout limit for this job to process a PA action in seconds"/>
Click the icon.
Use the following steps to adjust critical facts in the policy.
In the Explorer view of the Orchestrate Development Client, select the vsphereadaemon policy to open the policy editor.
On line 26, change the default value for the maxConcurrentTimeout fact from 3600 to 7200.
<fact name="maxConcurrentTimeout"
type="Integer"
value="3600"
description="Timeout limit to wait in seconds for a operation to be accepted. Wait is due to reaching the maxConcurrentOperation limit"/>
On line 46, change the default value for the javaArgs fact from 256 to 1024.
<fact name="javaArgs"
type="String"
value="-Xmx256m"
description="JVM args for vsphere client"/>
Click the icon.