[
https://issues.apache.org/jira/browse/CLOUDSTACK-2843?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13688170#comment-13688170
]
ASF subversion and git services commented on CLOUDSTACK-2843:
-------------------------------------------------------------
Commit d66e9c7b518895c28461118523698b6a7f0fd830 in branch refs/heads/master
from [~alena1108]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=d66e9c7 ]
CLOUDSTACK-2843: Provideded an ability to turn off the synchronization being
done on the CS agent side,
for number of commands participating in Vm deployment process, as parallel
deployment is supported on the hypervisor side.
The behavior is controlled by global config varirables:
"execute.in.sequence.hypervisor.commands" (false by default) sets/resets the
synchronization for commands:
=========================
StartCommand
StopCommand
CreateCommand
CopyVolumeCommand
"execute.in.sequence.network.element.commands" (false by default) sets/resets
the synchronization for commands:
==========================
DhcpEntryCommand
SavePasswordCommand
UserDataCommand
VmDataCommand
As a part of the fix, increased the global lock timeout to 30 mins in several
VR scripts:
===========================
edithosts.sh
savepassword.sh
userdata.sh
to support situations when multiple concurrent calls to the script are being
made.
> Support parallel VM deployment with CloudStack
> ----------------------------------------------
>
> Key: CLOUDSTACK-2843
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-2843
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: Management Server
> Affects Versions: 4.2.0
> Reporter: Alena Prokharchyk
> Assignee: Alena Prokharchyk
> Fix For: 4.2.0
>
>
> When a user deploys multiple instances concurrently, the deployment of these
> VMs are in fact queued up, so although CloudStack reports that all
> deployments have started to be created, it would appear in reality that until
> the 1st instance is deployed, the second, third, etc are queued and waiting
> to be executed.
> CS should be able to support parallel VM deployment assuming the cluster
> resources can handle it.
> As a part of it, we have to:
> 1) Set executeInSequence=false for Start/Stop commands (also might make it
> false for PrimaryStorageDownload command as well)
> 2) Identify possible implication of turning off the synchronization for those
> commands, and fix the problematic places in the code.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
