[
https://issues.apache.org/jira/browse/CLOUDSTACK-5218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13865339#comment-13865339
]
Radhika Nair commented on CLOUDSTACK-5218:
------------------------------------------
commit b26878d17961129f2218f442c2fae73b45496bb7
Author: Radhika PC <[email protected]>
Date: Wed Jan 8 17:10:44 2014 +0530
CLOUDSTACK-5218 vmware timeout global config
> CLONE - [Doc] Make VMware vCenter session timeout value configurable.
> ---------------------------------------------------------------------
>
> Key: CLOUDSTACK-5218
> URL: https://issues.apache.org/jira/browse/CLOUDSTACK-5218
> Project: CloudStack
> Issue Type: Bug
> Security Level: Public(Anyone can view this level - this is the
> default.)
> Components: VMware
> Affects Versions: 4.2.0
> Reporter: Likitha Shetty
> Assignee: Radhika Nair
> Priority: Critical
> Labels: documentation
> Fix For: 4.3.0
>
>
> We see socket timeout errors in a VMware setup if a VMware task
> (RelocateVM_Task, CloneVM_Task etc.) takes more than 20 minutes.
> Add a global config 'vmware.vcenter.session.timeout' to make the vCenter
> session timeout value configurable.
> Note that VMware tasks like CloneVM_Task take longer if we use the default
> full-clone mode and a slow storage.
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
