[
https://issues.apache.org/jira/browse/CLOUDSTACK-3484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13719800#comment-13719800
]
ASF subversion and git services commented on CLOUDSTACK-3484:
-------------------------------------------------------------
Commit 74df662037d178786fcba92f57f673a7040b1490 in branch refs/heads/master
from [~mlsorensen]
[ https://git-wip-us.apache.org/repos/asf?p=cloudstack.git;h=74df662 ]
Summary: Make vmdata_kvm.py concurrency friendly
Detail: Adds flocks, etc for calling this concurrently, since CLOUDSTACK-3484
made userdata, vmdata, start commands concurrent
Signed-off-by: Marcus Sorensen <[email protected]> 1374773177 -0600
> Parallel deployment - KVM - Synchrnization still happens on the agent side
> when execute.in.sequence.hypervisor.command and
> execute.in.sequence.network.element.commands are set to false.
> -----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: CLOUDSTACK-3484
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-3484
> 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
> Environment: Build from 4.2
> Reporter: Sangeetha Hariharan
> Assignee: Kishan Kavala
> Priority: Blocker
> Fix For: 4.2.0
>
>
> Parallel deployment - KVM - Synchrnization still happens on the agent side
> when execute.in.sequence.hypervisor.command and
> execute.in.sequence.network.element.commands are set to false.
> Steps to reproduce the problem:
> Set up -Advanced zone with KVM host.
> Deploy 30 Vm in parallel.
> Following commands are not getting executed in parallel on the host:
> StartCommand
> StopCommand
> CreateCommand
> CopyVolumeCommand
> DhcpEntryCommand
> SavePasswordCommand
> UserDataCommand
> VmDataCommand
--
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
